Can We Change the Response Code Using After Operations Rule

<?xml version='1.0' encoding='UTF-8'?> 1717387090541 1717387089675 0 50 0 50 2** 0 50 2** 0 50 2** 0 50 2** 0 50 0 50 2** 0 50 0 50 true true roleDescription

app.xml (34.6 KB)
Hi @ashutosh08 ,Please find app.xml file.

Hi @jespaancy,

I see that the “throwProvAfterRuleException” is not set to true. Can you change it and give it try? Also please make sure to remove the cache.

Thanks

hi @ashutosh08,
APP1.xml (32.7 KB)

I already tested with the value true then changed to false.when i tested again and again accidentally missed the value.
please find the attached updated xml.I am still not getting any error on the UI and showing commit status only.

hi @ashutosh08 ,
pls verify my rule also
rule1.txt (2.6 KB)
please find the log also

Arulmani Jespa ANCY (JTC) 5:59 PM (0 minutes ago)

to me

2024-06-05T16:18:01,846 ERROR https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:166 - Rule - Process response : Begin{issuccess=false, message=HUANGJJP - Invalid User ID.}

2024-06-05T16:18:01,851 ERROR https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:166 - Rule1

2024-06-05T16:18:01,855 ERROR https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:166 - Rule2false

2024-06-05T16:18:01,859 ERROR https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:166 - Rule4

2024-06-05T16:18:01,863 ERROR https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:166 - Account ID from JSON Body :::: false

2024-06-05T16:18:01,867 ERROR https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:166 - Rule5

2024-06-05T16:18:01,871 ERROR https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:166 - value from JSON Body :::: false

2024-06-05T16:18:01,875 ERROR https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:166 - Rule - Process response ex: sailpoint.tools.GeneralException: throwProvAfterRuleException

2024-06-05T16:18:01,879 WARN https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:687 - After operation rule returned invalid information for endpoint: AddRoleToUser

2024-06-05T16:18:01,879 DEBUG https-openssl-nio-443-exec-9 connector.webservices.v2.RequestOrchestratorV2:258 - No paging steps defined for endpoint ‘‘AddRoleToUser’’, terminating paging…

2024-06-05T16:18:01,879 DEBUG https-openssl-nio-443-exec-9 connector.webservices.v2.WebServiceFacadeV2:591 - Operation Modify completed on identity HUANGJJP

2024-06-05T16:18:01,881 DEBUG https-openssl-nio-443-exec-9 sailpoint.connector.webservices.WebServicesConnector:2364 - Provisioning plan in return : <?xml version='1.0' encoding='UTF-8'?>

2024-06-05T16:18:01,881 DEBUG https-openssl-nio-443-exec-9 sailpoint.connector.webservices.WebServicesConnector:2364 - result after method exit : <?xml version='1.0' encoding='UTF-8'?>

Hi @jespaancy,

Why are you catching the exception after it is being thrown explicitly?

Can you remove try/catch and then try it?

Thanks

thank you @ashutosh08 .
it is working

Hi @jespaancy,

Feel free to mark my response as solution so that it can be referenced by other at later stage.

Thanks

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