TAIL Logging Customization In MDM AE- Case TS000044672

The issue occurs during tail logging when a requester is part of multiple userRoles.

We have multiple userRoles in DWLControl to which user is associated and the RoV rules are applied on those groups. There are some users (super users) who are part of more than 35 such groups.
During Tail logging all userRoles are concatenated and stored in USER_ROLE column in TRANSACTIONLOG table. We have already increased the length of this field from 50 to 1024 but still it is insufficient.
So we were trying to customize the TAILTransactionComponent or TAILTransactionLogBObj to truncate the USER_ROLE field, but it seems we are not allowed to customize those classes due to plain initialization in code.
The TAILTransactionComponent just concatenate all the userROles and then tries to persist it in database which is not proper. As the number of uerRoles increases the length of USER_ROLE string to be persisted keeps on increasing, resulting the database column length becomes unpredictable.

Creating a behavior extension will not resolve this issue because the TAILTransactionLogBObj is being created in postExecute() method. Even if we create a behavior extension (post-execute) it gets executed before the instance of TAILTransactionLogBObj is actually created ( in TAILTransactionComponent.convertToTransactionLogBObj() during postExecute).

If we see the sequence during postExecute
1) execute all behavior extensions (OOTB and user defined).
2) Invoke RoV restrictions ( which is again a behavior extension)
3) Perform TAIL logging

So I don't see a way where I can access TAILTransactionLogBObj created at the last step.

We are aware of the procedure to extend the OOTB components in MDM, but this is possible only when the initialization of the component is done using the DWLClassFactory.getDWLComponent("Component_property_key") (the factory model).
But in this case the object initialization was done using "new" keyword which somehow does not allow us to override the OOTB component.

Refer Case TS000044672.