Skip to content

Workflow Actions

There are several different actions you can include in your Lifecycle workflows. The possible actions are listed below, along with the types of workflows in which they can be used.

Approval Form

Approval Form is an action used when a workflow requires an approval or a rejection, typically from another user.

Approval Form is available for the following workflow types:

To configure an Approval Form step, from the New Action page:

  1. Select the Approval Form button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.
      2. Page: select the page to use in the approval form being created. Select Pages for more information. Selecting the preview icon presents the administrator with a preview of the page.
      3. Require comments: select Yes if end user comments are required.
      4. Require comments: select Yes if end user comments are required.
      5. Skippable approval: select Yes if the requester can perform the approval.

    • NOTIFICATIONS

      1. Approved email: select a notification template to send to the requester when the action requiring review is approved.
      2. Rejected email: select a notification template to send to the requester when the action requiring review is rejected.
      3. Performer notification email: select a notification template to send to the Approver to inform them that action is required. Selecting the preview icon next to any of these presents the administrator with a preview of the notification. Select Notifications for more information.

    • APPROVERS

      1. From the request: select The requester if the requestor of the action should perform the approval.
      2. From the requests profile: select either or both Profiles owner or Profiles contributors if these users should perform the approval.
      3. Users with NEProfile role: select any of the NEProfile application roles and any user within the selected role(s) can perform the approval.
      4. Users with Collaboration role: select any of the NEAccess application roles and any user within the selected role(s) can perform the approval.
      5. Contributors from another profile: select another profile to inherit the contributors/owners of that profile. Those contributors/owners of the that profile can perform the approval within this workflow.
      6. Selected contributor: select an attribute to inherit the profile owner or contributor of that attribute. Those contributors/owners of the that attribute can perform the approval within this workflow. Select Attributes for more information.
      7. Selected contributors managers: select an attribute to inherit the profile owner or contributor of that attribute. The assigned manager of the contributors/owners of the that attribute can perform the approval within this workflow.

  3. Select create

  4. The Approval Form action appears on the Workflows page

Ask Security Questions

Ask Security Questions is an action used to define the number of security questions a user must answer upon logging in as an additional authentication factor.

Ask Security Questions is available for the following workflow types:

Important

A "Set Security Questions" action must be included in the registration workflow for "Ask Security Questions" to be used in the login workflow.

  1. Select the Add Security Questions button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.
      2. Number of Questions: select the number of questions the user must answer. The maximum number to select is set by the number of security questions currently created.

    • AUTHENTICATION

      1. Authentication expiration: enter a valid number based on the selection of one of the following to set how often the user will need to perform that type of validation.

        1. Hours: selecting this value will require a user to re-authenticate after x number of hours
        2. Days: selecting this value will require a user to re-authenticate after x number of days
        3. Login attempts: selecting this value will require a user x number of failed attempts to authenticate before system lockout
        4. Always: selecting this value will require a user to always authenticate.

  3. Select create

  4. The Ask Security Questions action appears on the Workflows page.

Auto Assign

Auto Assign is an action used to automatically assign contributors to a profile.

Auto Assign is available for the following workflow types:

To configure an Auto Assign step, from the New Action page:

  1. Select the Auto Assign button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

    • ASSIGNMENT

      1. NEProfile roles: select any of the NEProfile application roles and any user within the selected role(s) will be automatically assigned as a contributor.
      2. NEAccess roles: select any of the NEAccess application roles and any user within the selected role(s) will be automatically assigned as a contributor.
      3. Contributors from another profile: select a profile search/select attribute to be completed in the workflow. When selected the contributors/owners of that profile will assigned as a contributor.

  3. Select create

  4. The Auto Assign action appears on the Workflows page

Close Session Action is an action used to close the current workflow session.

Close Session Action

Ends the workflow. Any actions in a workflow after the Close Session action won't be executed.

Close Session Action is available for the following workflow types:

To configure a Close Session Action step, from the New Action page:

  1. Select the Close Session Action button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

  3. Select create

  4. The Close Session action appears on the Workflows page

Collaboration Account

Collaboration Account is an action used to create a Collaboration user account for a profile.

