Actions - SailPoint Identity Services

Feedback Documentation Feedback SaaS Documentation Feedback
,
1

Each workflow action receives input from the data flow and performs an action in your system. The values you enter in the fields for each action help determine what is done and how. The result of each action, in JSON format, is added to the workflow's data flow.

This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/saas/help/workflows/workflow-actions.html
3

2 posts were split to a new topic: Use workflow to remove manager from terminated identity

6

For the “Create Certification Campaign”, the Documentation here Describes Version 2 of the Action, but does not provide any details on Version 1 of the Action. Version 1 is still used in several of the Workflow templates, including:

  • Update and Certify Access When an Identity Changes Departments
  • Create and Activate a Certification Campaign

It is likely that these should be updated to Version 2, but since V1 exists, and could exist in client workflows, it would be good to document this, or at least denote that there is a V1 and V2, and that users should update to V2 during development if they find they have V1.

Example From Ambassador Tenant:
TemplateCreateandActivateaCertificationCampaign20240807.json (3.2 KB)

8

Hi Geoff! I’ve created SAASDOCS-7888 to update the info around V1 and V2 Actions in our Workflows documentation. We’ll let you know when that work is completed. Thank you!

9

Requesting you to improve the documentation with better examples for “Send Email” Action.

Current example:
{“name.$”:“$.getIdentity.name”}

What I tried to do:
I was trying to fetch some form data into my email. In the context, I have mentioned the following and this did not work well.
{“name.$”:“$.formData.fieldName”}

The right approach for this would be to mention the following in the context.

{“name.$”:“$.trigger.formData.fieldName”}

Examples suggested:

Requesting you to add the following in addition to existing example so that others can be helped.

Context should be configured as {“name.$”:“$.trigger.formData.fieldName”}. The trigger provided data may need to be used with the help of $.trigger.
Variable should be used as {$name}

11

Hi Sandilya! I’ve created SAASDOCS-8280 to review our Send Email action examples. Thanks for your feedback!

12

2 posts were split to a new topic: Filtering Get Pending Access Requests action isn’t working in Workflows

13

Hi @SandilyaKrovvidi Thank you for helping us improve our documentation. Based on your feedback, we’ve updated Actions - SailPoint Identity Services.

1 Like
14

Requesting a clarification and update to the documentation for the ‘Manage Access’. Action

Currently, the documentation primarily focuses on the usage of this action in conjunction with the ‘Get Access’ Action, and the provided JSON body example is specific to this context.

image
image863×234 2.46 KB

However, when using the ‘Manage Access Action’ independently, without input from the ‘Get Access’ Action, the current **JSON body format may not be suitable.

To ensure accurate and comprehensive documentation, I suggest the following modification to the JSON body example:

[
  {
    "id": "fg987jghjk",
    "name": "Access",
    "type": "ENTITLEMENT"
  },
  {
    "id": "fg987jghjk",
    "name": "Access ABC",
    "type": "ENTITLEMENT"
  }
]

This revised format provides a more flexible and universally applicable JSON body structure for the ‘Manage Action’, accommodating various use cases, including those independent of the ‘Get Access’ Action.

Thanks!

18

Hi @sidharth_tarlapally Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: SAASDOCS-8614

19

Hello Writers,

image
image1496×378 40.8 KB

I am missing the information on how the workflow will continue when the deadline is not met.

  • Will the workflow error out? Do we have to use the error handling mechanism?
  • If it will not error out, which information is available in the next step to determine that the user hasn’t submitted the form in the allocated time?

Thanks,
Andrei

21

Hi @adamian! I’ve created SAASDOCS-8757 to review these docs and provide more information about what happens when the deadline is not met. We’ll update this thread when that work is completed. Thanks for helping us improve the docs!

22

Hi @adamian! Thank you for helping us improve our documentation. Based on your feedback, we’ve updated what happens to the workflow when a form’s deadline is not met.

2 Likes
23

Hi Graeme,

The workflow is paused until the user completes and submits the form. If the form is not submitted before the configured deadline the workflow will encounter an error and stop.

If this should be the case, I hope you’ve also opened a bug defect, because it does not behave like that.

:sailpoint: