Table of Contents
Activity effects can be used to interact with third party systems such as KMD WorkZone, Salesforce, ServiceNow or SAP. DCR Open Case Manager also use activity effects to interact with systems such as Danish CPR number validation and sending letters to citizen using eBoks.
Activity effeccts are defined under resources on the graph and shown on each activity in the bottom in cursive:
When you click the activity effect, here Activityeffect, you can edit the values of the parameters of the activity effect:
Visit the graph to try it out for yourself..
The value of some activity effects refer to the value of activities within the graph and often written in a jQuery style, e.g. "$(SomeActivity)". WorkZone use a syntax like this "{SomeActivity}", "{Case.SomeField}" to refer to a field on the current case, e.g. {Case.ID}, as well as "{DCR.SomeAtivity}" to refer to an activity in a graph. For details refer to the actual definition of each activity effect in the target system.
Configuring your own activity effects
From DCR Portal 6.9 it is possible to configure your own activity effects.
A simple example is an effect that invokes a http get request in order to retrieve a value from an external service can be found under examples here.
DCR Simulator
DCR Simulator supports a range of activity effects.
The KMD WorkZone effects can be made available from the DCR Simulator for your organization. This will easy creating graphs as you can now simulate the graph directly from DCR Simulator. For details please contact your KMD representative.
Other effects available in DCR Simulator:
- CVRAPI.dk - lookup Danish CVR company name given the 8 digit cvr number
- Send an email
For details about how to configure these effects use the template "DCR Portal 6.9 Activity Effects" template.
KMD WorkZone
KMD WorkZone supports the following activity effects:
| Name | Description |
| Check | Check is the basic activity effect, which you can use for creating items on a check list. You can, for example, use it for providing information that must be read before moving on to the next activity. You can add instructions and links to more information in this activity. This is the default activity effect. |
| CompleteGraph | CompleteGraph completes the graph. You can use this activity to allow users to complete a case activity list even if some activities have not been executed, for example, if the activities were not needed in a work process. |
| CopyDocuments | CopyDocuments copies documents that are retrieved by a query to the current case. The documents are copied without the source meta data. The access code is verified on the basis of the case handler's or the case owner's access rights. For example, you can use this activity effect to copy standard documents, such as templates to a case. |
| EditDocuments | EditDocuments provides a list of documents for editing. The documents on the list are retrieved by a query, for example, documents on a specific case, documents with me as the case handler, and so on. |
| MergeDocuments | MergeDocument merges the merge fields in a document with values from WorkZone. MergeDocument merges one document at a time. The document will be merged and updated. |
| StartProcess | StartProcess starts a process or another case activity list. When a user executes the activity, the Start process dialog box opens with the specified process. |
| SendSmartPost | SendSmartPost starts a SmartPost process. In this release, you can send a letter to recipients. By default the SendSmartPost activity is executed automatically. |
| UpdateEntities | UpdateEntities updates values of specific text fields on a case, for example if you want the case title and the case state of the current case to change after an action has been completed. |
| ValidateEntities | ValidateEntities allows you to validate values on a case based on a condition that you define, and if the condition is met, the subsequent activities will be included or excluded. The ValidateEntities activity effect works in connection with guards that you define on the Include and Exclude relation effects. |
| CreateEntity | CreateEntity creates an entity, for example case, a document, a contact, or a custom type. |
| GetValue | GetValue allows you to fetch a value from an entity, for example a case. You can then use this value in guards to make conditions based on WorkZone data. If the condition is met, the subsequent activities will be included or excluded. |
| SetValue | SetValue allows you to set a value based on a query in a WorkZone field. You can use the Computations field on the SetValue activity to provide an expression, for example combining a GetValue activity and actual values. The value that is calculated in the Computations field, will be the value that will be set in the specified WorkZone field. |
DCR Open Case Manager
DCR Open Case Manager supports the following activity effects:
| Name | Description |
| Tasks | Represent an activity as a task in OCM. Ability to configure the UI of the task, i.e. the image. |
| TasksWNote | As Tasks but also edit a comment in plain text. |
| TasksWNoteHtml | As Tasks but also edit a comment in formatted text. |
| TasksWNoteFull | As Tasks but also show a comment in foramtted text as well as ability to edit the note for a long time. |
| OCMSpawn | Spawns a new instance within the same context as the parent instance. |
| UploadDocumentOCM | Uploads a document to Open Case Manager. |
| CreateCaseAcadre | Create a case in FormPipe Acadre |
| CloseCaseAcadre | Close a case in FormPipe Acadre |
| CreateJournalAcadre | Create a journal entry on a case in FormPipe Acadre |
| UploadDocumentAcadre | Upload a document to a case in FormPipe Acadre |
| CreateCaseSBSYS | Create a case in SBSYS |
| CloseCaseSBSYS | Close a case in SBSYS |
| CreateJournalSBSYS | Create a journal entry on a case in SBSYS |
| UploadDocumentSBSYS | Upload a document to a case in SBSYS |