Collaboration Account is available for the following workflow types:

  1. Select the Collaboration Account button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

    • ACCOUNT CREATION

      1. Username: select an available value builder to generate the username for this account. Refer to Value Builder for more information.
      2. Secondary username: select an available value builder to generate a secondary username for this account if the first username is not available.
      3. Store type: select if the user should be created as a directory or local account.
        1. If Directory is selected:
          • Directory: select the appropriate directory
          • Groups to assign to user: search and select the groups this user should be added to. Multiple groups can be added here.
        2. If Local is selected:
          • Roles to assign to the user: search and select the roles this user should be added to. Multiple roles can be added here.

    • PERFORMERS

      1. From the request: select The requester if the requestor is the user that should perform the action.
      2. From the requests profile: select either or both Profiles owner or Profiles contributors if these users should perform the action.
      3. Users with NEProfile role: select any of the NEProfile application roles and any user within the selected role(s) should perform the action.
      4. Users with NEAccess role: select any of the NEAccess application roles and any user within the selected role(s) should perform the action.
      5. Contributors from another profile: select a profile search/select attribute to be completed in the workflow. When selected the contributors/owners of that profile should perform the action.
      6. Selected contributor: select an attribute to inherit the profile owner or contributor of that attribute. Those contributors/owners of the that attribute should perform the action. Refer to Managing Attributes for more information.
      7. Selected contributors managers: select an attribute to inherit the profile owner or contributor of that attribute. The assigned manager of the contributors/owners of the that attribute should perform the action.

  3. Select create

  4. The Collaboration Account action appears on the Workflows page

Contributors

Contributors allows a user to manually assign owners or other contributors to a profile.

Contributors is available for the following workflow types:

To configure a Contributors step, from the New Action page:

  1. Select the Contributors button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

      2. Assignment options: select an option to control what the performer will assign: Owner, Contributor and/or roles.

        The options displayed are determined by the Role Filtering configuration for the profile type associated with this workflow.

    • NOTIFICATIONS

      1. Performer notification email: select a notification template to send to the approver to inform them that action is required. Selecting the preview icon presents the administrator with a preview of the notification. Select Notifications for more information.

    • PERFORMER

      1. From the request: select The requester if the requester of the action should perform the assignment.
      2. From the requests profile: select either or both Profiles owner or Profiles contributors if these users should perform the assignment.
      3. Users with NEProfile role: select any of the NEProfile application roles and any user within the selected role(s) will be able to perform the assignment.
      4. Users with Collaboration role: select any of the NEAccess application roles and any user within the selected role(s) should receive the notification.
      5. Contributors from another profile: select a profile search/select attribute to be completed in the workflow. When selected the contributors/owners of that profile will be able to perform the assignment.
      6. Selected contributor: select an attribute to inherit the profile owner or contributor of that attribute. Those contributors/owners of the that attribute will be able to perform the assignment. Select Attributes for more information.
      7. Selected contributors managers: select an attribute to inherit the profile owner or contributor of that attribute. The assigned manager of the contributors/owners of the that attribute will be able to perform the assignment.

  3. Select create

  4. The Contributors action appears on the Workflows page.

Create

Create is the action that stores all attributes collected during the workflow in the database to create a profile.

When multiple create actions are applied to a single workflow, additional create actions after the first act as update actions.

Create is available for the following workflow types:

To configure a Create step, from the New Action page:

  1. Select the Create button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

      2. Make the requester the default owner?: select Yes or No. Selecting Yes will set the requester as the default owner of the created profile if no owner is specified during the request process.

  3. Select create

  4. The Create action appears on the Workflows page

Duplicate Prevention

Duplicate Prevention is an action used to check the specified attribute(s) against existing profiles to find duplicates. If a duplicate is identified, the application prompts the requester to select that existing profile or create a new one from the request.

Duplicate Prevention is available for the following workflow types:

To configure a Duplicate Prevention step, from the New Action page:

  1. Select the Duplicate Prevention button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

    • DUPLICATE SETTINGS

      1. Attributes used to search for profile: search and select for the desired attributes. Multiple attributes can be added here.

    • NOTIFICATIONS

      1. Performer notification email: select a notification template to send to the requester to inform them of the duplicate. Selecting the preview icon presents the administrator with a preview of the notification. Select Notifications for more information.

      2. PERFORMERS

        1. From the request: select The requester if the requestor is the user that should perform the action.
        2. From the requests profile: select either or both Profiles owner or Profiles contributors if these users should perform the action.
        3. Users with NEProfile role: select any of the NEProfile application roles and any user within the selected role(s) should perform the action.
        4. Users with Collaboration role: select any of the NEAccess application roles and any user within the selected role(s) should perform the action.
        5. Contributors from another profile: select a profile search/select attribute to be completed in the workflow. When selected the contributors/owner of that profile should perform the action.
        6. Selected contributor: select an attribute to inherit the profile owner or contributor of that attribute. Those contributors/owners of the that attribute should perform the action. Select Attributes for more information.
        7. Selected contributors managers: select an attribute to inherit the profile owner or contributor of that attribute. The assigned manager of the contributors/owners of the that attribute should perform the action.

  3. Select create

  4. The Duplicate Prevention action appears on the Workflows page

Email Verification

Email Verification is an action used to initiate an email address verification process.

Establishing this in the workflow, sends the end user a code with an expiration time. The code is sent to the user’s email address and serves as verification that the user’s email address is valid.

Email Verification is available for the following workflow types:

  1. Select the Email Verification button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.
      2. Email expiration (minutes): enter the number of minutes that the code sent via email remains valid.

    • AUTHENTICATION

      1. Authentication expiration: enter a valid number based on the selection of one of the following to set how often the user will need to perform that type of validation.

        1. Hours: selecting this value will requires a user to re-authenticate after x number of hours
        2. Days: selecting this value will requires a user to re-authenticate after x number of days
        3. Login attempts: selecting this value will requires a user x number of failed attempts to authenticate before system lockout
        4. Always: selecting this value will require a user to always authenticate.

  3. Select create

  4. The Email Verification action appears on the Workflows page.

Fulfillment

Fulfillment is an action used when a workflow requires information from other users through the workflow.

Fulfillment is available for the following workflow types:

To configure a Fulfillment step, from the New Action page:

  1. Select the Fulfillment button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Page: select the page to use in the fulfillment process. Select Pages for more information. Selecting the preview icon presents the administrator with a preview of the page.
      2. Description: enter text to describe the purpose of this action.
      3. Require comments: select yes if end user comments are required.

    • NOTIFICATIONS

      1. Performer notification email: select a notification template to send to the fulfiller to inform them that action is required. Selecting the preview icon presents the administrator with a preview of the notification. Select Notifications for more information.

    • PERFORMER

      1. From the request: select The requester if the requestor of the action should perform the fulfillment action.
      2. From the requests profile: select either or both Profiles owner or Profiles contributors if these users should perform the fulfillment action.
      3. Users with NEProfile role: select any of the NEProfile application roles and any user within the selected role(s) can perform the fulfillment action.
      4. Users with Collaboration role: select any of the NEAccess application roles and any user within the selected role(s) can perform the fulfillment action.
      5. Contributors from another profile: select another profile to inherit the contributors/owners of that profile. Those contributors/owners of the that profile can perform the fulfillment action within this workflow.
      6. Selected contributor: select an attribute to inherit the profile owner or contributor of that attribute. Those contributors/owners of the that attribute can perform the fulfillment action within this workflow. Select Attributes for more information.
      7. Selected contributors managers: select an attribute to inherit the profile owner or contributor of that attribute. The assigned manager of the contributors/owners of the that attribute can perform the fulfillment action within this workflow.

  3. Select create

  4. The Fulfillment action appears on the Workflows page

Notification

Notification is an action used when a workflow requires sending an email to a particular recipient(s).

Notification is available for the following workflow types:

To configure a Notification step, from the New Action page:

  1. Select the Notification button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Email: select the template to use for the notification. Select Notifications for more information.
      2. Description: enter text to describe the purpose of this action.

    • RECIPIENTS

      1. Email addresses: enter the list of email addresses, separated by commas, that will receive this notification.
      2. Email attribute: select an attribute apply to the notification.
      3. From the request: select The requester if the requestor of the action should receive the notification.
      4. From the requests profile: select either or both Profiles owner or Profiles contributors if these users should receive the notification.
      5. Users with NEProfile role: select any of the NEProfile application roles and any user within the selected role(s) should receive the notification.
      6. Users with Collaboration role: select any of the NEAccess application roles and any user within the selected role(s) should receive the notification.
      7. Contributors from another profile: select another profile to inherit the contributors/owners of that profile. Those contributors/owners of the that profile should receive the notification.
      8. Selected contributor: select an attribute to inherit the profile owner or contributor of that attribute. Those contributors/owners of the that attribute should receive the notification. Select Attributes for more information.
      9. Selected contributors managers: select an attribute to inherit the profile owner or contributor of that attribute. The assigned manager of the contributors/owners of the that should receive the notification.

  3. Select create

  4. The Notification action appears on the Workflows page

