Handle 'Candidate User Problem' Exception before workflow starts
Summary: The discussion centers around a 'Candidate User Problem' Exception that occurs before a workflow starts. The author is seeking advice on how to handle this exception, as the default error message is unclear to users. A respondent suggests disabling the candidate user check at the start of the workflow and handling it within the workflow using a script task. The original poster appreciates this suggestion, acknowledging it as potentially the best solution and thanks the responder.
Hi citizens!
Is it possible to catch a 'Candidate User Problem' Exception that triggers before a workflow is started? This exception seems to trigger outside of the workflow, and I assume that it cannot be caught with regular exception handling in a Script task. Users have notified us that the error message is unclear, and we want to replace the error message with a clearer message.
Hope to hear your thoughts!
Thanks
Example of the Exception:
Laurenz Hiller
·1 year ago · EditedHi @takishoogterp1
You can disable the candidate user check on workflow start in the settings and then handle the candidate user check inside of the workflow in a script task.
def dgcError = new WorkflowException("Insert your text.") dgcError.setTitleMessage("Insert your text."); throw dgcError;takishoogterp1
OP1 year ago · EditedHi @laurenzhiller1
Thanks! I forgot that this was a setting; turning it off and handling it in the workflow is probably the best solution for this.