Dalay the workflow trigger

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.4

Please share any images or screenshots, if relevant.

[Please insert images here, otherwise delete this section]

Please share any other relevant files that may be required (for example, logs).

[Please insert files here, otherwise delete this section]

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

We are encountering a locking issue because the Mover and Attribute Sync lifecycle events are triggering simultaneously. To address this, I attempted to delay the execution of the Attribute Sync workflow by adding a wait parameter in the start step. However, after adding the wait, the wrapper workflow completes, but the Workflow-AttributeSync sub-workflow is not triggered. Could you please suggest a solution to resolve this issue? How to delay the event triggered?
```

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE Workflow PUBLIC "sailpoint.dtd" "sailpoint.dtd">
<Workflow explicitTransitions="true" name="Workflow-RequestObject-Wrapper" type="IdentityLifecycle">
  <Variable input="true" name="trigger">
    <Description>The IdentityTrigger</Description>
  </Variable>
  <Variable input="true" name="event" transient="true">
    <Description>
      The IdentityChangeEvent.  It can be used to build
      the provisioning plan, but does not need to be
      persisted with the case, so marked as transient.
    </Description>
  </Variable>
  <Variable input="true" name="identityName">
    <Description>The name of the identity.</Description>
  </Variable>
  <Variable initializer="true" name="transient"/>
  <Step icon="Start" name="Start" wait="2">
    <Transition to="Start Request Manager"/>
    <Transition to="Stop"/>
  </Step>
  <Step icon="Task" name="Start Request Manager">
    <Script>
      <Source>     
  			import sailpoint.rapidapponboarding.rule.WrapperRuleLibrary;
  			  WrapperRuleLibrary.startRequestManager(context,identityName,trigger,event,"Workflow-AttributeSync",60,null);  			 
  		</Source>
    </Script>
    <Transition to="Stop"/>
  </Step>
  <Step icon="Stop" name="Stop"/>
</Workflow>
2

Hi @Arunkumar0107

if there are 2 life cycle events triggered at the same when identity refresh with process events checkbox runs - do you have different workflows configured for these 2 life cycle events or same one?

3

Hi @vinnysail ,

We have Two different lifecycle event. Mover lifecycle event configured with separate workflow. Attribute syn lifecycle event configured with different workflow.

4

Hi @Arunkumar0107

Are you seeing identity locking issue if both workflows are called at the same time ?

Same identity will be going these 2 different workflows ?

am not sure just asking is it possible to combine 2 workflows into 1 and defined combined life cycle event criteria ?

5

Hi @vinnysail ,

Are you seeing identity locking issue if both workflows are called at the same time ?

Yes, identify lock issue due to both workflow processing the same identity at same time.

Same identity will be going these 2 different workflows ?

For testing, we have triggered lifecycle event for single identity. We are getting lock issue.

am not sure just asking is it possible to combine 2 workflows into 1 and defined combined life cycle event criteria ?

Mover and Attribute syn are different lifecycle event. We can’t combined into single workflow.

Any other suggestions to overcome this issue?

6

Hi @Arunkumar0107

Is the life cycle event criteria based on attribute changes or via any rule - if you can combine or detect both of these types via one life cycle event then you can combine bitg workflows into one and inside you can make changes accordingly you can do combined updates on identity object that can prevent locking

7

The key issue is that the wait parameter on the Start step might be causing the workflow engine to lose context.

Can you please put the wait at this step and test it

1 Like
8

@Arunkumar0107 You can launch a workflow with a delay using the Request API( you can schedule an actual transaction of mover actions in a separate workflow after 1 minute).

I believe you are not relying on target mapping for attribute synchronization for the target application.

Thanks,

@SivaLankapalli

9

Hi @Arunkumar0107 ,

as per my understanding your approach (using a wait step) would work if you remove “transient == true” from the workflow.

Give it a try please and let us know the results.

Thanks,
Daniel

1 Like
10

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