Building Workflows - SailPoint Identity Services

To build an automated workflow in SailPoint's cloud services, you can use the visual builder or you can configure a workflow using JSON.


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

There is a reference under “Building a Workflow” → Step #4 to “If you exceed the maximum number of steps allowed…” but there is no definition for the maximum number of Steps that I could find. Could this limit be added to the documentations?

Hi @gmilunich , Thank you for your feedback. The number of steps allowed per workflow is based upon your SailPoint Identity Security Cloud Suite level and they’re listed here. You can contact your Customer Success Manager to find out which suite level your organization is using.

It would be great if that note could be added to that section to let users know. Sometimes the developers writing the workflows are not the same people who purchase the software/work with the CSM. I have a client where the director and IAM Team lead work with the CSM, but there are 4 developers under them writing workflows/configuring the software.

Hi @gmilunich Thank you for your feedback. We appreciate you sharing it and will take it into consideration for future doc improvements.

Hi, I’m attempting to build a workflow right now using a trigger filter. I’m looking at the chart given for examples Building Workflows - SailPoint Identity Services . I feel that there could be more context given about exactly how the filter functions (i.e., in what format will data be fed into it, and what “output” should the filter have). For example, it’s confusing to me to see notation in the example chart both of the notation $[(@. == “xyz”)], which would seem to me to ONLY accept an JSON Array and then return a filtered version of that array, and also $.[?()] , which would seem to evaluate a JSON Object Array field, and return a filtered version of that object. In my testing and observations, it seems that essentially there just needs to be at least one “filter” expression in the filter ?[()], and that it needs to be “truthy” (returning SOME data) to evaluate as true, or false by returning NO data if the statement returns an empty array.

I would also suggest that this page link out to the Json Path Evaluator | SailPoint Developer Community tool as well, unless I’m missing it somewhere in there.