and more in a single search tool across platforms. Read the announcement here. |
03/26/2024 01:43 PM
Hello!
I am experiencing an issue in my CreateAccountJSON where my successResponses are not being recognized.
The account still gets provisioned in the target system, but this is the error we get in the Provisioning Comments of the subject user's pending task:
For reference, here is my CreateAccountJSON successResponses attribute:
Has anyone experienced this before? Let me know if you see any errors with what I have!
Thank you,
- Wes
Solved! Go to Solution.
03/26/2024 07:43 PM
You can use either message or HTTP Status code.
03/27/2024 05:48 AM
Hi Rushikesh,
I have tried using one or the other (message vs statusCode) on their own and I see the same error described above.
Thank you,
- Wes
03/27/2024 05:55 AM
did you tried like below:
successResponses": {
"statusCode": [
202
]}
03/27/2024 06:44 AM
Hi Raghu,
It looks like I haven't formatted the statuscode this way before, it worked as intended! Thank you for your help and to Rushikesh for the assist!
Thank you,
- Wes
03/27/2024 10:48 AM
Disclaimer - This is an AI generated response and feedback on this thread will be used to fine tune.
The issue you're encountering with successResponses not being recognized in your CreateAccountJSON configuration, despite the account provisioning successfully in the target system, could be due to the way the success conditions are defined and how the response from the target system is structured.
Looking at your configuration for successResponses, it seems there might be a misalignment between expected and actual response formats or values from the target system. Let's address potential issues and provide a corrected approach:
statusCode should be an integer, not a string. When specifying HTTP status codes in successResponses, ensure they are provided as numeric values without quotes.
When matching a message in the response, ensure the value exactly matches what the target system returns, including any quotations or additional formatting. If the message is a JSON object or nested, you might need to use responsePath to navigate to the correct value within the response.
If both a specific statusCode and a message within the response body indicate success, you might need to adjust your configuration to accurately reflect this. However, it's important to note that typically statusCode or message independently determine success.
Assuming you expect a 202 status code or a specific message in the response, the configuration should look something like this:
"successResponses": [
{
"statusCode": 202
},
{
"responsePath": "path.to.message",
"values": ["expected message"]
}
]
Notes: