In order to add a Job Operation, you first must have a Job set up. To learn more about how to set up a Job, refer to the Creating a Job help article. 

The previously mentioned article shows you how to set up a Job, select a trigger, and add an email and in-app notification. With Job Operations you can configure additional automated actions to occur within Risk Cloud once your trigger is met. 

Operations are optional and not always necessary to accomplish what you want. 

Below are some examples of when you might want an Operation:

  • If you want to automatically create a new Record. Example use case: you have a Vendor Contract Management Application and once a Vendor contract is approved, you want the system to automatically create a new Vendor Assessment Record to continue the onboarding process. 

  • If you want to automatically update a discrete Field. Example use case: you have an assessment Record that you want to automatically require a mitigation if the Record is sent back from review step to the assessment in progress step.

  • Map existing Record to trigger. Example use case: when you create a risk Record and the Record moves to the repository step in the risk Workflow you want it to automatically be mapped to an assessment Record in the assessment Workflow.

Adding an Operation

To add an Operation to a Job, click on the pencil icon under the 'Operation' tab. Then click the style of Operation you would like to use

Selecting an Operation

Next you'll have to select the Operation type. Below are the 4 types of Operations available.

  • Create New and Map to Trigger - A new Record is created and mapped to the triggering Record. You can decide which Workflow and Step you want to create this new Record in and also choose the initial assignee and set the Due Date. Note that in order for the Record to be created, the Workflows must already be connected together.

  • Create New and Map to Existing - A new Record is created and mapped to an existing Record. In addition to all of the configuration options above, you can also decide the existing Record you want this new Record to be mapped to.

  • Map Existing to Trigger - An existing Record is mapped to the triggering Record. You can decide what the existing Record is that will get mapped to the triggering Record.

  • Update a Field - A Discrete Field (Due Date, Date Picker, Select, Multi-Select, Radio, Checkbox, Number) is updated. Select the Field you would like to be updated. Dependent on the Field Type you have options for how to update the Field:

    • Select Fields and Radio Fields can be updated or cleared completely.

    • Date Fields can be updated relative to trigger date, relative to existing date in the Field, or cleared.

    • Multi-Select Fields and Checkbox Fields can have new values added, specific existing values removed, or all existing values removed.

    • Number Fields can be updated with a specific number, adjusted up or down by a specific number, or cleared completely.

The most commonly used Operations are Create New and Map to Trigger and Update a Field. Below are example use cases and configurations of these two common Operations.


Create New and Map to Trigger Use Case

You have an Enterprise Risk Management Application with two Workflows - Risks and Risk Assessments. You assess your Risks annually and would like LogicGate to automatically create a new Risk Assessment for every Risk 3 months before the Risk is due for review.

First you will need to setup a Due Date Job, then you can add the 'Create New and Map to Trigger' Operation. 

Next, in the 'Workflow (Mapped)' drop down, you will need to select the Workflow where you want this Record to be created in. For this example it would be the 'Risk Assessments' Workflow. Then you will need to select the Step you want to create it in.

The 'User' and 'Due Date' Fields are optional. If you want to, you can assign this newly created Risk Assessment Record to a user. Note: All Risk Assessments created from this Operation will always be assigned to this single user.

The 'Due Date' Field allows you to set a Due Date for this new Risk Assessment. You can set the Due Date to be X number of hours/days/weeks/months/years from the date the Risk Assessment was created (the date the Job executes for that Record).

For example, if I configure the 'Due Date' to be 3 months and the Risk Assessment was created on January 1st. Then the Due Date for the Risk Assessment would be set to April 1st.


Update a Field Use Case
You have an Incident Management Application and you would like to capture the date an Incident enters the 'Review' Step.

First you will need to setup a Moved Job, then you can add the 'Update a Field' Operation.

Next, you can choose the Field Type you want to update. 'System Field' will be the Due Date Field and 'Custom Field' will allow you to choose from all of the Date Picker Fields you have created in your Workflow.

Lastly, you will need to select the Field to update and define the parameters of the update.

Once this is done, be sure to save the job before exiting the modal.

Did this answer your question?