Page Comparison

New Inquiry Received : triggered when the Service Desk Email account receives a new email and an Inquiry is created.

New ServiceDesk Item Created : triggered when a new Service Desk Item is created.  All SD Types create to trigger this event in addition to the more specific events.

New Service Order Created :

 triggered when a new Service Order is created.

New Estimate Created :

 triggered when a new Estimate is created.

New Service Request Created :

 triggered when a new Service Request is created.

New Incident Created :

 triggered when a new Incident is created.

New Incident Request Created :

 triggered when a new Incident Request is created.

New Project Created :

 triggered when a new Project is created.

New Problem Created :

 triggered when a new Problem is created.

New QuickTick Created :

 triggered when a new QuickTick is created.

ServiceDesk Item Assigned : triggered when a Service Rep (CSR) is assigned to or changed on a Service Desk Item.

ServiceDesk Item Status Changed :

 triggered when the Status of a Service Desk Item is changed.

ServiceDesk Item Completed :

 triggered when a Service Desk Item is completed.

ServiceDesk Item Viewed :

 triggered when a Service Desk Item is opened by a User.

ServiceDesk Item Updated :

 triggered when a Service Desk Item is updated.

ServiceDesk Item Remarks Added :

 triggered when a Remark is added to a Service Desk Item.

ServiceDesk Order Action Added :

 triggered when an Action is added to a Service Order.

ServiceDesk Order Action Updated :

 triggered when an Action on a Service Order is updated.

ServiceDesk Action Status Changed :

 triggered when a Service Desk Action has its Status updated.

ServiceDesk Order Action Removed :

 triggered when a Service Desk Action is removed.

ServiceDesk Action Cisco Provision : triggered

when a Service Desk Action requested a new provisioning from the Cisco Call Manager. This Event is only setup if the Cisco Interface Module has been purchased.

Service Desk Workflow Added :

 triggered when a Workflow is added to a Service Desk Item.

Service Desk Workflow Deleted :

 triggered when a Workflow is removed from a Service Desk Item.

Service Desk Workflow Assigned :

 triggered when the Worker assigned to a Workflow changes - this Event provides data related to the new Worker, for example to notify the Worker they have been assigned.

Service Desk Workflow Unassigned :

 triggered when the Worker assigned to a Workflow changes - this Event provides data related to the previous Worker, for example to notify the Worker they are no longer assigned.

Service Desk Workflow Updated : triggered when a Workflow is updated, even if the only 'change' what to re-save the Workflow. This will NOT trigger when a new Workflow is created.

Service Desk Workflow Not Assigned : triggered

when a new Workflow has been created, and is not assigned to a Worker.

Service Desk Workflow Status Changed :

 triggered when a Workflow's Status has changed - this Event contains data related to the previous and new Statuses.

Service Desk Workflow Start Date :

 triggered when a Start Date is first set for a Workflow.

Service Desk Workflow Void :

 triggered when a Workflow on a Service Desk Item is Voided.

Service Desk Workflow Update Request :

 triggered from the Service Desk Workflow tab "Request Update" button.  Used to request an update from the Worker attached to the specified Workflow.

Service Desk Equipment Added :

 triggered when a piece of Equipment is added to a Service Desk Item.

Service Desk Equipment Updated :

 triggered when a piece of Equipment is updated on a Service Desk Item.

Service Desk Equipment Deleted :

 triggered when a piece of Equipment is removed from a Service Desk Item.

Service Desk Item Converted to Incident :

 triggered when a Service Desk Item is converted into an Incident.

Service Desk Item Converted to Service Order :

 triggered when a Service Desk Item is converted into a Service Order.

Service Desk Item Converted to Project :

 triggered when a Service Desk Item is converted into a Project.

Service Desk Item Converted to Problem :

 triggered when a Service Desk Item is converted into a Problem.

Service Desk Annual Number Reset

: recurring once a year to reset the Service Desk Number Configuration

"Next Sequence Number" to "1". This event is created on-demand and is not default for new installations. This Event can NOT be used to set up

Notifications and

Escalations.

Service Desk Bulk Update Requested :

 triggered when a Bulk Update request is made on

Service Desk Items. This Event can NOT be used to set up

Notifications and

Escalations.

Service Desk Log Approval : triggered from the Service Desk Activity Remarks tab "Log Approval" button.  Used to indicate that an approval has been logged for the specified item.

Service Desk Thread Received (CSR) : triggered when a Email message has been received and attached to an existing Service Desk item.  This event can be used to notify the Service Rep (CSR) that a new thread has been attached.

Service Desk Thread Received (Response) : triggered when a Email message has been received and attached to an existing Service Desk item.  This event can be used to notify the email sender that their message was received.

ServiceDesk Item Archive : triggered at scheduled intervals

to automatically collect any eligible Service Desk Records to be Archived. This is a Master Lock Event.

CustomerCenter Request Submitted for Approval : triggered when a Request that requires approval is Submitted.

CustomerCenter Request Approved : triggered when a Request that requires approval is Approved.

CustomerCenter Request Denied : triggered when a Request that requires approval is Denied.

Process Uploaded Import Files : recurring every minute this event watches for Import Files that are ready to be processed.  This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event.

Prepare Uploaded Import Files in Upload Directory for Processing : recurring every minute to detect files in the Inbound Directory that need processing. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event.

Check if Import Files in Upload Directory have finished Uploading : recurring every minute this Event to see if Files in the Inbound Directory have been completely uploaded. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Reprocess Import File Errors : recurring once a day to reprocess any Import File that have encountered errors. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Reprocess Selected Import Files : triggered from the Import Files grid "Reprocess Selected" button.  Used to reprocess selected Import File. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event.

