IIQ Joiner Workflow Issue because of wrong or missing identity attributes

Which IIQ version are you inquiring about?

8.3

Share all details about your problem, including any error messages you may have received.

I would like to ask about the joiner workflow behavior.
My issue is that when incorrect data is entered in the HR system, the joiner workflow remains in a pending state and the AD provisioning is stuck at executing, which is expected.

However, after correcting the data for some problematic users today (3-Nov), those users have a joining date of 2-Nov. When I run the refresh task, the joiner workflow is not triggered again because the joining date has already passed, and I cannot modify the joining date this is not allowed.

My questions are:

  1. Can I manually trigger the joiner rule and pass specific identities to it?

  2. Is there a way to make the workflow fail instead of remaining stuck in pending when mandatory data is missing or incorrect?

Thank you.

For your 1st question, yes you can trigger joiner workflow after manipulating the data. Check your Joiner event and based on the conditions, change the values of your identity and trigger the Joiner.

For your 2nd Question, yes, it can be done but for that I need to check the Workflow that you have created for Joiner Event.

Thanks for your reply.

Unfortunately, changing the joining date is not legal, and the condition in the workflow is based on it — which is my issue.

That is why I am asking if I can manually trigger the rule and pass the identity to it?

Write a rule to trigger the workflow. Add all the mandatory values that a workflow needs to process. Pass the username and other values in arguments and call the workflow.

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