ISC workflows add documentation JSONpath implementations

[angelo_mekenkamp]

Hi all,

SailPoint recently introduced a dedicated JSONpath evaluator tool:

Introducing the SailPoint JSONpath Evaluator

SailPoint has released a dedicated JSONpath evaluator tool on the Developer Portal and in the SailPoint CLI. These tools are maintained by SailPoint and offer a seamless experience for testing JSONpath expressions without having to go to a third-party website. All Developer Community tools can be accessed via the top-navigation: [Tools in top-nav] Our web validator allows you to choose between the Workflows and the Event Trigger JSONpath implementations, each of which support di…

This is great, as we can test how ISC workflows behaves on these JSONpath expressions, especially once the results actually match, which is being worked on, as you can see here:

ISC JSON path evaluator from SailPoint does not behave the same as ISC workflows

Hi all, SailPoint has written a Json path evaluator that should be as similar as possible to the implementation used by SailPoint in each area of the UI (only workflow and event trigger implementations are supported for now). This is great and can be useful, but I noticed during testing that it is actually not matching in behavior. Using this evaluator to convince yourself that your workflow implementation will work correctly is therefore not a working strategy. Since the defau…

However, besides testing the different operations, we also would need to know which operations are supported and how to use it. Therefore we need documentation. SailPoint currently points to documentation outside of SailPoint, but the refered documentation is not truly matching as well. Therefore it would make more sense if SailPoint has their own documentation on their own implementation of the operations, which allow us to validate this, and refer to SailPoint Support with the SailPoint documentation, making it easier to convince SailPoint Support on the wrong behavior of ISC workflows.

Created this idea discussion here as suggested by @colin_mckibben:

Introducing the SailPoint JSONpath Evaluator

We do provide links to our existing docs for whichever implementation you use, but it sounds like providing those operations directly in the web validator would be more beneficial. Can you please open a Idea Discussions for this?

Kind regards,
Angelo

[questjj (Jason Quest)]

Agree 100%. I spend way too much time trying various JSONpath expressions to do something so simple before guessing the supported one. I’ve been a developer for 25 years, would hate to see a less experienced person try to get there. This is really a blocker for less technical people to do anything particularly useful with workflow. Examples are needed, even “Harbor Pilot” tries to use unsupported JSONpath expressions, so let it eat some fresh documentation. Maybe give the community a place to post known working examples? Here’s one I struggled with just yesterday.

Native Change Event Trigger - if/else block to check if the changed attributes includes “mail”
String Compare when its a (list of maps, check if key “name” contains a value of “mail”).

"Compare Strings": {
				"choiceList": [
					{
						"comparator": "StringEquals",
						"nextStep": "Send Attributes Changed Notification 1",
						"variableA.$": "$.trigger.singleValueAttributeChanges[?(@.name== 'mail')].name",
						"variableB": "mail"
					}
				],
				"defaultStep": "Send Attributes Changed Notification 2",
				"displayName": "Has Mail Changed?",
				"type": "choice"
			}

Example Input

{
"account":
    {
    ...
    },
"accountChangeTypes":
    [
    "ATTRIBUTES_CHANGED"
    ],
"eventType": "ACCOUNT_UPDATED",
"identity":
    {
    ...
    },
"singleValueAttributeChanges":
    [
        {
        "name": "sn",
        "newValue": "Cr33ly",
        "oldValue": "Creely"
        },
 	{
        "name": "mail",
        "newValue": "[email protected]",
        "oldValue": "[email protected]"
        }
    ],
...