4.2 Release notes - 6th June 2016

You can create widget to monitor successful Processes, failing Processes, errors, and Process executions

  • It is possible to promote results of a Task or an entire Process

  • These promoted values can be seen in the Process instance view and used to filter them

  • They can also be used in silence monitoring rules

  • Process instances moved from their own view to the Process list view as a sublist

  • Clicking the arrow in front of the Process name or anywhere on the background of the Process, opens the Process instance list below the Process name

  • The user can choose what information is shown in the list

  • The instances can be filtered with dates and information in, for example, promoted values

  • Clicking on the Process name opens the Process editor

  • Silence Monitoring Rules

  • The rule will compare the count, distinct values, or minimum, maximum or sums of promoted values, and send an alert if the rule is not met

  • The UI indicates whether Agent Process configuration is out of date

  • The UI will inform the user if updating or activating a Process is not complete in the Agents in the environment

  • Hide passwords from showing in the UI by using 'secret' environment variable type

  • The user can write a description for Tasks in the Process editor

  • The user can check which Task packages have a newer version available and can choose what Tasks are updated

  • Tasks grouped according to NuGet package in Task view

  • Parallel foreach loops allowed

  • Triggers made more reliable and usable

  • Parameter change to or from array type fixed

  • Cobalt editor now saves parameter changes after updating the Tasks

Breaking changes

If you use 'secret' environment variables, the process must be compiled with 4.2 or later. For example, changing an existing password environment variable to 'secret' may cause runtime errors if the field is used by processes compiled in older versions.

4.2 Service Release 1 - 28th June 2016

  • Maintenance release, with fixes for:

  • Process listing performance: list will be shown even if counts take long to fetch

  • Unmanaged DLLs in task packages do not cause problems with delpoying processes

4.2 Service Release 2 - 14th September 2016

  • Maintenance release with fixes mostly to the memory usage of the agent and performance of the web UI:

  • Old, unused process versions are now periodically unloaded from agent memory, so agents running for months do not use up too much memory

  • You can further reduce agent’s memory usage by installing shared library DLLs to the global assembly cache of the machine

  • Process instance counts are now stored in the database to speed up the process list load time

  • Process instance list load times are also reduced by changing to a simpler pager that does not need to calculate the total number of instances

4.2 Service Release 3 - 5th October 2016

  • Performance fix release. The fixes include:

  • Process list is now paged. This greatly speeds up rendering of the list if there are > 100 processes.

  • Drastically reduced web server memory usage

  • Building and deploying new versions of processes is faster on on-premise installations with a lot of deployed process versions

Also as a small fix, you can again query for a specific process execution graph by the execution GUID, in order to e.g. generate links to the process in error emails. You get the execution GUID in process via the #process.executionId reference, and the link would be in format

https://<website>/ProcessInstance/Instance/<execution guid>

As a small breaking change, for performance reasons, audit logging all actions to the database has now been disabled by default. If you need it, to turn it on again, you need to set the EnableAuditLogging option in web.config to “true”.

4.2 Service Release 4 - 27th October 2016

  • Maintenance release with fixes for:

  • Showing executed decision branches correctly

  • Allowing import of tasks referencing NuGet packages that also have references to netstandard packages

  • Improved performance for instance count query

4.2 Service Release 5 - 29th November 2016

  • This version fixes a problem with automatic retries in the internal service message processing: in case of some transient errors, the message processing would not get retried, which could cause configuration or log messages not being processed at all. This could then lead to e.g. process versions not getting deployed correctly or processes seem to never finish.

  • Other changes and fixes in the release include:

  • Array parameters of a task (e.g. Cobalt’s message processing steps) are no longer cleared when you update the task version

  • SQL query performance tweaks

  • The authorization.config file can now be used for defining authorization rules in on-premise installations for easier editing

          

Did this answer your question?