...
Files changed:
eagle_ml-2-0_cm\wrkfl_add_log_entry.inc
eagle_ml-2-0_cm\wrkfl_cancel_log_entries.inc
eagle_ml-2-0_cm\wrkfl_get_processed_events_count.inc
eagle_ml-2-0_cm\wrkfl_read_log_file.inc
eagle_ml-2-0_cm\wrkfl_write_log_file.inc
SDP-42710: Introduction of new capabilities to supportprocessing of Multileg Corporate Actions
...
When the GenericEntity is sent without a populated entityId node, there is functionality to generate a dummy (system generated) entity Id. This method returns the next sequence “RULESDBO.ENTITY“ integer value . In some cases such as high generation, it returns non-unique values. To escape and prevent the problem, a new “GUID” method to generate a unique dummy entity id was added. It may be set as USE_GUID_AUTO_GEN_ENTITY_ID value in the <processingOptions> or set the global parameter W_USE_GUID_AUTO_GEN_ENTITY_ID variable to Y in the w_config_custom.inc. When applied, the “GUID” method will be used to generate an entity id.
...
If a twin CA record is found, check the Cp Status (tag 54).
If cpStatus of a twin CA record is PD/Pending or NC/Incomplete, then the twin CA record is deleted.
If cpStatus of a twin CA record is RD/Released, then the twin CA record is canceled.
A Delete Corporate Action announcement and Cancel Corporate Action Announcement are created. On the RD/Cancel one, it will be discovered as an issue to process if they test RD status without changing sub-priority.
Processing option should be part of the incoming file:
<referenceTransaction>
<header>
<processingOptions>CA_TRANS_TYPE_TWINS</processingOptions>
</header>
</referenceTransaction>
...