event ASSIGN on UNSAccountBInUNSGroupB is generated outside of the connection

Question

Hello, 
 I have fullsync script where I set FULLSYNC connection variable to prevent processes to generate. When I create missed UNSAccountB in IDM the processes aren't generate (event = INSERT on UNSAccountB) but When I make assignment (insert into UNSAccountBInUNSGroupB) the processes are generated despite generation condition with the variable check. I suppose that event ASSIGN is sent somewhere outside of my connection and the condition is true. 
 How can I suppress process generation in that case? 
 Thank you

Markus Weiss-Ehlers · Accepted Answer

I have talked to some guys internally and here is your solution. 
 You just need to set the property XIsInEffect to 1. But a normal user account is not allowed to set this property. If the script is executed by the Job Service using the component authenticator you should be able to set the property. 
 If you want to test the script in the System Library, you have to use a system user with the flag IsServiceAccount set.

Markus Weiss-Ehlers · Answer

Hi Sergey, 
 
you need to set the session (connection) variable FULLSYNC in addition as described in the threat.

Markus Weiss-Ehlers · Answer

Hi, 
 the event ASSIGN will be generated because the flag XIsInEffect was changed to 1 by the DB Queue processor calculation after you have created the assignment. 
 To avoid that behavior in your fullsync script, you need to set the properties XOrigin and XIsInEffect properly when you create the objects in UNSAccountBInUNSGroupB while having the connection variable FULLSYNC in place.