OEBPM: WORKSTEPNAME system dataslot can't be passed to sub-process

System dataslot ProcessInstanceid can be passed from one process to another by merely adding it to dataslots and casting it to a different name. One should expect the same behavior from system dataslot WorkstepName, but it fails

Jan 30, 2018
Knowledge

Title

URL Name

workstepname-system-dataslot-can-t-be-passed-to-sub-process

Article Number

000117081

Environment

Product: OpenEdge BPM Version: 11.5 and later OS: All supported platforms

Question/Problem Description

System dataslot PROCESS_INSTANCE_ID can be passed from one process to another by merely adding it to dataslots and casting it to a different name.
This is not the case for WORKSTEPNAME system dataslot.
Passing the WORKSTEPNAME system dataslot from one process to another instead requires setting up user-defined dataslot in first process and setting a specific javascript.

Steps to Reproduce

Clarifying Information

System dataslot PROCESS_INSTANCE_ID can be passed from one process to another by merely adding it to dataslots and casting it to a different name.

Error Message

Defect Number

Defect PSC00361222

Enhancement Number

Cause

The exact cause is not known at this time.

Resolution

Until the fix is available, use the workaround below.

Workaround

Create a custom dataslot callerWorkstepName to store the value of the WORKSTEPNAME, and use it as input to sub-process 2 workstep created in Process 1.
Passing the callerWorkstepName value from Process 1 to sub-Process 2 is then achieved with a Before Activation script.

In Process 1:

Edit Before Activation > Other > Custom > Custom Script (one line) as follows:

jst.putDataSlot("callerWorkstepName",jst.getWorkstepName());

In the sub-process workstep Process 2, use callerWorkstepName as the Input Dataslot.
Save and Publish.

In Process 2:

Create a CHAR dataslot callerWorkstepName.
Add this dataslot on some workstep to verify if the correct workstepname from Process 1 has been transmitted.
Use this dataslot for the conditional operations you wish to perform from the Process 2.

You can add the field on any of the worksteps to verify that the correct Process 1 workstepname has been passed.

Notes

Progress Article(s):

OEBPM: Unable to assign the value of WORKSTEPNAME to a user-defined dataslot.

Keyword Phrase

Last Modified Date

11/20/2020 7:11 AM

OEBPM: WORKSTEPNAME system dataslot can't be passed to sub-process

Files(0)

Was this article helpful?

Was this article helpful?

OEBPM: WORKSTEPNAME system dataslot can't be passed to sub-process

Information

Related Articles