New

 DCM Lists Component

To accommodate DCM 2.0 and improve separation of concerns, the DCM Lists Component has been split into two modules: The DCM Lists Client Component and the DCM Lists Publisher component. The DCM Lists Client Component is responsible for retrieving list data and presenting it to the user while the DCM Lists Publisher Component is responsible for updating the DCM Lists Service with case or task changes. For more information visit DCM Lists Components (14.6+).

Timeline SQL Store Component

Until this release, the Trace SQL Store component was needed to provide SQL storage for both Trace information and Timeline information. This tight coupling could lead to some unwanted side effects:

• It was not possible to store either Trace information or Timeline information. Both had to be enabled, which would cause unnecessary data to be stored.
• When Trace information was traced using the Trace Event Publisher Component, it would not be possible to store and retrieve Timeline information in a database.

In this release, we separated the timeline data storage from the Trace SQL Store component to the Timeline SQL Store component, to provide a greater flexibility in configuring trace and timeline separately.

Check the linked pages and the Release 14.6 Upgrade Instructions for more information on how to configure the timeline separately from the trace.

Note that there are some backwards compatibility measures in place, so if you have a project that doesn't contain custom code, the trace and timeline storage will behave like they did before.

 Blueriq Development Dashboard - New widget

In this blueriq version we added a new widget to the Runtime Development Dashboard; the Exposed Blueriq functions. It works equal to the Exposed Blueriq webservices widget. The new function widget helps you get the url and parameters for the functions that you explicitly want to expose 'as a webservice' for testing purposes. More information about Functions can be in this section: Functions and function calls.