Profile Check

Profile Check can be used to prevent duplicate profiles or to detect related profiles.

Profile Check is available for the following workflow types:

To configure a Profile Check step, from the New Action page:

  1. Select the Profile Check button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

    • PROFILE CHECKING

      1. Attributes used to search for profile: search and select attributes used to validate against.

      2. What should happen if an existing profile is found?: select either:

        • Perform this workflow against the profile thats found: if a profile is found that matches the attribute selected the existing profile is added to current request and the workflows is executed against the existing profile.
        • Create a relationship to the profile thats found: if a profile is found that matches the attribute selected then a relationship between the current profile and the existing profile.

  3. Select create

  4. The Profile Check action appears on the Workflows page

Registration Invitation

Registration Invitation is an action limited to customers who have purchased Collaboration. This action allows a user to send an invitation to a third-party to self-register in a Collaboration portal and would link the registration to the already created profile.

Registration Invitation is available for the following workflow types:

By default, registration invitations expire after 7 days. If a user receives another registration invitation during this time, the previous invitation automatically expires and they must register using the new link or code.

If an invitation expires, another invitation must be sent to the portal user before they can register.

To configure a Registration Invitation step, from the New Action page:

  1. Select the Registration Invitation button

  2. Specify the appropriate information in each field

    • INVITATION SETTINGS

      1. Registration Workflow: select the registration workflow from Collaboration.
      2. Portal: select the Collaboration Portal that the invite should include.
      3. Email Attribute: select an email address attribute.
      4. Email: select the Notification Template the invite should use.
      5. Wait for completion: select Yes to set the primary action to wait for the secondary action to complete.
      6. Wait until what action completes?: only available when Yes is selected. Select from the available list of actions. Caution: If No is selected, conflicts may arise

      7. INVITATION SESSION ATTRIBUTES

        • Attributes to send to the new request: search and select attributes to send from the current workflow session to the new workflow session.

      8. INVITATION WORKFLOW COMPLETION

        • Return the profile to this request: select Yes to send the profile created during the registration workflow to be sent back for further processing.
        • Attributes to receive back once complete: search and select attributes that should be returned once the secondary workflow completes.

      9. BASIC SETTINGS

        • Description: enter text to describe the purpose of this action.

      10. VALIDATION SETTINGS

        • Validate Completed Registration: selecting Yes, prevents invitations from being sent to an email address that belongs to a user that has already completed a registration workflow.
        • Validate In-Progress Registration: selecting Yes, prevents invitations from being sent to an email address that belongs to a user that has already has a pending registration workflow.

  3. Select create

  4. The Registration Invitation action appears on the Workflows page

Request Form

Request Form is an action used when a workflow requires a page for the end user that allows information to be entered about the profile being created. A request form is commonly the first step in a workflow where the end user’s interaction is required to initiate a process.

Request Form is available for the following workflow types:

To configure a Request Form step, from the New Action page:

  1. Select the Request Form button

  2. Specify the appropriate information in each field

    • Page: select the page to use in the request form being created. Select Pages for more information. Selecting the preview icon presents the administrator with a preview of the page.
    • Description: enter text to describe the purpose of this action.
    • Require Comments: select Yes if end user comments are required.

  3. Select create

  4. The Request Form action appears on the Workflows page.

Reset Password

Prompts the user to provide a new password for their portal account.

Portal users' passwords must meet the following criteria:

  • The password must be 8 or more characters long.

  • It must contain at least 3 out of these 4 types of characters:

    • Lowercase letters
    • Uppercase letters
    • Numeric characters
    • Special characters

Note

This action is included in all Collaboration Password Reset workflows and can't be modified or deleted.

REST API

REST API is an action used to send or receive data from and to other applications.

REST API is available for the following workflow types:

If your REST API request takes longer than 60 seconds to complete during a workflow's execution, the action will time out and the workflow will fail.

