Processes

Now that you have business objects and object rules for information processing, you can add processes to conveniently handle incoming requests for information or operations. See section Processes as Links between User Interface and Business Logic for details.

To simplify user operations on specific objects, configure a process with that object as input. For instance, a transaction approval operation can be configured as a process ApproveTransaction that takes Transaction object as input and contains

Transaction.State='Approved'
DISPLAY MESSAGE 'Transaction has been completed' 

Processes with a single object as input are available on the corresponding object forms. Users can start these processes instead of manually changing the state of a pending transaction and submitting the form.

You can define processes without input objects, which are useful for creating new objects or performing operations without selecting a single object. These processes can be available to users as system operations from the main menu. For instance, an account opening process could be configured as follows:

ENTER NEW Account 

PRINT DOCUMENT AccountOpeningLetter 

VIEW Account 

Remember, processes shouldn’t process information. This is a job for object rules. See Configuration principles for more details.