#DCR Active Repository

DCR Active Repository

The purpose of the DCR Active Repository is to make it easy to leverage DCR as the rules foundation for an Adaptive Case Management system.

You can access your DCR Process Model from a RESTful API currently supporting these functions.

Find information in Swagger format here.

  • Create a DCR Process Model
  • Update a DCR Process Model
  • Get a DCR Process Model
  • Instantiate a DCR Process Modelfor simulations and instances
  • Get information about instance status, i.e. whether the process is completed or not. We refer to this as "isAccepting"
  • Get Enabled or Pending Events of a DCR Process Model instance
  • ExecuteEvent of a DCR Process Model instance
  • Advance time of a DCR Process Model instance

Related Release notes

Release 7.0.3

  • Improved activity editor
  • More FEEL functions - more business value
  • Ability to view who has created revisions

Related Videos

No related videos found.

Related Articles

No related articles found.

Using the RESTful API we’ll implement all elements of the RESTful API supporting collections of Process Models, Process Model instances and events. Using the RESTful API Process Models can be modified, instantiated, executed etc.

An example of how to use DCR Active Repository using the Postman tool can be found here.

Access to DCR Active Repository requires your DCR username and password and use http basic authentication. Access to the repository requires a commercial license. Acaademic alliance partners can also use the repository for academic research and teaching.

The engine API interface outlines the programmatic interface.

DCR Process Models
*List URIs of process models, id and titles in collection. Filter options exists to search/filter specific process models. Optional parameters are:
title=title – will search for procss models containing “title” in title
sort=title (default) –
sort process models by title or other fields
sort: can be title, id, created, modified
orderby: asc or descGiven “CategoryId=123” will return all process models found in the category with the internal id “123”.The parameter “?Filter=CommunityUsage” will return data about the usage of the process model.
NA *Create a new DCR Process Model, returning the id. A DCR Process Model is described using DCR XML Ability to create new graph as copy from another graph, and place graph into specific category on creation (DCRSOPCategory). Title attribute to give graph new title on creation, NA
DCR Process Model
*Retrieve the DCR Process Model represented as DCR XML
If sending the parameter “?LatestMajor=true” the repository will return the latest major version of the Process Model.”filter=splice” will splice any fragment into the main model.”filter=localecsv” will return a CSV file for DCR Forms for localization.Always return Last-ModifiedDate of the graph.
*Update the DCR Process Model using DCR XML

* CategoryId=…, if send it will place graph in the category

NA * Remove the process model
Graph to Word and Excel
* Retrieve the DCR Process Model in Word or  Excel NA NA NA
DCR Process Model Wiki
* Retrieve the DCR Process Model in wiki format NA NA NA
DCR Process Model Image
* Retrieve the DCR Process Model as an image NA NA NA
DCR Process Model versions
*Retrieve the versions of the DCR process model as outlined below.
Using the parameter “?Versions=major or All” a list of versions will be returned as outlined in below.THe parameter “Versions=major&tags=<tag1,…,tagn>” will return all major revisions with the provided tags.
NA * Create a new major revision of the graph.

* filter=compare. Compare two DCR Process Models. Either by sending the full xml (parameters BeforeXml and AfterXml) or by sending the ids of the versions (parameters BeforeId and AfterId).

DCR Process Model version
*Retrieve the version XML of the specific DCR Process Model.

If “?RevisionXml=true” it does not return the Process Model xml but the comparison of the latest major revision.

DCR Process Model version wiki
Retrieve the process model in DCR wiki format NA NA NA
DCR Process Model meta data
*Retrieve meta data about the specific DCR Process Model. XML example below. NA NA NA
DCR Process Model instances
*Retrieve the DCR Process Model instances, i.e. instance id (simid) and title. Various filters exists to retrieve representative and swimlane process models:
isScenario=true or false – if true returns only scenarios (representative Process Models)
Format=DCRXMLLog – optional, only used if DCR XML Log format is needed.
Format=XES – optional, only used if XES format is needed.Filename=log.xml – optional filenameThe parameter “?filter=rerun” will re-run all traces using DCR Compliance Engine.
NA *Instantiate a DCR Process Model returning a new instance ID (simid). An optional Title of the simulation can be provided.
API enhanced and now support creating multiple instances by important DCR XML Log which creates multiple instances at the same time. Use parameter Log to enable import.
LatestMajor=true” is defined the instance will be based on the latest major version of the Process Model. Initialization time can be given in JSON body as outlined below.
DCR Process Model instance
*Retrieve the DCR Process Model instance
A filter exists, ?filter=isAccepting, which will return true or false depending on whether the DCR Process Model instance is accepting or notThe parameter “?filter=rerun” will re-run the specific simulation using the DCR Compliance Engine.
*Parameter ?complete=true will mark the simulation as completed, complete=false will un-complete the simulation
Parameter ?Title=… will update the title of the simulation
*Parameter ?Log=… – will update the simulation *Delete the instance
DCR Process Model instance events
*Retrieve the events of the DCR Process Model instance
Filter must be provided to search/filter specific instances
NA *Create a new event in the Process Model using the XML in the body illustrated below under events NA
DCR Process Model instance event
**Retrieve the DCR Process Model instance event *Mark the event as excluded
Use “?filter=exclude”
*Execute the event

