In this Process Automation tutorial, we will demonstrate how to trigger or run multiple workflows within one scope action.
If you have never created a Scope Action before, please refer to the below video and the Scope Action Creation Basics article for more information.
If the Scope Action module is located on COMPUTER-A, the scope module must look as follows:
The following screenshot represents the finished Action Modules tab. The Master Scope Action will contain a different action module for each Scope Action.
Process Automation Step 1 – Configure each Action Module in the Master Scope Action.
For each individual scope action, create the following action module in the Master Scope Action:
Process Name: This will be the location of the GovScopeActionWorker.exe (located in the Goverlan installation directory)
Example: C:\Program Files (x86)\GoverLAN v8\GovScopeActionWorker.exe (for x86 users remove the x86 from the Program Files path)
Process Argument String: This will be the Scope Action in question including its full path. (You can right click the Scope Action > Open Definition Directory, to confirm the exact location of your Scope Actions)
Example: C:\Users\vcruz\AppData\Roaming\Goverlan\Scope Actions v8\Report NTFS Permissions.gsa -opt:NoPrompt
Run As Type: 1 (This means that it will run as the console user, in this case since we selected the Goverlan Console machine, it will use the logged users credentials. Set this to the requirements of your network)
Wait for Completion: Set this value to True if the Scope Actions need to run sequentially. Set this value to false if the Scope Actions need to run simultaneously.
Wait Time Out(Seconds): Please enter a time in seconds for the Scope Action to complete. This depends on the nature of the scope action itself. Longer scope actions will need more time to complete.
Kill Process on Time Out: False
Hide Execution Window: True
Repeat Step 1 for each scope action that will participate in the Master Scope Action.
Process Automation Step 2 – Set the order of execution for each Action Module
Arrange the Action Modules in the order of execution: