Categories
#Activities #DCR Concept - DCR Semantics #Effect #Robot #Roles

Roles for activities with effects (KMD WorkZone)

This page describes which role to put on an activity depending on the
effect it carries, when the graph runs inside KMD WorkZone.

TL;DR

  • Robot/LocalRobot must not be used on static effects.
  • AUTO/L-AUTO must not be used on dynamic effects.
  • Any activity carrying System, AUTO, L-AUTO, Robot, or
    LocalRobot is hidden from the user in WorkZone 2025.3+.

Static vs. dynamic effects

  • Static effects are the "old" effect implementation provided by KMD WorkZone itself.
  • Dynamic effects are implemented by the DCR Workflow effect
    subsystem. Dynamic effects provide both functionality not available in Dynamic effects (HTTP, Mail) and in-graph error reporting.

Prefer dynamic effects if in doubt.

Role semantics

Role Used for Behaviour
AUTO Static effects WorkZone auto-executes the activity when it is included and enabled. Hidden from the user.
L-AUTO Static effects WorkZone auto-executes the activity when it is included, enabled, and locally pending. Hidden from the user.
Robot Dynamic effects The DCR runtime auto-executes the activity when it is pending and enabled. Hidden from the user.
LocalRobot Dynamic effects As Robot, but only when locally pending. This is the closest analogue to L-AUTO; if in doubt, use this one.
System Others Marks the activity as system-internal. Hidden from the user (WorkZone 2025.3+).

Recommended roles

Activity Role Comment
With static GetValue effect System WorkZone always executes this regardless of role; System documents intent and hides the activity.
With static ValidateEntities effect System Same as GetValue.
With any other static effect AUTO or L-AUTO Required for WorkZone to auto-execute it. Use L-AUTO if it should fire only while locally pending.
With any dynamic effect Robot or LocalRobot Dynamic effects must be triggered by the runtime. LocalRobot mirrors L-AUTO; pick it when in doubt.
Recipient for WorkZoneCase System Required. See below.
Plain user activity (no effect) any user role Behaves normally; visible to users.

The WorkZoneCase activity

The graph must contain an activity with:

  • Name: WorkZoneCase
  • Datatype: Text
  • Role: System
  • Initial state: included and enabled (a self-exclude relation is allowed)

Refer to it as $(WorkZoneCase) where you previously wrote {Case.ID}.

Related Release notes

Release 7.6.9

  • Welcome to DCR Effect Wizard

Related Videos

Portal 7.6.5 release webinar

https://www.youtube.com/5arjL2cyD1M

 

Related Examples

Related Articles

No related articles found.