• State Verified Answer
  • Replies 3 replies
  • Subscribers 95 subscribers
  • Views 276 views
  • Users 0 members are here
Options
Related

Undocumented object events for UNSAccountB: ENABLED, DISABLED and DEACTIVATE

Niels de Groot
1 month ago

When you disable or enable an UNSAccountB object (AccountDisabled@UNSAccountB)
You receive a DISABLED or ENABLED event.

When you delete an enabled UNSAccountB object (deferred deletion > 0)
The account is disabled and you receive a DEACTIVATE event but not a DISABLED event.

When you undelete an UNSAccountB object (deferred deletion > 0)
You receive an ENABLED event.

Now the thing is OOTB there are no QBMEvent entries for these events:
ENABLED, DISABLED and DEACTIVATE for UNSAccountB

- Why are these the events not registered in the QBMEvent table?
- I could not find any mention of these events in the documentation?
- Why are these Events ENABLED and DISABLED not named: DISABLE and ENABLE like UPDATE and DELETE present tense?
- Why is there only a DEACTIVATE event and not also an ACTIVATE event when you undelete the object?
- Why is the DISABLED event not triggered on the deferred deletion of an enabled account?
- Are there more events generated by the DBQueue processor that have no QBMEvent entry,
  and if so where can I find a complete list of all the OOTB supported events?

Sorry for all these questions.

Regards,
Niels

  • +1 1 month ago

    Hi Niels,

    I try to answer at least some of your questions to my best knowledge.

    The events ENABLED and DISABLED are coming from the customizer VI.Common.Customizer.AccountEventLogic that is assigned to the table UNSAccountB (You can verify this in the Designer. In short: Select the table, go to the View menu item, choose "Select table relations" and activate the relation DialogTableHasCustomizer). It provides an PasswirdChanged event as well.

    In dialog QBMEvent only the common events (INSERT, UPDATE, DELETE) or those that do have a process attached are present.

    The event DEACTIVATE will be fired for each object if the object has a DeleteDelay. In the case of undeleting an object an event UPDATE will be generated.

    I cannot comment on the differences in tense.

    Why is the DISABLED event not triggered on the deferred deletion of an enabled account? => My guess is to prevent two processes triggered at once, doing the same.

    HtH

  • 0 1 month ago in reply to Markus Weiss-Ehlers

    Hello  

    I'm currently working on a 9.0LTS (v90-167803) environment.
    Here the 'DEACTIVATE' event is not fired upon the UNSAccountB even though the QBMEvent entry is present.

    In my test labs 9.2/9.3 I can see the event being generated, but in this 9.0LTS production environment nothing happens.

    Db Operations Queue: Operation Insert on <Key><T>DialogDeferredOperation</T><P>b70a152c-4833-424d-a0ea-7b2733dd5c00</P></Key> added to database queue (level 0). 
Delayed Logic: OnSaved for b70a152c-4833-424d-a0ea-7b2733dd5c00 
Commit transaction in read/write entity 
Old state: None, New state: Saved 
Old state: Loaded, Deleted, PermissionBased, ToDeletePhysical, New state: Loaded, Deleted, PermissionBased 
Generating DEACTIVATE event 
Generating chains for DEACTIVATE on <Key><T>UNSAccountB</T><P>75bfe65e-45cd-4194-8875-d22f0faa691b</P></Key>.

    Do you know if this is a known issue with 9.0LTS, or was the DEACTIVE logic on UNSAccountB implemented after this version?
    What logic/customizer triggers the DEACTIVATE event?

    Thank you so much,
    Niels

  • +1 1 month ago in reply to Niels de Groot

    Do you have a delete delay configured for the UNSAccountB table in your 9.0 LTS environment? The DEACTIVATE event is a generic event from the base object layer, that is always fired if a delete delay is configured.

    I cannot find a specific issue around the event not fired.  Please create an SR if your issue persists.