Formedix ryze release notes 5.1.3 - Formedix community
<main> <article class="userContent"> <p><strong>Release date</strong></p><p>16 June 2021</p><p> </p><p><strong>Changes</strong></p><p>None</p><p> </p><p><strong>Fixed Issues</strong></p><p>FP-7644 Viewing assets with certain rule configurations can cause the app to slow</p><p>FP-7651 Duplicate standards could be created during publishing in some occasions</p><p> </p><p><strong>Known Issues</strong></p><p>FP-6268 Editing asset labels is not reflected in the dashboard history or favorites</p><p>FP-6441 Some non English language characters are not displayed correctly in change request emails</p><p>FP-6486 Paths don't show on origin document errors</p><p>FP-6546 Assets and asset groups are not added to the dashboard history after creation</p><p>FP-6681 Asset 'Updated' property isn't always correct following the update of a child asset</p><p>FP-6784 Assets within published standards are not shown in the asset search when the 'Standard' filter is used</p><p>FP-7016 Some repository log filters return additional results</p><p>FP-7048 Some relationships within analysis result child assets are not displayed correctly</p><p>FP-7246 Some change request summary filters return unexpected results</p><p>FP-7274 Terminology repeat 'other' term relationship lost when assets are imported separately from a standard</p><p>FP-7277 Completed version change request filter does not work for all change request types</p><p>FP-7407 Assets can sometimes be incorrectly flagged as a deviation from the standard</p><p>FP-7421 Incorrect asset search results when combining certain filters</p><p>FP-7432 Protocol name can be incorrectly reported as missing during validation</p><p>FP-7445 Analysis variable can be removed from an analysis result even when a 'required' rule is present</p><p>FP-7456 Subscription options missing from event description filter in admin logs</p><p>FP-7505 Custom attribute changes not always reflected when asset group validation is run</p><p>FP-7527 Parexel DataLabs Minimum Length custom attribute on question assets cannot be used</p><p>FP-7528 Downloaded container logs do not always contain all entries</p><p>FP-7532 Medidata Rave asset group level master custom attribute changes not always reflected in related custom attributes</p><p>FP-7535 Variable dropdown in where clause in selection criteria is limited to 100 options</p><p>FP-7544 Assets are sometimes being auto-selected for import in error</p><p>FP-7553 Asset comparison sometimes shows differences when there are none</p><p>FP-7558 View source button in relationships tab does not work when viewing derived or variant assets</p><p>FP-7559 Asset cannot be selected when creating a change request in some instances</p><p>FP-7560 Container label changes not always reflected correctly in change request details</p><p>FP-7562 Incorrect system version reported in logs</p><p>FP-7563 Erroneous log entries are created when a new user group is created in the admin section</p><p>FP-7564 All user group log entries are returned when the system or system version filters are used</p><p>FP-7570 Unable to add a document to an origin from the asset overview</p><p>FP-7574 A selection criteria where clause doesn't keep its rules when imported to a study</p><p>FP-7580 Associate asset dropdown list does not always display the correct content</p><p>FP-7586 Versions section within asset relationships fails to load in some circumstances</p><p>FP-7587 Invalid values can be entered within range checks</p><p>FP-7588 Incorrect rule types available on key sequence property</p><p>FP-7593 Asset has been updated notification sometimes shown in error</p><p>FP-7622 Completed version property within change requests cannot be saved if it is the only edit</p><p>FP-7636 Values for description custom attribute for Dataset Mapper plugin removed within variables when the same custom attribute is used at the dataset level</p><p>FP-7647 Units cannot be assigned to individual range check values</p><p>FP-7655 UI does not always show all selected values in multi-select custom properties within change requests</p> </article> </main>