Nextmv Docs

Decision workflows are now available in Nextmv Console. You can create a new workflow from the UI and then manage the workflow like you would an application. A workflow has all of the same views as an application, except that the workflow run details includes an extra Flow view that displays a directed acyclic graph (DAG) of the workflow run.

Read more about decision workflows and how to use them in the dedicated Decision workflows section in Nextmv Docs.

Prior to this update, when you logged in to Nextmv Console, after being authenticated, you would be directed to your root account. If you wanted to switch to another team you would need to select the team from the dropdown in the header. This pattern could be laborious if you were doing most of your work in a team other than your root account.

Now, Nextmv Console will remember your last-visited team and you will be automatically redirected to this team when you log in.

Applications can write custom metrics to the run output file using the standard Statistics convention. These custom metrics live under the top-level statistics property of the run output and are extracted and displayed in the run details view in Nextmv Console.

These metrics were displayed in a technical manner using their full data path as the name of the metric. For example, if a custom metric tracking total waste was named total_waste and was a property of the custom object which in turn was a property of the result object, the name of this metric would be displayed as result.custom.total_waste.

These object data paths were obscuring the meaningful parts of the metric names, and the end user often only cares about the metric and its value, not where it’s stored in the output JSON file. For these reasons, the metrics are now displayed without the data paths and also are presented with a more human-friendly title casing.

Before

After

When creating a new acceptance test you can now specify a tolerance level for the pass/fail rules. Prior to this, you were only able to set hard rules on how a test would pass or fail. When setting the tolerance, you can define it as an absolute value (specific number) or as a relative value (percentage-based).

This tolerance will be reflected in the final chart visuals as well.

A small update to the behavior for downloading run input and output ZIP files was made. Before, when you downloaded a ZIP file from the run (input or output), the files within the ZIP file would be automatically extracted and downloaded individually.

This auto-extraction has been disabled and now the ZIP file is downloaded as a single file that you can then extract as needed via your operating system (e.g. double click the file). This keeps all of the files in a single directory rather than spreading them out wherever they were downloaded.

A new column pinning feature for table views has been added to Nextmv Console. Now when viewing table data you can select certain columns to be pinned by hovering over the column header cell and then clicking the pin icon.

To unpin the column, just click on the filled-in pin icon and the column will return to its normal location in the table. You can pin as many columns as needed.

The ability to manage secrets in Nextmv Console is now available. You can add new secret collections and assign them to instances or individual runs, as well as edit and delete existing secret collections.

Read more about how to use secret collections to enhance your app and workflow functionality in the Secrets collection reference section in Nextmv Docs.