Solved

How to stop and start System flows

  • 8 July 2021
  • 2 replies
  • 114 views

Badge +7

In indicium-Universal there is the possibility to run System-flows in the background
Sometimes these System flows will run for sometime, (minutes or longer).
If we need to stop the system (par example for deployments), I have to be sure there is no System-flow running. Therefor I need the following functions:


1.    A way to tell Indicum-universal not to start new tasks
Is the way to achieve this to run the task: ‘Disable schedule’ ?
http://acto-D-upgradetest-EVO.acto.nl/indicium/api/20/disable_schedule 
Input Parameters: 
 {
  "project_id": "EVO",
  "project_vrs_id": "7.05",
  "gui_appl_id": 26,
  "process_flow_id": "create_iam_user"
}


2.    A way to find out whether there is still a task running.
Can you tell me how to do this?


3.    A way to tell Indicum-universal to start new tasks
Is the way to achieve this to run the task: ‘reset_system_flow_schedule’ ?
http://acto-D-upgradetest-EVO.acto.nl/indicium/api/20/reset_system_flow_schedule 
Input Parameters: 
 {
  "project_id": "EVO",
  "project_vrs_id": "7.05",
  "gui_appl_id": 26,
  "process_flow_id": "process_import_financial_data"
}
 

icon

Best answer by Erwin Ekkel 9 July 2021, 09:58

View original

2 replies

Userlevel 6
Badge +16

IAM will provide you with this information and the option to do this. If you have sufficient rights you could indeed als odo this using Indicium. Another option, which is probably the easiest option, would be to deactivate indicium to stop system flows from running during the deployment. 

Badge +7

The way I now have implementated it is:

1) I make a list of all active system flows and save it

2) next i deactivate all system flow schedules

3) next i looks for running system flows

if a system flow start time is before the start time of the applicationpool of indicium-universal then it will be ignored.     

if a system flow is running it will wait MaxWaitTime (in seconds)

       note: a system flow may not be running longer then MaxRuntime (in days)

             meaning that if a system flow is running longer then MaxRuntime, it will be ignored

3a)       if system flow is still running, 

            it activates (the deactivated) system flow schedules

            it will end this script with an error

3b)       if no system flow is running anymore

            it will end this script normally​

 

I retreive the needed information from IAM with SQL statements and from IIS with powershell.

Reply