To configure a REST API step, from the New Action page:

  1. Select the REST API button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

    • AUTHENTICATION

      1. Auth Type: select from the following options

        • None: (default), requires no additional information.
        • Basic: enter the Username and Password the endpoint recognizes.

        • Oauth2: enter the appropriate values for each field:

          1. Access token url
          2. Client id
          3. Client secret
          4. Scope

        • Oauth2 w/ Mutual TLS: enter the appropriate values for each field:

          1. Access token url
          2. Access token server certificate (choose a file)
          3. Client id
          4. Scope
          5. Client certificate (choose a file)
          6. Client key (choose a file)

    • REQUEST

      1. Http verb: select from one of the following options

        • Get: attempts to request data from the endpoint.
        • Post: attempts to create a new record at the endpoint.
        • Patch: attempts to update a specified record at the endpoint.
        • Put: attempts to completely replace a record at the endpoint.
        • Delete: attempts to delete a specified record at the endpoint.

      2. End point: enter in the full URL of the API to send the request.

      3. Headers: select the + Add header button. Enter the Header key and Value for each header added.
      4. Json body: define the expected HTTP body using JSON. Liquid can be used here to pull data from the requester or the profile that is being worked on in the workflow.

    • RESPONSE

      1. Mappings: to store any of the response data, define the mapping here, by searching and selecting an Attribute and specifying the Path to the key that has the desired value.

  3. Select create

  4. The REST API action appears on the Workflows page.

Review Form

Review Form is an action used when the workflow requires review from the original requester. This is like a final review before submitting the request.

Review Form is available for the following workflow types:

To configure a Review Form step, from the New Action page:

  1. Select the Review form button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Page: select the page to use in the review process. Select Pages for more information. Selecting the preview icon presents the administrator with a preview of the page.
      2. Description: enter text to describe the purpose of this action.
      3. Require comments: select yes if end user comments are required.

    • NOTIFICATIONS

      1. Performer notification email: select a notification template to send to the requestor to inform them that action is required. Selecting the preview icon presents the administrator with a preview of the notification. Select Notifications for more information.

  3. Select create

  4. The Notification action appears on the Workflows page

Run Workflow

Run Workflow is an action used to trigger another workflow or “sub-routines” from the current workflow.

Run Workflow is available for the following workflow types:

To configure a Run Workflow step, from the New Action page:

  1. Select the Run workflow button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

    • NEW REQUEST

      In some instances, when the sub-workflow is triggered, administrators can choose to send information from the current request for the secondary workflow to operate against.

      1. Profile to send to new request: select one of the available profile options

        • None: select to prevent the requests profile being set to anything else.
        • Current Profile: select to set the requests profile to the current pending profile from the primary workflow.

        • Profile(s) from attribute: select to set the requests profile to a related profile based on an attribute.

          • What attribute?: select attribute

        • All related profiles by type: select to set the requests profile to a one-to-many relationship.

          • What profile type?: select the profile type

      2. Attributes to send to the new request: search and select the attribute(s) from the current workflow session to update in the new workflow session.

        1. For each attribute set the following

          • Operation: select one of the following:

            1. set value
            2. remove value

          • Send: select one of the following (options may be different based on attribute type):

            1. another attributes value
            2. another profiles value
            3. another users account value
            4. another users profile value
            5. requestors account value
            6. requestors profile
            7. requestors profile value
            8. requests value
            9. static value
            10. value builder

      If a date attribute is selected and the operator selected is "more than," "less than," or exactly," 2 more additional fields called Days and Timeframe will appear.

    • SUBWORKFLOW COMPLETION

      1. Attributes to receive back once complete: when a secondary workflow competes, administrators can request attributes back from the secondary workflow session. Search and select the attribute(s)

        • For each attribute set the following

          1. Operation: select one of the following:

            • set value
            • remove value

          2. Send: select one of the following (options may be different based on attribute type):

            i. another attributes value ii. another profiles value iii. another users account value iv. another users profile value v. requestors account value vi. requestors profile vii. requestors profile value viii. requests value ix. static value x. value builder

      If a date attribute is selected and the operator selected is "more than," "less than," or exactly," 2 more additional fields called Days and Timeframe will appear.

    • SUBWORKFLOW

      1. Workflow to run: select the secondary workflow to run when this action is triggered.
      2. Wait for Completion: select Yes to set the primary workflow to wait for the secondary workflow to complete.
      3. Wait until what action completes?: only available when Yes is selected. Select from the available list of actions. Caution: If No is selected, conflicts may arise. For example, the current workflow may complete and create a new profile before the subroutine completes.

  3. Select create

  4. The Run Workflow action appears on the Workflows page.

