Sample scenarios
You can use the Application Event System to automate various tasks in response to various situations. In each of the scenarios in this set of topics, the situation is described and then a proposed solution that involves application events, handlers, and triggers. These solutions are presented in a step-by-step format, as examples that you can learn from and possibly modify for your own use.
- To a certain extent, each scenario builds on the concepts and practices of previous scenarios, so the most effective way to use them is to work through them sequentially. However, each scenario is also self-contained and can be used independently of the others.
- To see a graphical representation for each flow as you work on it, you can use the button on the Event Handlers form. This button opens the Event Handler Diagram form, which you can use to view the flow of the event handler as well as access the Event Actions form to edit individual actions.
These scenarios are available:
Sending notifications
- Sample scenario 1: Notification of a new record - Adding a user
A simple notification is sent to a credit manager when a new customer is added to the database.
- Sample Scenario 2: Notification of Changes to an Existing Record - Changing the Credit Limit
The credit manager is notified by email that a customer’s credit limit has been changed and the new credit limit is specified.
- Sample Scenario 3: Notification that includes an Old Value
A group of inventory stockers are automatically notified whenever an item’s lot size changes. In the message that is sent, both the previous lot size and the new lot size are included.
Requesting approvals
- Sample Scenario 4: Approval for a New Record
A purchasing manager is prompted for approval whenever a new purchase order is requested.
- Sample Scenario 5: Requesting Approval by External Email for Changes to an Existing Record
A credit manager is prompted through an external email for approval of a change to a customer’s credit limit.
- Sample Scenario 6: Requesting Multiple and Complex Approvals
A purchasing manager is prompted for approval on a purchase order (PO) both of a change in status to Ordered and for the amount of the PO. If the PO is for an amount greater than $100,000, a supervisor is also prompted for approval. If the PO is for an amount greater than $1,000,000, two senior level executives must also approve the PO.
Modifying records
- Sample Scenario 7: Adding Information to a Record
A credit manager is prompted to provide a credit limit for a new customer by means of a response to a message.
Voting
- Sample Scenario 8: Voting for Various Choices
Several managers are prompted to approve an engineering change by means of a response to a message.
Localizing message contents
- Sample Scenario 9: Translating Captions in a Purchase Request
A message that contains localizable strings is created.
More advanced scenarios
- Sample Scenario 10: Opening a Session in a Remote Environment
A remote site or Mongoose-based application environment is accessed to retrieve data. The details of and procedure for this scenario are in the IDO Integration with External Applications section of the help.
- Sample Scenario 11: Cross-site Event Firing - Adding a Message to another Site's Inbox
A message is sent to another site’s Inbox form, using a GenericNotify event.