If you add “?filter=note” to the URL you can post a note with the event. This note will be saved as a comment in the DCR XML Log.

The role of the event can be passed in the body of the call as a JSON parameter:



*Delete the event
DCR Process Model instance relations
*Retrieve the DCR Process Model instance relations NA *Create a new relation *Delete a relation given sourceId, targetId and relation type
DCR Process Model time
NA NA *Set absolute time in Process Model as outlined in body (see details below). NA
DCR Process Model categories
* Get list of categories NA *Create a new category
DCR Process Model categories
*Retrieve specific category NA *Update category *Delete category
DCR Process Model categories
Retrieve Process Models for specific category NA NA NA
* Retrieve list of organizations

* filter=current will only return current organization

DCR Process Model categories
Retrieve Process Models for specific category NA NA NA
Create Word document from a graph
Convert graph and scenarios into a Word document NA NA NA
Create Excel document from a graph
Convert graph and scenarios into an Excel document NA NA NA
Create Word or Pdf document from a DCR Form.
Convert dcr form in a Word or Pdf document NA NA NA
Rule to string
NA NA Convert a DCR rule into a written statement in various language. Use Accept-Language in header to set locale. NA

Notice: The list of URLs is not complete and not everything is implemented at the moment. We’ve marked working areas with an asterisk (*).

DCR Process Model are represented using DCR XML which is the output of the DCR designer tool. DCR XML is used both for classes and instances of processes.

The list of Process Model returned contain the following data:


<graph id=”1234″ title=”My first graph” />

When you initialize a Process Model you can provide the initialization time in the JSON body together with the title of the new instance:

{Title: “PostMan Simulation”,
The list of roles returned contain the following data:
<role title=”user” description=”This is the user” />
<role title=”responsible” description=”The responsible person” />

The list of events returned contain the following data:

<events isAccepting=”true|false” nextDeadline=”…” nextDelay=”…” phase=”…”>

<event id=”Activity 3″ included=”true” enabled=”true” pending=”false” executed=”false” fullPath=”Activity 3″ roles=”” groups=”” description=”” label=”Activity 3″ eventType=”” />
<event id=”Activity 5″ included=”true” enabled=”true” pending=”false” executed=”true” fullPath=”Activity 5″ roles=”” groups=”” description=”” label=”Activity 5″ eventType=”” />
<event id=”Activity 6″ included=”true” enabled=”false” pending=”true” executed=”false” fullPath=”Activity 6″ roles=”” type=”…” referId=”…” groups=”” description=”” label=”Activity 6″ eventType=”” />

The “type” attribute can be “subprocess”, “form”, “nesting”, “instance” or just empty.

The referId attribute points to a graphId – only supported for DCR Forms.

The Execute event takes optional data parameters in the form:
{DataXML: ‘<globalStore><variable id=”‘eventid'” type=”…” value=”…” isNull=”true|false”/> </globalStore>’,
Role: ‘role }

The set absolute time of a Process Model post the following data in the body: <absoluteTime>ISO 8601 time here</absoluteTime>.
Notice – time must be GMT+0, i.e. not local time zone. Format is ISO 8601, i.e. yyyy-mm-ddTHH:MM:ssZ etc.

The data should be in JSON format so in fact we send e.g.

time: ‘<absoluteTime>2018-09-05T10:40:27.9197330Z</absoluteTime>.‘ }

Deleting relations take the following JSON structure as a body:
{ sourceId:”Activity1″, targetId:”Activity0″, type: “condition” , }

type is the relationType which can be one of the following values “condition”, “response”, “include”, “exclude”, “milestone” or “spawn”.

The RESTful API will be expanded to include all events and relations of Process Models as well as simulations/instances, thereby enabling adding, updating and removing events and relations directly.

Versions are returned in the following XML:
<versions >
<version id=”64774″ type=”major” title=”First major version” date=”2018-10-01” user=”6″ />
<version id=”64772″ type=”minor” date=”2018-10-01” user=”4″ />
<version id=”64770″ type=”minor” date=”2018-10-01” user=”4″ />

We’ve created a Windows application for DCR Active Repository that you can use to experiment with the DCR Active Repository. The source code in C# is available for download.

Meta data about a Process Model returns the following XML:

<graph id=”4013″ title=”Expense – milestone – good coding practice”>
<Collection id=”1952″ title=”DCR Academy” ></Collection>
<Category id=”2252″ title=”DCR Academy – Public Repository” >
<user id =”107″ UserName=”hnor” ModeOfSharing=”CanEdit”></user>
<user id =”1526″ UserName=”” ModeOfSharing=”CanEdit”></user>
<user id =”4″ UserName=”marquard” ModeOfSharing=”CanEdit”></user>
<Owner id=”4″ UserName=”marquard” OrganizationId=”1″ Organizationtitle=”Community” ></Owner>
<user id=”42″ UserName=”Hamza.Ahmad” ModeOfSharing=”CanEdit” ></user>

Accessing this API requires a commercial license.