Set Attribute Values

Set Attribute Values is an action used to predefine an attribute to a specific value.

Set Attribute Values is available for the following workflow types:

To configure a Set Attribute Values step, from the New Action page:

  1. Select the Set Attribute Values button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

      2. Attributes: search and select the attribute to predefine

        1. For each attribute selected set the following

          • Operation: select one of the following

            1. set value
            2. remove value

          • Set as: select one of the following

            1. static value: enter the value
            2. value builder: select the appropriate value builder
            3. requestors account value: select the appropriate attribute

            4. another users account value: select the appropriate values within each field

              • From what user attribute?
              • Attribute

            5. another attribute value: select the appropriate attribute

            6. another profiles value: select the appropriate values within each field

              • What profile
              • From what Attribute

            7. requestors profile value: select the appropriate attribute

            8. another users profile value: select the appropriate values within each field

              • What user
              • From what Attribute

      If a date attribute is selected, Set As can be set to static or dynamic value. If static value is chosen, select a date. If dynamic value is chosen, the administrator can specify the number of days before or after a value of either:

      • days before today
      • days after today
      • days before attribute (admins will have to search and select the attribute)
      • days after attribute
      • same day as attribute

  3. Select create

  4. The Set Attribute Values action appears on the Workflows page

Set Security Questions

Set Security Questions is an action used to define the number of security questions a user must answer to facilitate self-service password resets or as an additional authentication factor.

Set Security Questions is available for the following workflow types:

Important

When using a Set Security Questions action, it must come after the Collaboration Account Action action in the workflow.

  1. Select the Set Security Questions button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS
      1. Description: enter text to describe the purpose of this action.
      2. Number of Questions: select the number of questions the user must answer.

  3. Select create

  4. The Set Security Questions action appears on the Workflows page.

SOAP API

SOAP API is an action used to send or receive data from and to other applications.

SOAP API is available for the following workflow types:

To configure a SOAP API step, from the New Action page:

  1. Select SOAP API button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

    • ENVELOPE SETTINGS:

      1. WSDL URL: provide the link to the XML file where the Web Services Description Language is defined.
      2. Operation: enter the name of the operation that this action should use.

    • AUTHENTICATION

      1. Auth Type: select from the following options

        • None: (default) requires no additional information.
        • Basic: enter the Username and Password the endpoint recognizes.
        • WSSE: enter the Username and Password for the WS-Security Username Token

    • REQUEST XML

      1. Enter the XMLHttpRequest object to be used to request the data. Liquid can be used here to pull data from the requester or the profile that is being worked on in the workflow.

    • RESPONSE HANDLING

      1. Mappings: to store any of the response data, define the mapping here, by searching and selecting an Attribute and specifying the Path to the key that has the desired value.

    Add another Key Label for each layer if the value is nested in the response.

  3. Select create

  4. The SOAP API action appears on the Workflows page

Status Change

Status Change is an action used to change the current status of a profile.

Status Change is available for the following workflow types:

To configure a Status Change step, from the New Action page:

  1. Select the Status Change button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.
      2. New status: select from the available statuses

  3. Select create

  4. The Status Change action appears on the Workflows page NOTE: The status change takes effect immediately. If the status change should be approved, move the Status Change action after the Approval action.

Un-Assign

Un-assign is an action used to automatically remove contributors from a profile.

Un-Assign is available for the following workflow types:

To configure an Un-Assign step, from the New Action page:

  1. Select the Un-assign button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

    • UNASSIGNMENT

      1. NEProfile roles: select any of the NEProfile application roles and any user within the selected role(s) will be automatically unassigned.
      2. NEAccess roles: select any of the NEAccess application roles and any user within the selected role(s) will be automatically unassigned.

  3. Select create

  4. The Un-assign action appears on the Workflows page

Update

Update is an action used to update a profile using the values in the workflow.

Update is available for the following workflow types:

To configure an Update step, from the New Action page:

  1. Select the Update button

  2. Specify the appropriate information in each field

    • BASIC SETTINGS

      1. Description: enter text to describe the purpose of this action.

  3. Select create

  4. The Update action appears on the Workflows page

Username and Password

Prompts the user for their username and password.

Note

This action is included in all Collaboration Login workflows and can't be modified or deleted.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.