SG-3289 CLONE - Databridge - ION inboubnd transaction failed to trigger outbound BOD from table R5USERS - HxGN EAM - 12.0.1 - Release Bulletin - Hexagon

 Description 

This is on cloud and EAM is integrated with ION.

#1 An inbound transaction from ION inserts a new record into table R5TRACKINGDATA;

#2 A flex business rule of Post-Insert on table R5TRACKINGDATA, this flex is to update a record in table R5USERS;

#3 And the install parameter @SECUSER is 'Y' ;

#4 On Databridge Partners screen, Partner 'INFOR-ONRAMP' is active and in Subscriptions tab, the event 'SECUSER' with Document type 'ProcessSecurityUserMaster' is enabled;

Scenario #1:

1.1 Open User Setup screen, locate a User code 'USER1' and update description, group and un-select check box 'HxGN EAM' and checkbox 'Screen Designer', then save;

1.2 Open Databridge Outbound Events screen, there is a new outbound event with Transaction Type 'SECUSER' and status is Done;

1.3 Open Databridge Message Status screen, 2 new outbound messages: #1 is SECUSER, #2 is ProcessSecurityUserMaster;

1.4 Check on ION, an BOD of type SECUSER were pushed out from EAM;

Scenario #2:

2.1 Add a post-insert flex on table R5TRACKINGDATA, this flex is hardcoded to update the record in table R5USERS, usr_code = 'USER1', update the 4 columns: USR_GROUD, USR_DESC, USR_ACTIVE, USR_SCREENDESIGNER, the change is same above step#1.1;

2.2 go to ION, push a messages into EAM, this message is to insert a new record into table R5TRACKINGDATA and fire the flex of #2.1;

2.3 go to User Setup screen, check 'USER1', the Description, group, check box 'HxGN EAM' and checkbox 'Screen Designer' had been changed;

2.4 Open Databridge Outbound Events screen, there is a new outbound event with Transaction Type 'SECUSER' and status is Done , same as Step#1.2 of Scenario#1;

2.5 Open Databridge Message Status screen, only 1 new outbound messages, type is SECUSER;

2.6 check in ION, no BOD of SECUSER were pushed from EAM;

Expected Result: in Scenario #2, Step 2.5 & 2.6, EAM should create 2 new outbound message, #1 is SECUSER and #2 is 'ProcessSecurityUserMaster' and a new outbound BOD, type SECUSER, should be pushed out from EAM to ION;

Actual Result: in scenario#2, Step 2.5 & 2.6, EAM created only 1 new outbound message - SECUSER, no message of 'ProcessSecurityUserMaster' and no outbound BOD of SECUSER from EAM to ION.