Skip to main content

Manage workflow cases

Workflows · Cases

See every request at a glance, find out what it waits for, and get a stuck case moving again.

A case is one request running through a published workflow configuration. NIM administrators manage cases in Studio, on the Cases tab of Configuration → Workflows. Supervisors who are not administrators manage cases from a NIM App: see Workflows in Apps.

Find a caseDirect link to Find a case

Open the Cases tab. The Workflow cases grid shows the newest case first:

ColumnShows
CaseThe first eight characters of the case ID.
SubjectWhat the case is about.
Configuration and DefinitionWhat the case runs on.
StatusThe status, followed by the blocked reason, if any.
Waiting forThe open steps.
Started byThe initiator. Hover to see the e-mail address.
Started and ChangedWhen the case started and when it last changed.

Use the grid filter to narrow the list. Select the edit icon (Open the case) to open the case details.

Start a case from StudioDirect link to Start a case from Studio

To test a configuration without its start form:

  1. On the Cases tab, select Start case.
  2. Choose the Configuration. Only published configurations are listed.
  3. Select Start.

The case starts with you as the initiator and no start form data. Normally, cases are started from the start form App.

Open a caseDirect link to Open a case

The case details show Case with its short ID, the subject, the configuration and definition, the status, who started it, and the version. Use Refresh to reload and Close to return to the list.

Steps under wayDirect link to Steps under way

The Steps under way grid lists the open and failed steps. Completed and withdrawn steps are not shown.

ColumnShows
StepThe step.
Performed byThe App, the nim service, the clock with its due time, a message from a participant, or the nim service, sending a message to a participant.
Statewaiting, waiting for the service, waiting for the message, waiting for its moment, the service is running it, or failed with its reason.
SinceWhen the step appeared.

When the case waits for nobody, the grid shows This case is not waiting for anybody.

Case data and historyDirect link to Case data and history

The Case data grid shows each Variable (an asterisk marks a required one), its Type, its Value, and its Description. The History grid shows the newest event first, with When, What, Step, Detail, and Who.

What a case holdsDirect link to What a case holds

PartContents
VersionThe published version of the configuration the case runs on, such as Access request@3.
InitiatorWho started the case: NIM user ID, login name, and e-mail address, recorded at the start. Empty when the case was started by the service or the API without a user.
Subject and resultTexts built from the case data with the configuration's Case subject and Case result templates.
Case dataThe current value of every case variable, including the built-in variables.
Steps under wayThe work items the case waits for.
ParticipantsThe people resolved from case variables while the case runs.
HistoryEvery event of the case, oldest to newest.

Case statusDirect link to Case status

Show states and history reference
StatusMeaning
runningThe case waits for a person, the service, a message, or a moment. A running case can be blocked: it waits for a correction, for example because a gateway found no branch for the case data. The reason is shown with the status.
stuckNothing can continue, while the case has not finished.
completedEvery path reached an end event.
cancelledA supervisor cancelled the case. All open steps were withdrawn.

Step statesDirect link to Step states

Show states and history reference

Each step under way is a work item in one of these states:

StateMeaning
openWaiting for a performer, a message, or a moment.
runningThe NIM service is running the step's actions.
completedDone.
withdrawnNo longer needed, for example because a boundary event or a cancelling join took over, or the case was cancelled.
failedAn action, mail, or participant lookup failed. The step waits until a supervisor runs it again.

When the NIM service stops while a service task is running, NIM marks that step as failed: The service stopped while this step was running; check whether it happened before running it again.

HistoryDirect link to History

Show states and history reference

The history records these kinds of events, each with its time, step, detail, and the user who caused it:

KindRecorded when
startedThe case started.
work_item_created, work_item_started, work_item_completed, work_item_withdrawn, work_item_failed, work_item_retriedA step was handed out, started, completed, withdrawn, failed, or run again.
task_firedThe process moved past a gateway or event.
participant_resolvedNIM looked up who a participant is, including when a fallback stood in.
data_amendedA supervisor corrected a case variable, recorded as name: 'old' -> 'new'.
blockedThe case could not continue.
notifiedNIM mailed someone about the case, or explains why it did not.
completed, cancelledThe case ended. A cancellation records the reason.

When a delegate completes a step, the history shows who did it on behalf of whom.

Act on a caseDirect link to Act on a case

As an administrator, you can move a case along from its details.

Perform a user stepDirect link to Perform a user step

For an open user task, the Steps under way grid shows one button per outcome, such as Approved or Rejected, and Perform:

  • Select an outcome button to complete the step with that outcome.
  • Select Perform to open Perform step, then select Complete step.

An administrator who completes a step is recorded as the performer, not as acting on behalf of anyone.

Send a messageDirect link to Send a message

For an open message event, select Send. NIM asks: Send the message '…'? A step that waited beside it is withdrawn. Use this, for example, to withdraw a request for its initiator.

Run a failed step againDirect link to Run a failed step again

Failed step

Run a failed step again

Resolution

  1. Fix the cause first: for example, correct the target system, the script, the mail settings, or the case data.
  2. Select Run again on the step. NIM runs the step again and records work_item_retried.
Check for partial execution

Check whether a failed service task did part of its work before you run it again. For example, an account may already have been created before a later action failed.

Correct the data of a blocked caseDirect link to Correct the data of a blocked case

Blocked case

Correct the data of a blocked case

What you see

The reason is shown in red with a Correct data button.

Resolution

  1. Select Correct data.
  2. Choose the case variable and enter the new value.
  3. Select Amend.

NIM records the change as data_amended and tries to continue the case.

Cancel a caseDirect link to Cancel a case

Studio has no Cancel button. To cancel a case, use the Cancel workflow case action in a supervisor App. It withdraws every open step, sets the status to cancelled, and records the reason in the history. A finished case cannot be cancelled.

Delete casesDirect link to Delete cases

Select Delete in the case details, or the delete icon in the list. You can select several cases in the list and delete them together. Deleting removes the case and its history permanently. Only administrators can delete cases, from Studio.

caution

Deleting a case is not the same as cancelling it. Delete only test cases or cases you no longer need to account for: the history is gone afterward.