I am working on a Launcher which is connected to a Workflow and what I am seeing is that when Form in the Launcher is “Cancelled” instead of “Submitted” Interactive Form in the workflow errors out with Code 500.
Cancelled in the Interactive Process while testing:
Execution View:
Following the DSS Form, process entered Error branch and found Error Code 500 that was displayed in above screenshot.
I was expecting the process to enter “Success” branch from the Interactive form (labelled DSS Form) and then enter “False” branch from “Form Submitted” node below
Is this a bug? ie missing Error Handling when form is not submitted.
Or is it meant to be designed like this? ie Users should NEVER click cancel button?
@tyler_mairose Could someone from SailPoint look into this please?
Hi @iamnithesh
I’ve come across this many times before. I assumed it was a feature, not a bug…
I usually follow up my forms with a compare operator check to ensure we have the proper data rather than assuming the form will perform validation for us.
Thanks @trettkowski
I too intend to put Comparators in place as it is going to be critical for my form, I would like to display a warning message (instead of error message) when user Cancels the form. I cannot do this if the form goes into Error state when cancelled.
Ah gotcha, I think that can be accomplished. You’ll just need another compare check after your “Error Exists” step and an interactive message specifically for cancelled. Just tested in my own environment and seems to work great:
Form UI:
Compare Operator Logic:
Thanks @trettkowski
That works perfect for me.
