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

Event UPDATE on UNSAccountB not firing process

We want run process when column AccountDisabled changes from False to True. We've assigned UPDATE event with generating condition:

  • Value = $AccountDisabled:Bool$ <> False OR
  • Value = $UID_UNSRootB$.Equals("3940b6c6-a5ce-4aa0-855a-8c512f645e03") _
            AndAlso $AccountDisabled:Bool$=True

Process is not firing with none above. When there is no gen. cond. process is executing.

  • try  just:

    Value=$AccountDisabled:Bool$

  • Still won't work. Only when there are no Gen. Cond. it is fired.

    PS. I have another process to enable account which is always fired (even twice) on Event=Update with gen. condition:

    Value = $UID_UNSRootB$.Equals("3940b6c6-a5ce-4aa0-855a-8c512f645e03") _
            AndAlso $AccountDisabled:Bool$=False

    Could it be collision between these two process?

  • if you really change the AccountDisabled from False (unchecked) To True (checked) during the update, then Value=$AccountDisabled:Bool$ must work !

    Just to be sure:
    -) commit Jobchain changes to database
    -) compile database
    -) restart Fat-client tool for testing
    -) retest (Change AccountDisabled from False to True (From Checked => Unchecked)
  • Update process is firing by IDM after subscribe\unsubscribe account def. in ITShop.
    Imagine that:

    1. account resists in UNSAccountB with XMarkedForDeletion=1 and AccountDisabled=1
    2. requesting for account through ITShop results in the end with updates for XMarkedForDeletion=0, AccountDisabled=0 and invoking KPT_UNSAccountB_Enable process
    3. unsubscribing for account through ITShop results only with updates for XMarkedForDeletion=1, AccountDisabled=1 but NOT firing KPT_UNSAccountB_Disable process

    JobChain is always commited to DB and compilation is always made.

    PS. In log I'm seeing something like this:

    <p>2017-05-24 09:24:36 +02:00 - Process step parameter fc30848d-9004-4788-9c71-5ba234ff9313:
    [Job]
        ComponentAssembly=HandleObjectComponent
        ComponentClass=VI.JobService.JobComponents.HandleObjectComponent
        Task=Delete
        Executiontype=INTERNAL
    [Parameters]
        ConnectionProvider=VI.DB.ViSqlFactory,VI.DB
        ConnectionString=Hidden
        ObjectType=UNSAccountB
        ProcID=d1854693-aeca-439c-b8a4-9a1228a18744
        WhereClause=(UID_Person = 'ad6898f1-db5e-47bb-8ce8-a57d7d5e9f5d') and (UID_TSBAccountDef = '6f65a4bf-acde-49fb-8f1a-6892ddaf6d08')

    so I even tried invoke process for DELETE event but it didn't help.

  • Maybe the WhereClause is restrictive, try to open or remove it just for test
  • It's not depending on me. This is result of IDM internal calculation.
  • Try to simulate the generation of JobChain in Designer = >

    can you show me the Generation condition of the Process step ?

    is the Do not generate option of the JobChain unchecked?

    can you show me the Process step Parameters?

    or can you export the Jobchain and paste it here for me?

  • When I'm changing AccountDisabled from 0 => 1 directly from Manager process is fired on UPDATE (Gen. Cond. => Value=$AccountDisabled:Bool$).

    When ubsubscribing from ITShop some type of deletion is made. This deletion updates XMarkedForDeletion to 1 and AccountDisabled to 1 but in this case process is NOT fired.

  • Maybe the DELETE Event is fired instead of UPDATE, Try to add the DELETE Event to the Chain and try again
  • I've already tried this but with no success. I'm pretty sure that is the UPDATE because without Gen. Conditions process will fire up. Of course without Gen. Cond. two processes will be fired (Enable and Disable) and I want to avoid it.
    Temporarily, my workaround is to change "Deferred deletion" to 0 for UNSAccountB and change event UPDATE to DELETE for process KPT_UNSAccountB_Delete.