Falcon Space. Business processes

How business processes work

You can define a process as a sequence of trigger calls.

We check the event for each trigger. If the trigger returns result = true, the next trigger is called. If result=false, this trigger is scheduled to restart in N minutes. 

The action that the trigger performs can be any, for example: 

• creating a task (job)
• creating a notification)

An event check in a trigger is usually used to check the execution of a task associated with this trigger (but in General, it can be any check based on the state of the database). 

Important! The business process trigger has nothing to do with sql server triggers. SQL triggers are not being used. 

Implementing the business process

To automate a certain process, follow these steps: 

1. Create a process.
2. Describe its triggers. 
3. Implement SQL procedures for each trigger (state check and action execution).
4. Launch the trigger via the stored procedure as_jb_startProcess

Stored procedures for business processes

• as_jb_startProcess-starting a new process (creating an instance of the business process)
• as_jb_createJob-creates a new task (used in storage for triggers).
• as_nt_createNotification - creating notifications
• jb_example_check is an example of a stored procedure that is used as the basis for trigger stores. 

System stored procedures: 

• as_jb_checkCron (internal) - runs every minute via sync_minute to check planned triggers.& nbsp;
• as_jb_cron (internal) - adds a trigger to the crown
• as_jb_finishProcess (internal) - storage for completing the process
• as_jb_nextTrigger (internal) - used to search for and launch the next trigger in the process.

Note: 

The table jb_triggerCron records planned trigger launches. Their initiation is tested and run through the place sync_minute. 

For notifications, the default notification code is the OEWG (don't forget to add it).