|
| 1 | +--- |
| 2 | +title: "September 9, 2024" |
| 3 | +filters: |
| 4 | + - tachyons |
| 5 | +--- |
| 6 | + |
| 7 | +## Release highlights |
| 8 | + |
| 9 | +We've expanded functionality in the {{< var vm.platform >}}, including a more extensible version of risk areas that allows you to customize guidelines associated with your validation templates, as well as the ability to reset your model workflows. |
| 10 | + |
| 11 | + |
| 12 | +<!--- |
| 13 | +PR #906: Added new page to manage Risk Areas and guidelines |
| 14 | +URL: https://github.com/validmind/frontend/pull/906 |
| 15 | +Labels: enhancement |
| 16 | +---> |
| 17 | + |
| 18 | +### Manage validation guidelines |
| 19 | + |
| 20 | +:::: {.flex .flex-wrap .justify-around} |
| 21 | + |
| 22 | +::: {.w-50-ns} |
| 23 | +We've expanded on our risk area functionality and added a new page to your Workplace Settings: **Risk Areas & Validation Guidelines**. |
| 24 | + |
| 25 | +This replaces the old Risk Areas set up under **Organization**, and allows you to customize guidelines associated with your model validation templates. |
| 26 | + |
| 27 | +<form method="get" action="/guide/model-validation/manage-validation-guidelines.html" target="_blank"> |
| 28 | + <button type="submit" style="color: white; background-color: #de257e; border-radius: 8px; border: none; font-size: 16px; padding: 6.25px 12.5px; margin-left: 16px; margin-bottom: 20px;">Manage validation guidelines</button> |
| 29 | +</form> |
| 30 | + |
| 31 | +::: |
| 32 | + |
| 33 | +::: {.w-50-ns} |
| 34 | + |
| 35 | +{fig-alt="A screenshot showing the Risk Areas & Validation Guidelines in Workspace Settings"} |
| 36 | + |
| 37 | +::: |
| 38 | + |
| 39 | +:::: |
| 40 | + |
| 41 | + |
| 42 | +<!--- |
| 43 | +PR #921: Added "Reset Workflow" on the model inventory page |
| 44 | +URL: https://github.com/validmind/frontend/pull/921 |
| 45 | +Labels: enhancement |
| 46 | +---> |
| 47 | + |
| 48 | +### Reset your model workflow |
| 49 | +:::: {.flex .flex-wrap .justify-around} |
| 50 | + |
| 51 | +::: {.w-70-ns} |
| 52 | + |
| 53 | +Need to start over with a model? You can now reset your model's workflow to its initial state in the lifecycle. |
| 54 | + |
| 55 | +<form method="get" action="/guide/model-workflows/working-with-model-workflows.html#reset-your-model-workflow" target="_blank"> |
| 56 | + <button type="submit" style="color: white; background-color: #de257e; border-radius: 8px; border: none; font-size: 16px; padding: 6.25px 12.5px; margin-left: 16px; margin-bottom: 20px;">Working with model workflows</button> |
| 57 | +</form> |
| 58 | + |
| 59 | +::: |
| 60 | + |
| 61 | +::: {.w-30-ns} |
| 62 | + |
| 63 | +{fig-alt="A screenshot showing the option to reset your model workflow"} |
| 64 | + |
| 65 | + |
| 66 | +::: |
| 67 | + |
| 68 | +:::: |
| 69 | + |
| 70 | +## Enhancements |
| 71 | + |
| 72 | +### Model inventory fields |
| 73 | + |
| 74 | +Previously, we used custom fields to refer to your organization's unique additional fields for models as well as the default fields provided as suggestions by ValidMind. Custom fields has been renamed to model inventory fields, capturing all additional fields, and the terminology standardized across the {{< var validmind.platform >}} and our documentation. |
| 75 | + |
| 76 | +:::: {.flex .flex-wrap .justify-around} |
| 77 | + |
| 78 | +::: {.w-70-ns} |
| 79 | +You can still require additional fields to be provided upon model registration, and work with a number of different types of fields. |
| 80 | + |
| 81 | +::: |
| 82 | + |
| 83 | +::: {.w-30-ns} |
| 84 | + |
| 85 | +<form method="get" action="/guide/model-inventory/manage-model-inventory-fields.html" target="_blank"> |
| 86 | + <button type="submit" style="color: white; background-color: #de257e; border-radius: 8px; border: none; font-size: 16px; padding: 6.25px 12.5px; margin-left: 16px; margin-bottom: 20px;">Manage model inventory fields</button> |
| 87 | +</form> |
| 88 | + |
| 89 | +::: |
| 90 | + |
| 91 | +:::: |
| 92 | + |
| 93 | + |
| 94 | + |
| 95 | +<!--- |
| 96 | +PR #929: Renamed Statuses to Model Lifecycle Statuses |
| 97 | +URL: https://github.com/validmind/frontend/pull/929 |
| 98 | +Labels: enhancement |
| 99 | +---> |
| 100 | +### Model lifecyle statuses |
| 101 | + |
| 102 | +Previously, we used resource statuses to refer to the model stages made available for use in your model workflows. Resource statuses has been renamed to model lifecycle statuses, clarifying their function, and the terminology standardized across the {{< var validmind.platform >}} and our documentation. |
| 103 | + |
| 104 | +:::: {.flex .flex-wrap .justify-around} |
| 105 | + |
| 106 | +::: {.w-70-ns} |
| 107 | +- Default statuses are provided for you as suggestions. |
| 108 | +- You can add, edit, remove, and define your own custom statuses. |
| 109 | + |
| 110 | +::: |
| 111 | + |
| 112 | +::: {.w-30-ns} |
| 113 | + |
| 114 | +<form method="get" action="/guide/model-workflows/customize-model-lifecycle-statuses.html" target="_blank"> |
| 115 | + <button type="submit" style="color: white; background-color: #de257e; border-radius: 8px; border: none; font-size: 16px; padding: 6.25px 12.5px; margin-left: 16px; margin-bottom: 20px;">Customize model lifecycle statuses</button> |
| 116 | +</form> |
| 117 | + |
| 118 | +::: |
| 119 | + |
| 120 | +:::: |
| 121 | + |
| 122 | +<!-- REMOVED AFTER DISCUSSION WITH ROBIN --> |
| 123 | + |
| 124 | +<!-- ## Bug fixes --> |
| 125 | + |
| 126 | +<!--- |
| 127 | +PR #910: fix template editor showing multiorg roles |
| 128 | +URL: https://github.com/validmind/frontend/pull/910 |
| 129 | +Labels: bug |
| 130 | +---> |
| 131 | + |
| 132 | +<!-- ### Multi-organizational roles display issue |
| 133 | +
|
| 134 | +Previously, for users that belonged to multiple organizations, there was a display issue in the {{< var vm.platform >}} where your user roles from other organizations other than your actively selected organization were shown. |
| 135 | +
|
| 136 | +Now only your roles from your actively selected organization are displayed, reducing confusion around access permissions. --> |
| 137 | + |
| 138 | + |
| 139 | + |
0 commit comments