You can specify the workstep template priority in two ways: either by reading a range of hard-coded values from the oebps.conf file or by using the mapped dataslot.
The workstep template priority has four default options:
Low
Medium
High
Critical
Depending on the requirement, you can also define your own priorities in the configuration file OEBPS_HOME\conf\oebps.conf. However, in this case, once the applications are installed and used, the priority option should not be changed.
You can map workstep priority either to an ABL CHARACTER dataslot so that you can dynamically assign a priority to a workstep.
Whenever there is a change in the workstep template priority value, you must perform a process refresh to make the changed priority effective. For example, in the case of hard-coded values, if you change the priority of a workstep from ‘High’ to ‘Low’, then you must perform process refresh. Similarly, in the case of a mapped dataslot, if you change the priority of a workstep by changing the mapped dataslot from ‘@stringDS’ (a CHARACTER dataslot) to ‘@stringDSNew’ (another CHARACTER dataslot), then you must perform process refresh.
Note: Priority is not case-sensitive.
public java.lang.String getPriority()
BP Server enables retrieval the priority associated with a workstep template with this API.
public String getMappedPriority()
BP Server enables retrieval the dynamically assigned priority associated with a workstep template with this API.
Note: If you change the priority of a process template, then it does not affect the priority of the corresponding Workstep Template.
Low