Debugging the code I found that the SCIMUtil.getETagString(...) method throws a null pointer when trying to fetch modified or created time of the TaskDefinition object since they are both null at this time.
Share all details about your problem, including any error messages you may have received.
We are looking to move from using the REST api to launch workflows to the preferred SCIM API, however most of our workflows have the transient variable set to true and we are seeing this issue when attempting to launch a workflow. Is this a bug in the SCIM code?
@jthorson I’m curious why you need the transient variable set to true. This is typically useful when a form is left open and the user doesn’t take any action, as it prevents the data from being saved to the database. However, for workflows triggered via SCIM, this isn’t necessary.
I don’t necessarily need the transient variable set to true for the API launched workflows since they wont have a form. However, I am still not able to launch the Identity Refresh task which shouldn’t be transient, so not sure what is going on there.
Regardless, I think it is a bug for the SCIM mapper code to throw a NPE when trying to map the response of the workflows task result to a SCIM response object.
Yep, I guess so. Because when I tried to recreate the issue, I got same error. I tried removing all transient values and executing POST API again, but got same error. I’ll let you know if I get any more details
Although I’m aware that ‘resultExpiration’ would be used to set expiration on RequestDefinitions (Usually on emails), I’m not aware what would be the impact if we remove it from workflow.
I would suggest you to give it a try and check with SailPoint Vendor team to know the impact of removing resultExpiration on workflow entries.
