Setting Up Stop Process Actions
This topic describes how to prevent processes from being executed based on your business rule. For example, you can stop a final inspection from being created, scheduled, or assigned if fees are due for the permit.
The Stop Process action is supported for this Business Rules Framework event:
Event Attribute |
Value |
---|---|
Offering |
Permits |
Business Object |
Inspection |
Event Name |
Before Inspection Saved |
While the Business Rules Framework can be used to stop the creation or update of a final inspection when there is a permit fee balance due, other conditions can be evaluated based on the Criteria setup in the rule that can result in a Stop Action.
To configure a Stop Process action:
-
Expand the Criteria section of the Business Rules Details page.
For more information on setting up criteria, see Setting Up Business Rule Criteria.
-
Make sure your statements reference the applicable attributes in the business object.
-
Expand the Actions section of the Business Rules Details page.
-
Click Add.
-
From the Action Name drop-down list, select Stop Process.
-
Click Configure.
Enter the text to include in the message that displays to the user if the action is triggered.
In this example, the Stop Process action prevents the final inspection from being created, scheduled, or assigned, and it displays a message to alert the user in the following format:
The process has stopped due to this reason: {CUSTOM_MESSAGE_TEXT}.
Where {CUSTOM_MESSAGE_TEXT} is the text you enter in the Message Body field.
Note: The Stop Process action is triggered only during a request for a final inspection, or when a final inspection is being scheduled or assigned. It is not triggered during import, migration, or when an inspection is canceled or updated. Also, keep in mind that the Stop Process action isn’t triggered by requests sent from the Oracle Inspector mobile app, however requests sent from a browser running on a mobile device will trigger the Stop Process action.