The eCASE Procedure Designer allows you to create Procedures, or Event Handlers in your application that trigger processes designed to fulfill your business requirements. A procedure is a sequence of steps calling other procedures with branching and looping constructs. Procedures can be created to occur at certain events throughout the business process, or used to add unique logic to a UI or workflow.
The eCASE Procedure Designer allows you to create the following:
Type | Description |
|---|---|
Event Handlers | When an event occurs in eCASE, you have the ability to implement your own custom business logic using Event Handlers. The eCASE platform has Global, App and Case Events: · Global Events are platform level events. · App Events are app level events. · Case Events are raised at the case folder level. Please refer to the Event Handler Types section of this document for more detailed information on events. Event handlers are defined as a sequence of procedural steps using Procedure designer for a selected event and triggering moment. Event handlers do not return any values. It has pre-defined inputs. App developer cannot modify input/outputs for event handlers |
Procedures | Procedures implement custom business logic as a sequence of procedural steps: · You can define inputs and outputs for a procedure. · Procedures are callable from other procedures, event handlers, UI form rules, workflow robotic process or scheduled job |