Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
SecurID® Governance & Lifecycle Recipes
SecurID Governance & Lifecycle recipes is a collection of items, to help you get the most out of your product deployment. For example, a useful report with the SQL to implement or a way to achieve some advanced rule processing.
RSA IGL Services 101 blogs, help to explain various areas of RSA Identity Governance and Lifecycle, to ensure you are getting the most out of the product and following recommended practices. We hope to show you lots of great features, tips and tricks that you may not have been aware of!
This blog provides a high level index and summary of each workflow node available, taken from v7.1x of RSA IGL. As we dive into more detail of each node, we will provide a link below, to click and get more info. For example, please click "Milestone" in the table below.
If there is a specific node you would like to know more about, please let us know in the comments below
Workflow Node Summary
The workflow editor includes processing nodes common to and also specific to request, approval, fulfillment, and escalation workflows. Nodes are the building blocks you use to create and modify workflows. This following table lists nodes that you can use in request, approval, fulfillment, and escalation workflows.
Used to define a activity for a change request.
Used to define an approval for a change request.
Used to allow change request items to be approved as groups at the same level.
Cancel Change Request
Used to generate amilestone to cancel the entire change request processed by the workflow and revert all changes completed in the change request, reject the entire change request processed by the workflow, or put the change request in an error state.
Used in an escalation workflow to mark work assigned to a user (through an approval or activity) as completed.
Specifies the type of admin error to create for an administrator.
Evaluates a condition(s) based on a true or false result for outgoing transitions to an action or stop delimiter based on whether or not the condition exists.
Suspends a workflow temporarily based on date criteria. The date could be a specific date, the change request fulfillment date, a system calculated date relative to current time, the result of a java method that returns a date, or the result of a SQL query resulting in a date.
Used to define an approval for a change request generated from a form.
Used to define a fulfillment for a change request generated from a form.
Invokes a Java class to fulfill changes in a request.
Used to allow change request items to be fulfilled as groups at the same level.
Get Remaining Seconds
Used to store how much time remains for a calculated due date, performs some escalation outside of the assigned user’s control, and then updates the due date for the assigned user based on the earlier recorded remaining time.
Provides an interface to a Java method passing any parameters and returning a true/false result you can incorporate into a workflow.
The Java node, can evaluate conditions and perform actions in a workflow required for an approval and to initiate completion of an activity.
Note that if you use the Java node in a workflow or use the Java tag in workflow forms, you should place custom classes or jars in one of the following directories:
Provides high-level status information about a workflowmilestone you want displayed in a change request.
Returns the next value for a given job level workflow variable. If no value is returned (the last value was previously retrieved), the node returns false, which can be tested on an outgoing transition. If a valid value is returned, a true return code is provided. This node is typically used to iterate through an array of values to get the next value in the array..
Used to complete a provisioning command in a data source for a particular business source.
Used to assign an approval or activity to another user.
Used to generate an email notification prompting a user to retrieve a password that has been reset for the user.
REST Web Service *
Invokes a REST call to an endpoint. The responses and results from the calls are stored in the workflow variables based on the configuration in the node. This information can be used in a workflow’s decision logic.
The node supports:
GET and POST methods
XML and Properties response types
Parsing of the response using XPath and RegEx expressions.
Generates a report configured for the node in the workflow.
Used to generate a user access review associated with the node.
Generates email you want from the workflow. It supports the use of workflow variables or runtime workflow information to specify the To/From portions of the email.
Creates or updates a job level workflow variable(s) using the value(s) provided. The value can be a literal or use other workflow variables that are evaluated at the time the node is executed
SOAP Web Service *
Invokes a SOAP call to an endpoint. The responses and results from the calls are stored in the workflow variables based on the configuration in the node. This information can be used in a workflow’s decision logic.
The node supports:
Generic MIME Header
SOAP based XML response type
Parsing of the response using XPath and RegEx expressions
SQL Execute *
Runs an Insert/Update/Delete SQL command or a stored procedure where no result set is needed. It runs against the system database (AVDB). This node supports variables from the workflow with the SQL.
If you want to use an output parameter from your stored procedure (say, ‘success’ or “failure’ status) as a workflow variable for subsequent processing, you must define the stored procedure as a function and use the following syntax:
select sp_update_db (‘JOE’, ‘SMITH’, status) status from dual.
SQL Select *
To be updated.
Used as the start delimiter for a workflow.
Used as the stop delimiter for a workflow.
Calls/interjects another workflow as a subprocess of the current workflow. This node is useful in compartmentalizing work items or to improve maintenance or re-use of workflows.
Used to enter text into a workflow.
Used to connect two workflow nodes (processes) unidirectionally with a straight line. Transitions can be conditional or unconditional. A conditional transition occurs only if a particular condition is true. An unconditional transition can occur regardless of whether a condition is true. A transition is visually represented as an arrow.
Used to generates changes to reverse the requested changes that have been fulfilled.
Wait for Verification
Used to create a database watch for evidence of a change request fulfillment.
Note: Not all controls and types are available for every workflow type. Also, nodes with an asterisk symbol ( * ) are designed for advanced application. These nodes should be implemented carefully because poorly defined nodes can negatively impact workflow performance.