Calyx RIM 7.1.8 Resolved Issues
Calyx RIM 7.1.8 resolves the following issues.
Publishing
| Issue | Description |
|---|---|
| DE28921
[INC0139947, TASK0045320, INC0136904, TASK0045184] |
After replacing a PDF file in the output location and the recalculating checksum, the wrong checksum was displayed in the XML. This issue is resolved. Now, the correct checksum is displayed in the XML after recalculating the checksum. |
|
DE28912 [INC0139930, TASK0045319] |
In two parallel submissions, a replaced leaf was not copied to a working assembly after synchronizing with the submitted view. This resulted in incorrect assembly structure. This issue is resolved. Now, the submitted view synchronization process works correctly and the assembly shows the correct structure. |
|
DE28846 [INC0127050,TASK0044604] |
When publishing STF, the output STF XML file name was being normalized differently than the reference to the STF XML file name in the index.xml file. As a result, the link in the index.xml file to the output STF XML file was broken. Additionally, the normalization method used to create the STF XML file name was determined by the XML definition files assigned to the assembly in Publishing Settings and not the Assembly Type value that is used to determine how to normalize non-STF file names. This sub-minor release now uses the Assembly Type value to determine which normalization method to use for all output file names (including the STF XML file name) as it was in Calyx RIM 6.2. See Assembly Template Attribute . |
| DE28730 | If assembly contains both target and reference leafs, output location was not populated for a reference leaf if the target leaf was replaced. This issue is resolved. Now, the output location path contains the correct value. |