----------------------------------------------------- SUMMARY OF CHANGES IN RIVERWARE PATCH RELEASE 7.5.3 ----------------------------------------------------- Released October 1, 2019 ----------------------------------------------------- RPL predefined SortPairsAscending & SortPairsDescending enhancement ---------------------- The RPL Predefined functions SortPairsAscending and SortPairsDescending were modified to return stable and predictable results in the case where the second item in each pair of lists is the same. Prior to the current work, the return order of values from pairs with the same second value was unspecified and unpredictable; now that order is specified and deterministic. Specifically, for pairs whose second item is the same, SortPairsAscending now returns the first items in their original order and SortPairsDescending returns the first items in the reverse of their original order. Previously, the result tended to be in this order when the comparisons were equal. Now the order is guaranteed. This could change model results depending on the RPL logic. Examples: Given a list = {{1, "c"}, {2, "a"}, {3, "c"}, {4, "a"}} SortPairsAscending(list) returns {2, 4, 1, 3} SortPairsDescending(list) returns {3, 1, 4, 2} Issues ---------------------- The following issues were addressed: 6309: On the RPL Palette, the Else If button was not available when there was a comment. 6314: On the Object dialogs, scalar slot units were not updating correctly. 6324: An internal error could occur when opening a multi slot. 6325: Selecting a Unit Scheme exception could change the display precision. The unit scheme manager now disables editing controls for display attributes that are not shared by all selected rows. 6331: A crash could occur when clearing the workspace with the DMI Name Map Dialog box open. 6332: In a text series slot, you could not start editing by typing "O" or "I" in the slot dialogs. 6339: Distributed MRM could crash if there were no configured traces. 6340: There was an extraneous beep when loading a model file after an MRM run. 6343: Snapshot objects got coordinates of 0,0 on the geospatial and accounting views. Now, the snapshot objects are placed (in columns, ten high) to the right of the lower right corner of the bounding box around existing objects. 6344/6359: An unmatched "{" in file paths in DMI and MRM dialogs could lead to a model load failure. 6345: A crash could occur using RPL Undo on boolean expressions with parentheses. 6349: A crash could occur in Iterative MRM when Initialization rules issued an error messages. 6350: While paused in a script executed run, a crash occurred loading new model. 6353: In the "Read/Write the workbook directly" Excel Dataset option, empty cells in Excel no longer cause warnings. 6357: A crash could occur when loading an accounting model. --- [end] ---