...
Support for Loading Data into a Partitions Other than the Primary Partition for Warehouse NavMonthEnd and NavMulti
Data for the Warehouse NavMonthEnd and NavMulti feed types was previously being saved only to the first partition in the database due to logic pertaining to the partitions getting ignored in the rules.
The inbound Inbound Warehouse rules were changed to support the loading of data into partitions other than just the primary partition.
Files changed:
- xml-dbdirect_common.inc
- bind_wrhs_nav_me.xml
...
</taskParameters>
</EagleML>
Note - the stream name parameter is required and should always be set to eagle_mc_server_support as shown in the RTR above.
Files changed:
eagle_mc_server_support.rsf
eagle_mc_server_support_stream_disable.xml
...
Delete accounting trades positions via default workflow 'eagle_wrf_generic_delete'
Deleting accounting trade positions was only possible through a panel which required manual execution. Deleting positions would be much easier and quicker if the process could be automated.
The eagle_wrf_generic_delete workflow and the eagle_ml-2-0_default_in_xml_delete_objects stream were enhanced withthe with the eagle_wrf_generic_delete_accounting_objects.wrf and the t_eagle_ml-2-0_default_in_xml_delete_accobject.xml rule. This enhancement made it possible to delete trade positions via the generic delete workflow.
...
Ability to Send User Data from Automaction Automation Center/Scheduler to the Schedule Stream
User data which was defined in automation center for _schd (_restart) stream was being ignored.
Changed logic in the "workflow_restart.sch" and "workflow_restart.xml" rules to transfer and add user parameters from Automation Center into an RTR as task parameters.
...
Added Parameter in the w_config_custom include to Suppress Intermediate TSR
There were processing delays and failures when gnerating generating a high volume of TSRs during loads. 18 thousand records could generate 52 thousand TSRs.
A new parameter was added to reduce the number of TSRs generated by simply not creating intermediary TSRs and only sending the final TSR.
The InternalTSRGeneration parameter with values of “Y” and “N” may be added to the incoming file. If set to "Y", there will be one ACK and one TSR message in the local and FTP folders. A valud value of "N" will maintain the default bahavior behavior of many intermediate TSRs being generated.
...
Added eagle_default_bbca_helper stream to the EagleML package as a core stream.
There was a request to add the bbca_to_tagvalue stream to the core EagleML package. To conform to naming conventions the The stream was first renamed to eagle_default_bbca_helper to match the current naming convention.
The eagle_default_bbca_helper stream was added to the core EagleML package.
...
Remove Unneeded XML Aliases for the IssuerRole Feed
Unneeded XML aliases were overwriting the mapping for some of the required XML aliases because both of them were using the same ALIAS values.
Unneeded XML aliases from the IssuerRole object.
...
This issue was tracked as Item #162378.
Fixed Problem with Resolved Processing for the EagleML User Feed Type Insert/Update on MC2017 2017 Versions
The EagleML core code didn’t did not have mapping for tag990, but this tag is required in the 2017 version of the panel. The original name of element was listed as: <relarionshipInstance>.
Mapping for tag 990 was added for User in the xml-user_user.xml rule.
The name of element has been fixed to <relationshipInstance> in these rules:
t_user_user_streaming.inc,
t_user_group_streaming.inc.
The eagleml-user-shared-2-0.xsd was also fixed to include the correct name of the element:
<xsd:element name="relationshipInstance" type="xsd:integer" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Relarionship Instance - if groupCode = 'PaceRole'</xsd:documentation>
<xsd:appinfo>Is Primary Role</xsd:appinfo>
<xsd:appinfo>PACE_MASTERDBO.PACE_USER_ROLE_DETAILS.INSTANCE</xsd:appinfo>
<xsd:appinfo/>
</xsd:annotation>
</xsd:element>
...
Added New Value(P) for ExtractLevel Parameter
The default behavior for the ExrtactLevel ExtractLevel parameter value of A was changed. The inner join to the POSITION_DETAIL table was replaced with a left join.
A new value, “P”, was added to follow the same logic as the “A” value did previously.
This issue was tracked as Item #162662.
EJM
Included Entity Filter UserGroup didn't Work Support for the SMFExtract when Executing the extract in HeldOnly Mode
An SMFEXTRACT in HeldOnly heldonly mode should have requires the ability to use the UserGroup entity filter. This functionality was not working properly.
Support for this filter capability was added to the Held filter logic.
...
Fixed Logic for Naming EJM Supplementary Files
In EJM the
The standard behavior in EJM is to send a trigger file to the incoming folder of each sub process in a workflow. The name of each subsequent file would be was generated based on the name of the trigger used for the previous sub process with an appended time stamp. In the case that When there were a large number of sub processes in a workflow the names of the trigger files would eventually exceed the file name character limit.
...