Business Rules Framework Event Details
This topic provides additional details for business rule events to help you make decisions regarding your implementation of the Business Rules Framework.
The following sections provides additional details for Business Rule Framework events, enabling you to view delivered events, their triggers, what actions can be run, and the associated Communication Event ID. In almost all cases, the Communication Event ID and the Business Rules Framework Event ID are the same. Knowing the event ID will be required if calling events from workflow.
Permits
The following table provides additional details for events related to permits. The events are sorted by Resource.
Event |
Details |
---|---|
Resource: Fee Communications Event: New Fees Due |
Description: New fees have been assessed and are due. Trigger: Click Add Fees on the Fees and Payments tab in the permit details. Actions:
Communication Event: New Fees Due (LNP-FEES-001) |
Resource: Permit Application Contact Event: Permit Additional Contact Added |
Description: Additional contact is added to the permit. Trigger: Click Add New Contact in the Additional Contacts grid on the Contacts page in permit details, and either select an existing contact or create a new one. Actions:
Communication Event: Permit Additional Contact Added (LNP-CONTACT-ADD) |
Resource: Permit Document Event: Permit Document Attached |
Description: Applicant attaches a permit document. Trigger: Click Add on Attachments page in permit details, select a document to upload, and click Upload on the Add Attachments dialog box. Actions:
Communication Event: Permit Document Attached (LNP_ATTACHMENT_UPLOADED) |
Resource: Permit Expiration Communication Event: About to Expire Permit |
Description: A permit is about to expire. Trigger: A permit is about to reach its set expiration date. Actions:
Communication Event: About to Expire Permit (PER-ATE-EXPIRY-001) |
Resource: Permit Expiration Communication Event: Expired Permit |
Description: A permit has expired. Trigger: A permit is about has exceeded its set expiration date. Actions:
Communication Event: Expired Permit (PER-EXPIRED-001) |
Resource: Permit Expiration Communication Event: Permit About to Expire Based on Inspection Commencement |
Description: A permit is about to expire based on the inspection beginning. Trigger: A permit is about to expire based on the inspection commencement rule setup. Actions:
Communication Event: Permit About to Expire Based on Inspection Commencement (PER-INS-ATE-EXPIRY-001) |
Resource: Permit Expiration Communication Event: Permit Expired Based on Inspection Commencement |
Description: A permit has expired based on the inspection beginning. Trigger: A permit has expired based on the inspection commencement rule setup. Actions:
Communication Event: Permit About to Expire Based on Inspection Commencement (PER-INS-EXPIRED-001) |
Resource: Permit Inspection Event:Permit Inspection Requested |
Description: An inspection is created. Trigger: Select Add Inspection from the permit or the Inspections page, provide the required information, and click Submit on the Inspections page. This can occur also from the mobile application and IVR. Actions:
Communication Event: Inspection Requested (LNP-INSPREQ-001) |
Resource: Permit Inspection Event: Final Permit Inspection Passed |
Description: Indicates that the final inspection is complete with a passing result. Trigger: For a final inspection, click Submit on the Inspection Result page. Actions:
Communication Event: Final Inspection Passed (LNP-FINALINSP-001) |
Resource: Permit Inspection Event:Permit Inspection Canceled |
Description: Indicates that an inspection is canceled. Trigger: Select Cancel Inspection for the inspection. An inspection can be canceled from the inspections console, the Inspections tab in the transaction details, or from the inspection request. Actions:
Communication Event: Inspection Canceled (LNP-INSPCANC-001) |
Resource: Permit Inspection Event:Permit Inspection Postponed |
Description: Indicates that an inspection is postponed. Trigger: Select Postpone for the inspection. An inspection can be postponed from the Inspections console page for agency staff, the Inspections tab in the transaction details, or from the inspection request. Registered public users can only postpone inspections if allowed at the agency-level in the permit and business license options. Actions:
Communication Event: Inspection Postponed (LNP-INSPPOSTPONE-001) |
Resource: Permit Inspection Event: Permit Inspection Rescheduled |
Description: Indicates that an inspection is rescheduled. Trigger: Click Reschedule for a currently scheduled inspection determine a new time, click Select, and click Submit. An inspection can be rescheduled from the inspections console for agency staff, the Inspections list page for registered public users, the Inspections tab in the transaction details, or from the inspection request. Actions:
Communication Event: Inspection Rescheduled (LNP-INSPRESCH-001) |
Resource: Permit Inspection Event:Permit Inspection Scheduled |
Description: Indicates that an inspection is scheduled. Trigger: For a newly added inspection, click Select a Time, determine a time slot, click Select, and click Submit. An inspection can be scheduled from the inspections console, the Inspections tab in the transaction details, or from the inspection request. Actions:
Communication Event: Inspection Scheduled (LNP-INSPSCH-001) |
Resource: Permit Inspection Event: Permit Inspection Complete |
Description: Notification sent to applicants when final inspection results have been determined. Trigger: Click Submit on the Inspection Result page or from Inspection Details page within the Mobile Inspector app. Actions:
Communication Event: Inspection Complete (LNP-INSPCOMP-001) |
Resource: Permit Inspection Event: Before Permit Inspection Saved |
Description: Before an inspection is saved. Trigger:
Actions:
Communication Event: Before Inspection Saved (LNP-INSPRSAVE-001) |
Resource: Permit Inspection Event:Permit Inspection ETA Updated |
Description: Indicates that the estimated time of arrival for a scheduled inspection is updated. Trigger: From the Actions menu in the Mobile Inspector app, select Update ETA. On the Estimated Time of Arrival page, select a new time, and click Save. Actions:
Communication Event: Inspection ETA Updated (LNP-INSPETAUPDATE-001) |
Resource: Permit Inspection Document Event: Permit Document Attached for Inspection Supervisor |
Description: Applicant attaches a permit document for the inspection supervisor. Trigger: Click Add on Attachments page in permit details, select a document to upload, and click Upload on the Add Attachments dialog box. Actions:
Communication Event: Permit Document Attached for Inspection Supervisor (LNP_ATTACHMENT_SUP_UPLOADED) |
Resource: Permit Inspection Document Event: Permit Document Attached for Inspector |
Description: Applicant attaches a permit document for the inspection supervisor. Trigger: Click Add on Attachments page in permit details, select a document to upload, and click Upload on the Add Attachments dialog box. Actions:
Communication Event: Permit Document Attached for Inspector (LNP_ATTACHMENT_INS_UPLOADED) |
Resource: Permit Missing Document Event: Permit Missing Document |
Description: Indicates that a permit application step is missing a required document. Trigger: Application steps or workflow events including Application Submittal, Application Issuance, Application Acceptance, Final Inspection, and Application Complete, depending on agency configuration. For more information, see Setting Up Required Documents. Actions:
Communication Event: Permit Missing Document (LNP_REQUIRED_DOCUMENT) |
Resource: Permit Plan Review Event: Permit Plan Review Finalized |
Description: Indicates that the permit plan review is finalized. Trigger: Click Finalize Session for the plan review session in Bluebeam Studioâ„¢. Actions:
Communication Event: Permit Plan Review Finalized (LNP_PR_FINALIZED) |
Resource: Permit Plan Review Event: Permit Plan Review Ready To Finalize |
Description: Indicates that the permit plan review is ready to finalize. Trigger: Click Save after the last reviewer provides a decision or the review is marked N/A (not applicable), and it is an electronic review. Actions:
Communication Event: Permit Plan Review Ready To Finalize (LNP_PR_READY_TO_FINALIZE) |
Resource: Permit Plan Review Event: Permit Plan Review Completed or Canceled |
Description: Indicates that the permit plan review is completed or canceled. Trigger:
Actions:
Communication Event: Inspection Scheduled (LNP-INSPSCH-001) |
Resource: Permit Plan Review Document Event: Permit Document Attached for Plan Coordinator |
Description: Applicant attaches a permit document for the plan coordinator. Trigger: Click Add on Attachments page in permit details, select a document to upload, and click Upload on the Add Attachments dialog box. Actions:
Communication Event: Permit Document Attached for Plan Coordinator (LNP_ATTACHMENT_PCC_UPLOADED) |
Resource: Permit Plan Review Document Event: Permit Document Attached for Plan Reviewers |
Description: Applicant attaches a permit document for plan reviewers. Trigger: Click Add on Attachments page in permit details, select a document to upload, and click Upload on the Add Attachments dialog box. Actions:
Communication Event: Permit Document Attached for Plan Reviewers (LNP_ATTACHMENT_PR_UPLOADED) |
Resource: Permits Workflow Communications Event: Permit Canceled |
Description: Applicant receives email or alert notification when a permit is canceled. Trigger: Select Cancel Application for a permit in the state of Pending, enter the cancellation reason, and click Yes on the Cancel Application page. Actions:
Communication Event: Permit Canceled (LNP-CANCEL-COMMUNICATION) |
Resource: Permits Workflow Communications Event: Before Permit Issuance |
Description: Runs before a permit is issued based on the Issue Permit task in the workflow process. For example, you can prevent a permit from being issued based on the criteria defined in the associated event. Trigger: This event is triggered by a workflow process task if the PSC_BRF_EVENT_CODE has been specified. Actions:
Communication Event: Before Permit Issuance (LNP-BEFORE-ISSUANCE) |
Resource: Permits Workflow Communications Event: Permit Application Updated |
Description: Initiates actions when a permit application is updated. Trigger: This event must be triggered from the workflow model. Actions:
Communication Event: Permit Application Updated (LNP-PERMIT-UPDATE) |
Resource: Permits Workflow Communications Event: Permit Contact Added to Application |
Description: Contacts are added to permit application. Trigger: Occurs when a new application has been submitted. All contacts added during the application intake are notified. It is recommended to include all contacts in the communication template. Actions:
Communication Event: Permit Contact Added to Application (LNP-CONTACT-ADD-TO-APP) |
Resource: Permits Workflow Communications Event: Permit Withdrawn |
Description: Applicant receives email or alert notification when a permit is withdrawn. Trigger: Click Withdraw Application on the Overview tab of the permit details, enter the reason, and click OK. Actions:
Communication Event: Permit Withdrawn (LNP-WITHDRAW-COMMUNICATION) |
Resource: Permits Workflow Communications Event: After Permit Application Submitted |
Description: After a permit application is submitted. Trigger: Applicant fills out an intake form and clicks Submit. Actions:
Communication Event: Before Permit Application Submitted (LNP-AFTER-SUBMIT) |
Resource: Permits Workflow Communications Event: Before Permit Application Submitted |
Description: Before a permit application is submitted. Trigger: Applicant fills out an intake form and prior to the user clicking Submit. Actions:
Communication Event: Before Permit Application Submitted (LNP-AFTER-SUBMIT) |
Code Enforcement
The following table provides additional details for events related to code enforcement. The events are sorted by Resource.
Event |
Details |
---|---|
Resource: Code Enforcement Case Event: Case Created |
Description: The case is created. Trigger:
Actions:
Communication Event: Case Created (CE_CASE_CREATED) |
Resource: Code Enforcement Case Event: Case Location Updated |
Description: The location of the case is updated. Trigger:
Actions:
Communication Event: Case Location Updated (CE_CASE_LOCATION_UPDATED) |
Resource: Code Enforcement Case Event: Case Status Updated |
Description: The status of the case is updated. Trigger: Whenever there is a case status update. The case status can be updated through inspections, from the case Overview tab, when issuing a citation, the result of a hearing, and so on. For example,on the case Overview tab click Edit for Case Status field. On the Update Status page, select a new status and reason and click Done. Actions:
Communication Event: Case Status Updated(CE_CASE_STATUS_UPDATED) |
Resource: Code Enforcement Case Document Event: Code Enforcement Case Document Attached |
Description: A responsible party attaches a document to a case. Trigger: In the case information on the attachments tab, a responsible party uploads a document. Actions:
Communication Event: Code Enforcement Case Document Attached (CE_CASE_ATTACHMENT_UPLOADED) |
Resource: Code Enforcement Incident Event: Incident Assigned to Officer |
Description: The incident is assigned to an officer. Trigger: On the Assign Code Officer page, select a code officer from the list, and click Save. Actions:
Communication Event: Incident Assigned to Officer (CE_INCIDENT_OFFICER_ASSIGNED) |
Resource: Code Enforcement Incident Event: Incident Assigned to Technician |
Description: The incident is assigned to a technician. Trigger: On the Assign Code Technician page, select a technician from the list and click Save. Actions:
Communication Event: Incident Assigned to Technician (CE_INCIDENT_TECHNICIAN_ASSIGNED) |
Resource: Code Enforcement Incident Event: Incident Location Updated |
Description: The location of the incident is updated. Trigger: On the Property Information tab for the Incident, select Edit for Incident Address field, update the address on the Property Information page and save. Actions:
Communication Event: Incident Location Updated (CE_INCIDENT_LOCATION_UPDATED) |
Resource: Code Enforcement Incident Event: Incident Priority Updated |
Description: The priority of the incident is updated. Trigger: On the incident Overview page, update the priority field value and save. Actions:
Communication Event: Incident Priority Updated (CE_INCIDENT_PRIORITY_UPDATED) |
Resource: Code Enforcement Incident Event: Incident Status Updated |
Description: The status of the incident is updated. Trigger: Numerous triggers, including when there is an update on the incident status by scheduling an inspection, an inspection resulting in a case, an incident is closed, and so on. Actions:
Communication Event: Incident Status Updated (CE_INCIDENT_STATUS_UPDATED) |
Resource: Responsible Party for Case Event: Responsible Party's Case Access Updated |
Description: Responsible party's online access to case is approved or denied. Trigger: When a public user requests access and the agency approves that request using the Responsible Party tab for the case or through workflow. Actions:
Communication Event: Responsible Party's Case Access Updated (CE-RP-REQ-UPDATE) |
Planning and Zoning
The following table provides additional details for events related to planning and zoning. The events are sorted by Resource.
Event |
Details |
---|---|
Resource: Activity Tracking Event: Planning Activity Updated |
Description: Indicates that an activity is updated. Trigger: Updating the Activity Status or Due Date field on the Activity Tracking list page, and click Save. Actions:
Communication Event: Planning Activity Updated (COM-ACT-UPDATE) |
Resource: Hearing Notification Event: Hearing Appealed |
Description: Notifies that an appeal is submitted for the public hearing. Trigger: On the Request Appeal page, provide the required information and click the Confirm and Pay button. Actions:
Communication Event: Hearing Appealed (PZ-HRGS-APPEAL-NOTIFY) |
Resource: Hearing Notification Event: Hearing Canceled |
Description: Notifies that the public hearing is canceled. Trigger: An application previously inserted into the calendar on the Hearing Scheduler has the hearing date changed using the Cancel action. Actions:
Communication Event: Hearing Canceled (PZ-HRGS-SCHD-CANCEL) |
Resource: Hearing Notification Event: Hearing Decision Changed |
Description: Notifies that the public hearing decision is updated. Trigger: On the Update Decision page, select a value from the Decision drop-down list, and click Save. Actions:
Communication Event: Hearing Decision Changed (PZ-HRGS-DECISION-CHANGED) |
Resource: Hearing Notification Event: Hearing Re-scheduled |
Description: Notifies that there is a change in the date of the public hearing. Trigger: An application previously inserted into the calendar on the Hearing Scheduler has the hearing date changed using the Reschedule action. Actions:
Communication Event: Hearing Re-scheduled (PZ-HRGS-SCHD-RESCHEDULE) |
Resource: Hearing Notification Event: Hearing Schedule Finalized |
Description: Notifies that the public hearing is scheduled on a finalized date. Trigger: An application has been added to the calendar on the Hearing Scheduler page with a Schedule Status of Final, a previously added application has the Schedule Status updated to Final, or the status is changed using the Finalize action. Actions:
Communication Event: Hearing Schedule Finalized (PZ-HRGS-SCHD-FINAL) |
Resource: Hearing Notification Event: Hearing Scheduled Tentatively |
Description: Notifies that the public hearing is scheduled on a tentative date. Trigger: An application has been added to the calendar on the Hearing Scheduler page with a Schedule Status of Tentative. Actions:
Communication Event: Hearing Scheduled Tentatively (PZ-HRGS-SCHD-TENTATIVE) |
Resource: Planning Application Document Event: Planning Application Document Attached |
Description: Notifies agency staff when the applicant uploads a planning application document. Trigger: An applicant has uploaded an attachment to a planning application or a preapplication. Actions:
Communication Event: Planning Application Document Attached (PNZ_ATTACHMENT_UPLOADED) |
Resource: Planning Application Plan Review Document Event: Planning Application Document Attached for Plan Review |
Description: Notifies agency staff when the applicant uploads a planning application document for plan review. Trigger: An applicant has uploaded an attachment to a planning application or a preapplication. Actions:
Communication Event: Planning Application Document Attached for Plan Reviewers (PNZ_ATTACHMENT_PR_UPLOADED) |
Resource: Planning Missing Document Event: Planning Missing Document |
Description: Indicates that a planning application step is missing a required document. Trigger: Application steps or workflow events including Application Submittal, Application Acceptance, and Application Complete, depending on agency configuration. For more information, see Setting Up Required Documents. Actions:
Communication Event: Planning Missing Document (PZ_REQUIRED_DOCUMENT) |
Resource: Planning and Zoning Application Event: Planner Assigned |
Description: A planner is assigned for the application. Trigger: When a planner is assigned from the Overview page of the planning application details page, or on the planner worklist Unassigned Planners tab. Actions:
Communication Event: Planner Assigned (PNZ-ASSIGN-PLANNER) |
Resource: Planning and Zoning Application Event: Planner Reassigned |
Description: A planner is reassigned for the application. Trigger: When a planner is reassigned from the Overview page of the Planning Application Details page, or on the Planner Worklist Unassigned Planners tab. Actions:
Communication Event: Planner Reassigned (PNZ-REASSIGN-PLANNER) |
Resource: Planning and Zoning Application Contacts Event: Planning and Zoning Additional Contact Added |
Description: Additional contact added to a planning application or preapplication. Trigger: Click Add New Contact in the Additional Contacts grid on the Contacts page in planning application details, and either select an existing contact or create a new one. Actions:
Communication Event: Planner Assigned (PNZ-ASSIGN-PLANNER) |
Resource: Planning and Zoning Expiration Communication Event: About to Expire Planning and Zoning Application |
Description: A planning and zoning application is about to expire. Trigger: The planning and zoning application is about to exceed the set expiration duration. Actions:
Communication Event: About to Expire Planning and Zoning Application (PNZ-APP-ATE-EXPIRY-001) |
Resource: Planning and Zoning Expiration Communication Event: About to Expire Pre-application |
Description: A planning and zoning pre-application is about to expire. Trigger: The planning and zoning pre-application is about to exceed the set expiration duration. Actions:
Communication Event: About to Expire Pre-application (PNZ-PREAPP-ATE-EXPIRY-001) |
Resource: Planning and Zoning Expiration Communication Event: Expired Planning and Zoning Application |
Description: A planning and zoning application has expired. Trigger: The planning and zoning application has exceeded the set expiration duration. Actions:
Communication Event: Expired Planning and Zoning Application (PNZ-APP-EXPIRED-001) |
Resource: Planning and Zoning Expiration Communication Event: Expired Pre-application |
Description: A planning and zoning pre-application has expired. Trigger: The planning and zoning pre-application has exceeded the set expiration duration. Actions:
Communication Event: Expired Pre-application (PNZ-PREAPP-EXPIRED-001) |
Resource: Planning and Zoning Workflow Communications Event: Before Planning and Zoning Application Submitted |
Description: Contacts are added to preapplication or planning application during the application intake form. When submitted. Trigger: Occurs before a planning and zoning application is submitted. Actions:
|
Resource: Planning and Zoning Workflow Communications Event: Planning and Zoning Contact Added to Application |
Description: Contacts are added to preapplication or planning application during the application intake form. When submitted. Trigger: Occurs when a new application has been submitted. All contacts added during the application intake are notified. It is recommended to include all contacts in the communication template. Actions:
Communication Event: Planning and Zoning Contact Added to Application (PZ-CONTACT-ADD-TO-APP) |
Resource: Planning and Zoning Workflow Communications Event: Planning Application and Pre-Application Updated |
Description: Initiates actions when a planning application or a preapplication is updated. Trigger: This event is triggered by the workflow model. Actions:
Communication Event: Planning Application and Pre-Application Updated (PZ-PLANNING-UPDATE) |
Resource: Planning and Zoning Workflow Communications Event: Planning Application Canceled |
Description: Initiates action when a planning application is canceled. Trigger: This event is triggered when the planning application is canceled from the Planning application list or Planning Details Overview page. Actions:
Communication Event: Planning Application Canceled (PNZ-CANCEL) |
Resource: Planning and Zoning Workflow Communications Event: Planning Pre-Application Canceled |
Description: Initiates action when a planning preapplication is canceled. Trigger: This event is triggered when the planning preapplication is canceled from the Planning list or Overview page. Actions:
Communication Event: Planning Pre-Application Canceled (PNZ-PREAPP-CANCEL) |
Resource: Planning Plan Review Event: Planning Plan Review Completed or Canceled |
Description: Indicates that the planning plan review is completed or canceled. Trigger: When the last reviewer provides a decision status for a plan review cycle, it is automatically closed. Upon closing, the overall review status changes to Complete. Or, on the Plan Reviews page, click the Cancel Review Cycle button to cancel a plan review cycle that is active. Actions:
Communication Event: Planning Plan Review Completed or Canceled (PNZ_MPR_REVIEW_COMPLETED) |
Resource: Planning Plan Review Event: Planning Plan Review Finalized |
Description: Indicates that the planning plan review is finalized. Trigger: Click Finalize Session for the plan review session in Bluebeam Studioâ„¢. Actions:
Communication Event: Planning Plan Review Finalized (PZ-HRGS-SCHD-FINAL) |
Resource: Planning Plan Review Event: Planning Plan Review Ready To Finalize |
Description: Indicates that the planning plan review is ready to finalize. Trigger: Click Save after the last reviewer provides a decision or the review is marked N/A (not applicable), and it is an electronic review. Actions:
Communication Event: Planning Plan Review Ready To Finalize (PNZ_PR_READY_TO_FINALIZE) |
Resource: Pre-Application Meeting Request Notification Event: Planning Application Meeting Invitee Added |
Description: Notifies that the invitee has been added to the planning meeting. Trigger: An invitee has been added to the invitee list for the planning application meeting and saved. Actions:
Communication Event: Planning Application Meeting Invitee Added (PZ-NA-MEETSCH-INV-001) |
Resource: Pre-Application Meeting Request Notification Event: Planning Application Meeting Rescheduled |
Description: Notifies that the planning application meeting is rescheduled on a tentative date. Trigger: The meeting for the planning application has been moved to a different date on the calendar and saved. Actions:
Communication Event: Planning Application Meeting Rescheduled (PZ-NA-MEETRESCH-001) |
Resource: Pre-Application Meeting Request Notification Event: Planning Application Meeting Canceled |
Description: Notifies that the planning application meeting is canceled. Trigger: On the Planning Application details page, select the Meetings tab for the planning application. Click Cancel for a meeting in the list. Actions:
Communication Event: Planning Application Meeting Canceled (PZ-NA-MEETCAN-001) |
Resource: Pre-Application Meeting Request Notification Event: Planning Application Meeting Remove Invitees |
Description: Notifies that the invitee has been removed from the meeting. Trigger: Invitees previously on the invite list are removed, and the update has been saved. Actions:
Communication Event: Planning Application Meeting Remove Invitees (PZ-NA-MEETREM-001) |
Resource: Pre-Application Meeting Request Notification Event: Planning Application Meeting Scheduled |
Description: Notifies that the planning application meeting is scheduled on a tentative date. Trigger: A meeting has been scheduled on the calendar. Actions:
Communication Event: Planning Application Meeting Scheduled (PZ-NA-MEETSCH-001) |
Resource: Pre-Application Meeting Request Notification Event: Pre-Application Meeting Canceled |
Description: Notifies that there is a change in the planning application meeting date. Trigger: An update has been made to the meeting and saved. Actions:
Communication Event: Planning Application Meeting Updated (PZ-NA-MEETUPD-001) |
Resource: Pre-Application Meeting Request Notification Event: Pre-Application Meeting Canceled |
Description: Notifies that the preapplication meeting is canceled. Trigger: On the Planning Application details page, select the Meetings tab for the planning preapplication. Click Cancel for a meeting in the list. Actions:
Communication Event: Pre-Application Meeting Canceled (PZ-PREAPP-MEETCAN-001) |
Resource: Pre-Application Meeting Request Notification Event: Pre-Application Meeting Remove Invitees |
Description: Notifies that the invitee has been removed from the meeting. Trigger: Remove a row in the invitees list for a meeting. Actions:
Communication Event: Pre-Application Meeting Remove Invitees (PZ-PREAPP-MEETREM-001) |
Resource: Pre-Application Meeting Request Notification Event: Pre-Application Meeting Rescheduled |
Description: A pre-application meeting is rescheduled on a tentative date. Trigger: A previously scheduled pre-application meeting's scheduled date or time has been changed and saved. Actions:
Communication Event: Pre-Application Meeting Remove Invitees (PZ-PREAPP-MEETREM-001) |
Resource: Pre-Application Meeting Request Notification Event: Pre-Application Meeting Scheduled |
Description: Notifies that the pre-application meeting is scheduled on a tentative date. Trigger: Click the Schedule button on the meeting request page. Actions:
Communication Event: Pre-Application Meeting Scheduled (PZ-PREAPP-MEETSCH-001) |
Resource: Pre-Application Meeting Request Notification Event: Pre-Application Meeting Updated |
Description: Notifies that there is a change in the preapplication meeting date. Trigger: Update a scheduled meeting and save your changes. Actions:
Communication Event: Pre-Application Meeting Updated (PZ-PREAPP-MEETUPD-001) |
Resource: Pre-Application Meeting Request Notification Event: Pre-Application Meeting Invitee Added |
Description: Notifies that the invitee has been added to the planning meeting. Trigger: Invitee has been added to the invitees list for the preapplication meeting. Actions:
Communication Event: Planning Application Meeting Invitee Added (PZ-NA-MEETSCH-INV-001) |
Resource: Planning and Zoning Workflow Communications Event: Planning Application Withdrawn |
Description: Applicant receives email or alert notification when a planning application is withdrawn. Trigger: This event is triggered when the planning application is withdrawn from the Planning application list or Planning Details Overview page. Actions:
Communication Event: Planning Application Withdrawn (PNZ-WITHDRAW) |
Resource: Planning and Zoning Workflow Communications Event: Planning Pre-Application Withdrawn |
Description: Applicant receives email or alert notification when a planning preapplication is withdrawn. Trigger: This event is triggered when the planning application is withdrawn from the list or overview page. Actions:
Communication Event: Planning Pre-Application Withdrawn (PNZ-PREAPP-WITHDRAW) |
Resource: Planning and Zoning Workflow Communications Event: After Planning and Zoning Application Submitted |
Description: After a planning and zoning application is submitted. Trigger: Applicant fills out an intake form and clicks Submit. Actions:
Communication Event: After Planning and Zoning Application Submitted (PNZ-AFTER-SUBMIT) |
Business Licenses
The following table provides additional details for events related to business licenses. The events are sorted by Resource.
Event |
Details |
---|---|
Resource: Business License Inspection Event: Business License Final Inspection Passed |
Description: Indicates that the final inspection is complete with a passing result. Trigger: For a final inspection, click Submit on the Inspection Result page. Actions:
Communication Event: Business License Final Inspection Passed (LIC-FINALINSP-001) |
Resource: Business License Inspection Event: Business License Inspection Canceled |
Description: Indicates that an inspection is canceled. Trigger: Select Cancel Inspection for the inspection. An inspection can be canceled from the inspections console, the Inspections tab in the transaction details, or from the inspection request. Actions:
Communication Event: Business License Inspection Canceled (LIC-INSPCANC-001) |
Resource: Business License Inspection Event: Business License Inspection Complete |
Description: Notification sent to applicants when final inspection results have been determined. Trigger: Click Submit on the Inspection Result page or from Inspection Details page within the Mobile Inspector app. Actions:
Communication Event: Business License Inspection Complete (LIC-INSPCOMP-001) |
Resource: Business License Inspection Event: Business License Inspection ETA Updated |
Description: Indicates that the estimated time of arrival for a scheduled inspection is updated. Trigger: From the Actions menu in the Oracle Inspector mobile app, select Update ETA. On the Estimated Time of Arrival page, select a new time, and click Save. Actions:
Communication Event: Business License Inspection ETA Updated (LIC-INSPETAUPDATE-001) |
Resource: Business License Inspection Event: Business License Inspection Requested |
Description: An inspection is created. Trigger: Select Add Inspection from the business license activity pages or the Inspections console page, provide the required information, and click Submit on the Inspection request page. This can occur also from the mobile application and IVR. Actions:
Communication Event: Business License Inspection Requested (LIC-INSPREQ-001) |
Resource: Business License Inspection Event: Business License Inspection Rescheduled |
Description: Indicates that an inspection is rescheduled. Trigger: Click Reschedule for a currently scheduled inspection, determine a new time, click Select, and click Submit. An inspection can be rescheduled from the inspections console for agency staff, the Inspections list page for registered public users, the Inspections tab in the transaction details, or from the inspection request. Actions:
Communication Event: Business License Inspection Rescheduled (LIC-INSPRESCH-001) |
Resource: Business License Inspection Event: Business License Inspection Postponed |
Description: Indicates that an inspection is postponed. Trigger: Select Postpone for the inspection. An inspection can be postponed from the Inspections console page for agency staff, the Inspections tab in the transaction details, or from the inspection request. Registered public users can only postpone inspections if allowed at the agency-level in the permit and business license options. Actions:
Communication Event: Business License Inspection Postponed (LIC-INSPPOSTPONE-001) |
Resource: Business License Inspection Event: Before Business License Inspection Saved |
Description: Before an inspection is saved. Trigger:
Actions:
Communication Event: Before Business License Inspection Saved (LIC-INSPRSAVE-001) |
Resource: Business License Inspection Event: Business License Inspection Scheduled |
Description: Indicates that an inspection is scheduled. Trigger: For a newly added inspection, click Select a Time, determine a time slot, click Select, and click Submit. An inspection can be scheduled from the inspections console, the Inspections tab in the transaction details, or from the inspection request. Actions:
Communication Event: Business License Inspection Scheduled (LIC-INSPSCH-001) |
Resource: Business License Inspection Document Event: Business License Document Attached for Inspection Supervisor |
Description: Applicant attaches a document for the inspection supervisor. Trigger: Click Add on Attachments page in the transaction details, select a document to upload, and click Upload on the Add Attachments dialog box. Actions:
Communication Event: Business License Document Attached for Inspection Supervisor (LIC_ATTACHMENT_SUP_UPLOADED) |
Resource: Business License Inspection Document Event: Business License Document Attached for Inspector |
Description: Applicant attaches a document for the inspector. Trigger: Click Add on Attachments page in the transaction details, select a document to upload, and click Upload on the Add Attachments dialog box. Actions:
Communication Event: Business License Document Attached for Inspector (LIC_ATTACHMENT_INS_UPLOADED) |
Resource: Business License Missing Document Event: Business License Missing Document |
Description: Indicates that a business license application step is missing a required document. Trigger: Application steps or workflow events including Application Submittal, Application Issuance, Application Acceptance, Final Inspection, and Application Complete, depending on agency configuration. For more information, see Setting Up Required Documents. Actions:
Communication Event: Business License Missing Document (LIC_REQUIRED_DOCUMENT) |
Resource: Business License Activity Event: Before Business License Issuance |
Description: Runs before the Issue Business License human task in the workflow process. Trigger: Runs if the PSC_BRF_EVENT_CODE custom property is specified for the Issue Business License workflow process task. Actions:
Communication Event: Before Business License Issuance (BL-BEFORE-ISSUANCE) |
Resource: Business License Workflow Communication Event: Business License Application Canceled |
Description: Indicates that a business license application is canceled. Trigger: This event is triggered when a business license application is canceled. Actions:
Communication Event: Business License Inspection Application Canceled (BL-CANCEL) |
Resource: Business License Workflow Communication Event: Business License Consultation Application Canceled |
Description: Indicates that a consultation application is canceled. Trigger: This event is triggered when a business license consultation application is canceled from the list or overview page. Actions:
Communication Event: Business License Consultation Application Canceled (BL-CON-CANCEL) |
Resource: Business License Workflow Communications Event: Business License Application Withdrawn |
Description: Applicant receives an email or alert notification when a business license application is withdrawn. Trigger: This event is triggered when the business license application is withdrawn from the list or overview page. Actions:
Communication Event: Business License Inspection Application Withdrawn (BL-WITHDRAW) |
Resource: Business License Workflow Communications Event: Business License Consultation Application Withdrawn |
Description: Applicant receives an email or alert notification when a business license consultation application is withdrawn. Trigger: This event is triggered when the business license consultation application is withdrawn from the list or overview page. Actions:
Communication Event: Planning Pre-Application Withdrawn (BL-CON-WITHDRAW) |
Resource: Business License Activity Event: After Business License Application Submitted |
Description: After a business license application is submitted. Trigger: An applicant fills out an intake form and clicks Submit. Actions:
Communication Event: After Business License Application Submitted (LIC-AFTER-SUBMIT) |
Common
The following table provides additional details for the common events. The events are sorted by Resource.
Event |
Details |
---|---|
Resource: Application Summary Event: Ad Hoc Application Event |
Note: Reserved for future use.
Description: General application event. Trigger: Varies. Actions:
Communication Event: Ad Hoc Application Event (ADHOC-WORKFLOW-EVENT-001) |
Resource: Delegation Notifications Event: Delegation Invitation Expired |
Note: Reserved for future use.
Description: The set time for the delegation invitation duration has expired. Actions:
Communication Event: Delegation Invitation Expired (COM-DLG-INVITATION-EXPIRE) |
Resource: Delegation Notifications Event: Delegation Invitation Updated for Privilege Decrease |
Note: Reserved for future use.
Description: A profile or transaction owner modifies a delegation invitation to decrease privileges. Actions:
Communication Event: Delegation Invitation Updated for Privilege Decrease (COM-DLG-INVITATION-MODIFY-PVGDEC) |
Resource: Delegation Notifications Event: Profile or Transaction Owner Ends Delegation |
Note: Reserved for future use.
Description: A profile or transaction owner ends delegation privileges. Actions:
Communication Event: Profile or Transaction Owner Ends Delegation (COM-DLG-END-PTO) |
Resource: Delegation Notifications Event: Delegate Ends Delegation |
Note: Reserved for future use.
Description: A delegate ends delegation privileges. Actions:
Communication Event: Delegate Ends Delegation (COM-DLG-END-DELEGATE) |
Resource: Delegation Notifications Event: Delegation Request Updated |
Note: Reserved for future use.
Description: A prospective delegate modifies a delegation request. Actions:
Communication Event: Delegation Request Updated (COM-DLG-REQUEST-MODIFY) |
Resource: Delegation Notifications Event: Delegation Request Declined |
Note: Reserved for future use.
Description: A profile or transaction owner declines a request to delegate. Actions:
Communication Event: Delegation Request Declined (COM-DLG-REQUEST-DECLINE) |
Resource: Delegation Notifications Event: Delegation Request Accepted |
Note: Reserved for future use.
Description: A profile or transaction owner accepts a request to delegate. Actions:
Communication Event: Delegation Request Accepted (COM-DLG-REQUEST-ACCEPT) |
Resource: Delegation Notifications Event: Delegation Request Expired |
Note: Reserved for future use.
Description: A delegation request expired. Actions:
Communication Event: Delegation Request Expired (COM-DLG-REQUEST-EXPIRE) |
Resource: Delegation Notifications Event: Delegation Invitation Declined |
Note: Reserved for future use.
Description: A prospective delegate declines an invitation. Actions:
Communication Event: Delegation Invitation Declined (COM-DLG-INVITATION-DECLINE) |
Resource: Delegation Notifications Event: Delegation Invitation Accepted |
Note: Reserved for future use.
Description: A prospective delegate accepts an invitation. Actions:
Communication Event: Delegation Invitation Accepted (COM-DLG-INVITATION-ACCEPT) |
Resource: Deposit Account Event: Account Established |
Description: Enables the agency to trigger a notification after establishing a deposit account. Trigger: A deposit account has been created and saved. Actions:
Communication Event: Account Established (BNP-DEPOSIT-ACCOUNT) |
Resource: Deposit Fund Event: Additional Funds |
Description: Enables the agency to trigger a notification when funds have to be deposited into deposit account. Trigger: Funds have been added to an existing deposit account. Actions:
Communication Event: Additional Funds (BNP-DEPOSIT-FUND) |
Resource: Deposit Received Event: Deposit Received |
Description: Enables the agency to trigger a notification after receiving a deposit. Trigger: Initial funds have been added to a deposit account. Actions:
Communication Event: Deposit Received (BNP-DEPOSIT-RECEIVED) |
Resource: Invite Delegation Notifications Event: Delegation Request |
Note: Reserved for future use.
Description: A prospective delegate requests delegation. Trigger: Varies. Actions:
Communication Event: Delegation Request (COM-DLG-REQUEST) |
Resource: Invite Delegation Notifications Event: Delegation Invitation |
Note: Reserved for future use.
Description: Profile or Transaction owner sends invitation to prospective delegate. Trigger: Varies. Actions:
Communication Event: Delegation Invitation (COM-DLG-INVITATION) |
Resource: Invite Delegation Notifications Event: Delegation Invitation Updated for Privilege Increase |
Note: Reserved for future use.
Description: A profile or transaction owner modifies a delegation invitation to increase privileges. Trigger: Varies. Actions:
Communication Event: Delegation Invitation Updated for Privilege Increase (COM-DLG-INVITATION-MODIFY-PVGINC) |
Resource: Payment by Transactions Event: Payment Received by Transactions |
Description: Enables the agency to trigger various actions upon the successful payment of fees for a transaction. Trigger: One or more fee payments have been received successfully. Actions:
Communication Event: Payment Received by Transactions (COM-PAYMENT-TRANSACTIONS) Note:
Update Workflow actions triggered by the Payment Received by Transactions event can send multiple fees at once for a transaction (if there are multiple fees), which you can see in rule logs. |
Resource: Payment History Event: Payment Received |
Description: Enables the agency to trigger a template that generates a successful payment notification. Trigger: A fee payment has been received successfully. Actions:
Communication Event: Payment Received (BNP-PAYMENT-RECEIPT) |
Resource: Refund Record Event: Refund Notice |
Description: Enables the agency to trigger a template that generates a successful payment notification. Trigger: A refund has been completed successfully by the agency. Actions:
Communication Event: Refund Notice (BNP_REFUND_NOTICE) |
Resource: User Access Changes Event: User Access Changed |
Description: A user or administrator has changed access to deposit account details. Trigger: Deposit account access is changed and saved. Actions:
Communication Event: User Access Changed (BNP-DEPOSIT-ACCESS) |
Resource: User Invite Event: User Invite |
Description: A user is invited to be an authorized user on a deposit account. Trigger: A user invite to access the deposit account is created and saved. Actions:
Communication Event: User Invite (BNP-DEPOSIT-INVITE) |
Resource: User Profile Notifications Event: User Profile Information Changed |
Description: Notifies a public user when the user's profile is updated by agency personnel. Trigger: The public user's profile was updated and saved. Actions:
Communication Event: User Profile Information Changed (PBL-PROFILE-INFO-CHANGED) |
Resource: User Profile Notifications Event: User Account Information Changed |
Description: Notifies a public user when the user's account is updated by agency personnel. Trigger: The agency updates a public user's account and saves. Actions:
Communication Event: User Account Information Changed (PBL-ACCOUNT-INFO-CHANGED) |