Table of Contents | ||||
---|---|---|---|---|
|
Excerptexpand | ||
---|---|---|
| ||
Toggle cloak | | |
| ||
Cloak | ||
|
Expand | |||
---|---|---|---|
| cloak
| ||
Service ID Range Generation Requested : triggered when atriggered when a range of Service IDs is requested to be generated. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Phone Service Range Generation Requested : triggered when atriggered when a range of Phone Services is requested to be generated. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Alias Range Generation Requested : triggered when atriggered when a range of Alias is requested to be generated. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Service Bulk Update Requested : triggered when atriggered when a (2024.1) Bulk Update is made on Services. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Process Aging : A built-in Event that processes Inactive Services back to Availability. The customer must opt-in to activate this Event. This is a recurring Event. This Event can NOTcan NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Inventory |
Expand | |||
---|---|---|---|
| cloak
| ||
Purchase Order Created : triggered when atriggered when a (2024.1) Purchase Order is created. Purchase Order Updated : triggered when atriggered when a (2024.1) Purchase Order is updated. Purchase Order Status Open : triggered when atriggered when a (2024.1) Purchase Order has it's Status updated to Open. Purchase Order Approved : triggered when atriggered when a (2024.1) Purchase Order is approved. Return Order Created : triggered when atriggered when a (2024.1) Return Order is created. Return Order Updated : triggered when atriggered when a (2024.1) Return Order is updated. Equipment Bulk Update Requested : triggered when atriggered when a Bulk Update is made on Equipment. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Warehouse Equipment Bulk Add Requested : triggered when atriggered when a Bulk Add is made for Equipment. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Warehouse Equipment Bulk Transfer Requested : triggered when atriggered when a Bulk Transfer is made for Equipment. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Barcode Transactions : recurrs every minute, unless it is already running to Process all pending Barcode Transactions. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This requires a Barcode Module License. Payments |
Expand | |||
---|---|---|---|
| cloak
| ||
Payment Created : triggered when atriggered when a Payment is created. Payment Updated : triggered when atriggered when a Payment is updated. Payment Status Changed : triggered when atriggered when a Payment's Status is updated. Process Payment Batch : triggered when atriggered when a Payment Batch is requested to be processed. Payment Batch Complete : triggered when atriggered when a Payment Batch completes processing. Billing |
Expand | |||
---|---|---|---|
| cloak
| ||
Delete Bill : triggered when atriggered when a Bill is requested to be deleted. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event. Generate Bill : triggered when atriggered when a Bill is requested to be generated. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. This is a Master Lock Event. Approve Bill : triggered when atriggered when a Bill is marked as approved. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Bill Generation Completed : triggered when atriggered when a Bill completes generation. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Bill Generation Estimate Completed : triggered when a Bill Estimate is completed. Used to cleanup the estimate data after a day. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Bill Coordinator Email : triggered from the "Email Coordinators" button on the Bills grid. Used to email the Billing Coordinators. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Bill Specified Servicedesk Items : triggered when atriggered when a Bill has completed, and Service Desk Items on the Bill need to move from Finalized to Billed. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Unbill Specified Servicedesk Items : triggered when atriggered when a Bill has been deleted, and Service Desk Items on the Bill need to move from Billed to Finalized. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. GLA Replacement Requested : triggered when atriggered when a GLA Replace is requested. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. Available Charges Bulk Update Requested : triggered when a Charge Catalog has been changed to update related Charges on Equipment, Services and Service Desk Items. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. GLA Created : triggered when atriggered when a new GLA is created. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. GLA Updated : triggered when atriggered when a GLA is updated. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. GLA Activated : triggered when atriggered when a GLA is made Active. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. GLA Deactivated : triggered when atriggered when a GLA is made Inactive. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. GLA AR Account Update : triggered when atriggered when a GLA for Accounts Receivable is updated. This is a recurring Event. This Event can NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. |
Expand | ||
---|---|---|
| ||
Toggle cloak | Cloak | 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. ThisThis 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. ThisThis 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 antriggered 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 antriggered 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 NOTcan 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 atriggered 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 atriggered 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. |
Expand | ||
---|---|---|
| ||
Toggle cloak | Cloak | Cleanup Audit Data : WhenWhen enabled, this Event runs on a regular schedule to Clean up the AUDIT table and the AUDIT Archive tables. TheThe 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. ThisThis 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 SOAPtriggered 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. Escalations |
Expand | |||
---|---|---|---|
| cloak
| ||
Escalation Sequence Result : triggeredtriggered when a Eventa Event generated following a REST Sequence from an Escalation. Response data from the REST call is given to this Event. Other (2024.1) Escalations and (2024.1) Custom Events can then use this Event to execute other procedures. This Event can NOTcan NOT be used to set up (2024.1) Notifications and (2024.1) Escalations. |
Expand | ||
---|---|---|
| ||
Toggle cloak | Cloak | System Failed to Process Email : triggered when atriggered when a received email was unable to be processed into PCR-360. Cron Process Error Occurred : triggered when notificationwhen 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 awhen 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 atriggered 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 atriggered 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 atriggered when a Bulk Update is made for Pairs/Strands. This Event can NOTcan 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 awhen 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 atriggered 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 atriggered 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. |
Expand | ||||
---|---|---|---|---|
| toggle-cloak||||
Cloak | 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. |
Expand | ||
---|---|---|
| ||
Toggle cloak | 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. cloakAvaya 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 Avayatriggered 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. |
Expand | ||
---|---|---|
| ||
Toggle cloak | 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. Cloak | 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 Ciscotriggered 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. |