Delete Selected Import Files : triggered from the Import Files grid "Delete Selected" button. Used to delete selected Import File.

   This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Rerate Calls : triggered from the Call Details grid "Rerate Calls" button.  Used to rerate Calls in a specified Date Range.

  This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Import File Processed - Number of records Imported, number of Errors :

 triggered when an Import Process completes, and the Import Format definition is set to always notify on completion and an email address was provided. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Import File Processed with Unusual record Volume :

 triggered when an Import Process completes, and the Import Format definition has defined low and high volumes, and the volume processed was outside the expected range and an email address was provided. This Event

can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Delete old Import Files and Imported Records : recurring  every day to cleanup old Imported Files and Imported Records based on the Import File Format Retention settings. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Update Bill Date :

 triggered when a User has manually set an Import File to override the Bill Date (usually for a Calls or Charges Import). This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Process Uploaded VH Data Files : recurring daily to process uploaded VH Data Files. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Rate Processed Calls : recurring daily (more often by request) to Rate unrated Calls. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Rerate Processed Call Errors : recurring daily (less often by request) to rerate Call Errors encountered during the initial rating process. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Rate Processed Usage : recurring daily to Rate unrated Usage data. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Rerate Processed Usage Errors : recurring daily (less often by request) to rerate Usage Rating Errors encountered during the initial rating process. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Call Rates Bulk Update Requested :

 triggered when a Bulk Update is made for Call Rates. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Cleanup Audit Data :

 When enabled, this Event runs on a regular schedule to Clean up the AUDIT table and the AUDIT Archive tables.

 The purpose of this event is to remove duplicate audit data for each PRIMARY_KEY. A record is a duplicate if the FROM_DATA and the TO_DATA JSON are identical with the exception of the MODIFIED_DATE and MODIFIED_BY fields.

 This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event.

Archive Audit Data : Audit Data needs to be archived. This Event runs on a weekly basis. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event.

Archive Bill Details Data : triggered when a Bill is generated.  Used to archive the specified Bill based on the Tenant setting for Bill Archiving. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event.

Archive Call Details Data : Call Details Data needs to be archived. This Event runs on a weekly basis. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event.

Archive Escalation Log Data : Escalation Log Data needs to be archived. This Event runs on a weekly basis. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Archive Escalation Sequence Log Data : Escalation Sequence Log Data needs to be archived. This Event runs on a weekly basis. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Archive Imports Data : Import Data needs to be archived. This Event runs on a daily basis. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event.

Archive Notification Log Data : Notification Log Data needs to be archived. This Event runs on a weekly basis. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Archive SOAP Data :

 triggered when SOAP Data needs to be archived. This is only setup within the System if the Avaya or Cisco Modules are licensed. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

System Failed to Process Email :

 triggered when a received email was unable to be processed into PCR-360.

Cron Process Error Occurred : triggered

when notification event triggered when the Cron Process encounters an error processing an event. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Knowledgebase Article Error : triggers when an error is reported on a Knowledgebase Article, so the Article's status can be updated.

Reset Password Request : triggered

when a Notification event triggered by a User requesting their password reset. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Scheduled Export Request Executed : triggered when an Export is scheduled. Can be created as a recurring or one-time event. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

IP Address Bulk Update Requested :

 triggered when a Bulk Update is made of IP Addresses. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Ports/Pins/Lens Bulk Update Requested :

 triggered when a Bulk Update is made for Ports/Pins/Lens. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Pairs/Strands Bulk Update Requested :

 triggered when a Bulk Update is made for Pairs/Strands. This Event

can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Threshold for Failed Logins Met : triggered when a User reaches the threshold for failed login attempts. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

E-mail Grid Report : triggered when a grid Perspective Report is scheduled.  Can be a recurring or one-time event. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Generate Report Batch : triggered

when a Crystal Report Batch is scheduled from the Crystal Report grid or form.  Can be a recurring or one-time event. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Custom PHP Event : recurring events used to trigger Custom Event logic. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

System-wide Contact Replacement :

 triggered when a Contact replacement is requested. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

System-wide Department Replacement :

 triggered when a Department replacement is requested. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

API Request Logs Deleted : recurring daily to cleanup REST API  Request Logs based on the Log Retention setting. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

System Bulk Update History Cleanup : recurs weekly to clean up Bulk Update History as defined by the Tenant.

System Message Cleanup : recurs weekly to clean up Messages as defined by the Tenant.

SL100 Auth Code Command Issued : triggered when Activating, Updating or Deactivating an Authorization Code Service.  If the Authorization Code is using the SL100 Service Host the requested changes are sent to the switch via an IP connection. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

These Events are a part of a separate module of the Application and will not be created on your Organization's install unless the Avaya Interface Module has been purchased.

Avaya Sync : This Event triggers over a set interval for making sure all CORs and Auth Codes are synchronized between the Avaya Call Manager and PCR-360. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Avaya Bulk Update :

 triggered when Avaya Communication Records need to be updated from the Avaya Call Manager. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

These Events are a part of a separate module of the Application and will not be created on your Organization's install unless the Cisco Interface Module has been purchased.

Cisco CM Reconciliation : This Event triggers over a set interval for making sure all CORs and Auth Codes are synchronized between Cisco Call Manager and PCR-360. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.

Cisco Bulk Update :

 triggered when Cisco Communication Records need to be updated from the Cisco Call Manager. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations.