A new version is just around the corner! Today we’ll look at all the great new things you get when you update to 4.2.
There’s a completely new view called the Dashboard view. It is in its early stages and the look and feel will change in the future, but the basic functionality is there.
The dashboard view with different widgets. The green widget is the successful processes widget and the red one the failed processes widget. Below them is the Errors widget and to the right the Process execution graph.
The dashboard view is completely customizable. You can add as many different widgets there as you wish, and position them freely how you see fit. The configuration is currently user and browser specific, so if you want your dashboard to look the same, use it on the same browser with the same login information.
Currently there are four kinds of widgets available:
- Successful processes widget shows the amount of successful processes in given environment(s). You can set the environments which it will show the successful processes for, as well as the time limit for which the number is shown.
- Failed processes widget works exactly like the successful processes widget, only for failed processes.
- Errors widget shows the errors for given environment(s). Again, you can freely choose which environments the errors are shown for. You can investigate and dismiss errors via this widget.
- Process executions graph shows either the successful processes or failed processes in the environment(s) you choose. You can also set the time limit for which the process executions are shown as well as the time interval for which they are depicted.
As mentioned before, the look and feel of the view will be updated and there will be more widgets to choose from in the future.
The process view has changed a bit from 4.1. Now the process executions list can be seen below each process name when the row, or the chevron in front of it is clicked. Now clicking the process name takes you straight to the process editor.
Clicking on the chevron in front of the process, or just the row, will open the process execution list below.
As a user you have a lot of options in this view as well. First, you can chooce which columns are shown in the list. The default options are presented in the picture on the right.
By default only the State, Start time, Duration, and Error info are shown. On top of those you also have Id, Version, Trigger, and Agent columns to chooce from.
You can also filter the items on the list. By clicking on the “Filter” button, depicted in the top right corner of the list view, you open the filtering options. The options include the start and end time for the time period under observation. There’s also a text filter with which to filter the instances based on the text in Error column and the promoted value columns.
The filtering options include start and end dates and a text filter.
The list also shows whether the agent has the most up to date information or not. First of all, if the agent has been inactive for a long time, it is shown at the top of the view. The user is also notified whether the latest changes to the process configuration or trigger state has been updated to the agent.
If the agent is offline or not responding, this message is shown at the top of the process view.
When the process is updated on the UI, but not on the agent, the message “Updating to version X” appears next to the process name. When the agent is up to date, only the version number is shown.
When the process configuration is not updated to the agent, the message “Updating to version X” is shown.
Similarly, when the triggers are activated, they might not be immediately active on the agent. When the trigger is activated, it is first shown in grey, so that the user knows it is activated, but the agent is unaware of this. When the agent has activated the trigger as well, the trigger turns blue.
In 4.2 it is possible to promote the results of a process or a single task or scope of a process. These values can be viewed in the process execution list and they can be used in monitoring rules (explained below.)
The third field from the top is the selection which promotes the value of the task. In this case it is named “developer actions”.
In the process execution list, you can choose the promoted value as one of the columns. They appear at the bottom of the column selection list. By selecting the values to be shown in the process execution list, you can view the return value of the task, scope, or process.
Promoting certain values makes it possible to monitor those values. It is possible to merely observe that the value exists, or to set different requirements for the value itself. It is also possible to set a rule to monitor the number of values passing that criteria or, again, monitor the sum or minimum or maximum values of the values passing the criteria.
An example of a monitoring rule.
It is possible to just generate the graph and look at when it meets the rule and when there are errors. It is also possible to set the rule to send an email alerting the relevant people when the rule isn’t met.
Miscelaneous smaller improvements
There are numerous smaller improvements done to the UI. Here are the biggest improvements.
Comments for tasks
It is possible to write comments for single tasks, which can be seen when the mouse is hovered over the task in the editor or execution graph.
On the left is the editor where the comment can be set. On the right is the comment which can be seen when the mouse is hovered over the task.
Major and minor versions for processes
It is now possible to set the major and minor version number for a process when saving it. It is also possible to switch between versions through the actions menu.
Above: It is possible to chooce the version for the process. Below: The version will be shown after the process name. The first number is the major version, second minor, and the third is a running number the user cannot set.
Task parameter descriptions
If task parameters are commented in the NuGet package, those comments will be shown when the mouse is hovered over the parameter name in the process editor. Otherwise the parameter’s type is shown.
Task package descriptions
The task packages can be described in a comment in the NuGet package. That description will be shown in the task view.
Now it is possible to check whether tasks can be updated with the click of a button. On the top of the Tasks view is a button labeled “Check for updated packages”. When it is clicked, it checks whether any packages can be updated. If they can, an “Update” button will appear next to the package name, as can be seen in the picture above.
So hold tight: 4.2 is coming soon!