Event Trigger Managed by Workflow

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi,

I need your help. We’re experiencing an issue with our workflow that is triggered by the Access request decision. When a request is approved, the workflow does not get triggered. We also tested the subscription and checked the activity log, but nothing appears there.

image

2

Hi Earlvil,

I guess there is some issue with your filter. If you are creating filter using default trigger template from documentation, I wouldn’t suggest that. This is what I will do to resolve or debug.

  • I will create a dummy workflow with just “Access Request Decision” trigger and success step, without filter operation. Then I will turn on the workflow and will see if the workflow executes or not when a request is approved.

  • If workflow doesn’t execute ( on empty filter and when a request is approved), I will open a ticket with sailpoint. I can’t do anything.

  • If the dummy workflow executes, then I will grab the execution JSON response and use the trigger output from that execution, to prepare the filter according to my requirement.

Sometimes the JSON provided in the documentation are outdated and if we use that JSON response for specific trigger to create our filter, it may not work.

Hope it helps on debugging your issue.

Thanks,
Kapil

3

Hi,

Thank you for your suggestion—it worked, and I was able to debug the issue by creating a dummy workflow.

Previously, our filter was working and able to trigger the workflow. The filter I’m using is:

$.requestedItemsStatus[?(@.clientMetadata.requestedAppName == ‘Cority’ && (@.approvalInfo == null || @.approvalInfo == || @.approvalInfo[0].approvalDecision == ‘APPROVED’))]

Here’s the JSON output that matches the filter. However, I’m a bit confused—when I request access through the application, the clientMetadata appears as null.

“requestedItemsStatus”: [
{
“accessRequestContext”: null,
“approvalInfo”: ,
“clientMetadata”: null,
“comment”: “test”,
“description”: “Cority - General User”,
“id”: “###”,
“name”: “##”,
“operation”: “Add”,
“type”: “ACCESS_PROFILE”
}

4

Great to hear that it helped you debugging the issue. If you think it can help other fellow developers facing similar issue, you can mark my response as a solution.

Thanks.

5

Thank you Kapil.

We raised a ticket to SailPoint, and the engineering team fixed the issue on our tenant

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.