This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Creating delay in custom process (Process Orchestration)

I'm looking to add a delay in a custom process before running (Send mail with account name) to give enough time for Office 365 accounts to be created.

Issue is users are getting emails about their account being created and configuring their password before all target systems are completed.

I can insert a new process before it, which is blank my thoughts were to add some sort of timer in that process. However I'm not sure the best way to approach this as their might be a better method or solution.

Does anyone have any insight as the best way to approach this?

0 kung over 7 years ago

Use the DelayComponent in the process. Look for examples in the standard D1 code.
Cancel
Up 0 Down

Cancel
+1 Craig.Bolte over 7 years ago

I know these screenshots are from v6 but it should be the same for v7. Create a process step, within your process flow, and use the DelayComponent:

And then on the Parameters tab, define how long you want to delay. In this case it is delayed 10 minutes.

Hope this helps.
Cancel
Up 0 Down

Cancel
0 ndahms over 7 years ago

It does help very much and I'm using 6.1.2 I very much appreciate the help.
Cancel
Up 0 Down

Cancel
0 Sebastian.Kuebbeler over 7 years ago

Just to make sure you got the right answer on this:
It sounds like you have multiple target systems in which accounts are created, but users receive an email to change their password on the back of the O365 account creation process. Is this a correct description of your issue?
Cancel
Up 0 Down

Cancel
0 ndahms over 7 years ago

I believe, basically the issue being AD accounts are created users are then sent an email to change their password. Since we have 30K users to sync with 365 Quick Connect takes several hours to run and create the users in the target system. The goal was to add a long delay in that email so the 365 account actually exists before the users resets their password.
Cancel
Up 0 Down

Cancel
0 dezuykov over 5 years ago in reply to Craig.Bolte

Hello Craig, what should I write to the JobID parameter ?

I have an error in my "Delay" step "Process step Delay contains neither a server detection script nor a server mask". I can't find any information in documentation
Cancel
Up 0 Down

Cancel
0 Markus Weiss-Ehlers over 5 years ago in reply to dezuykov

I suggest taking a look into that part of the documentation that describes the definition of processes and process steps. In your case, the information about a server detection script and server function (server mask) can be found here https://support.oneidentity.com/technical-documents/identity-manager/8.0/configuration-guide/72#TOPIC-862572

In short, you haven't specified which job server or type of job server should execute your process step.
Cancel
Up 0 Down

Cancel
0 Sebastian.Kuebbeler over 5 years ago in reply to Craig.Bolte

In version 7+ this approach may cause DBQueue operations for the same base object to reset while waiting for the process to finish. For that reason long-running processes should be avoided. Instead of creating a long-running process I would suggest creating a schedule that triggers the event regularly on those objects whose creation date is x minutes in the past.
Cancel
Up 0 Down

Cancel
0 dezuykov over 5 years ago in reply to Markus Weiss-Ehlers

Yes, you are right. Sorry for such a question.
Cancel
Up 0 Down

Cancel

Endpoint Privilege Management

Creating delay in custom process (Process Orchestration)