Workflow Processes (PRC)

The prc submodule of wfl owns the process definitions and the ordered process steps that drive task creation. A WFProcess names a workflow (e.g. "purchase requisition", "sales onboarding") and points at an optional input/output DomainSchema; each WFProcessStep is one step within the process — its handler (page or batch job), assignment defaults, due-day offset, and the initial task status used when the step instantiates a WFTask. The submodule depends on sys.frm for the schema, on wfl.tms for the team a step assigns to, on sys.usr for the user fallback, on com.pop for the optional notification mail group, on wfl.tsk for the task status the step creates tasks in, and on sys.term for the handler class name and parameter value types.

Concepts

Process: A named workflow with an optional input/output schema. The schema describes the data the process consumes and produces.
Process Step: One step within a process. Pins the handler that runs the step (a page or a batch job), the team and optional user the resulting task is assigned to, the due-day offset, the priority, and the initial task status. A step can be flagged createAtProcessStart (skip the trigger and instantiate immediately) or skipInProcessStep (an inert placeholder kept for ordering).
Task Handler Type: Whether the step’s task is handled by a UI page or by a batch job.

Entities

Process (`WFProcess`)

A named workflow.

Field Description

Field	Description
`code`	Business key (up to 16 characters).
`description`	Human-readable name.
`specSet`	Optional input/output `DomainSchema` for the process.

code

Business key (up to 16 characters).

description

Human-readable name.

specSet

Optional input/output DomainSchema for the process.

Process Step (`WFProcessStep`)

One step within a process.

Field Description

Field	Description
`wfProcess`	Owning process (composite business key with `code`).
`code`	Step code (up to 8 characters).
`description`	Human-readable name.
`createAtProcessStart`	Whether the step’s task is created immediately at process start. Default `false`.
`skipInProcessStep`	Whether the step is skipped during execution. Default `false`.
`daysTillDue`	Optional offset (days from creation) applied to the resulting task’s due date.
`taskHandlerType`	Whether the step is handled by a page or a batch job — see Task Handler Types below. Default `PA` (Page).
`taskHandler`	Optional fully-qualified Java class name of the handler.
`handlerParameter`	Optional parameter passed into the handler.
`mailMessageGroup`	Optional notification template group used when the step’s task is created.
`assignToTeam`	Default team the resulting task is assigned to.
`assignToUser`	Optional default user inside the team.
`exceptionTeam`	Optional team that picks up the task when it goes into an exception state.
`initialTaskStatus`	Optional initial status applied to the resulting task.
`initialPriority`	Initial priority applied to the resulting task. Default `M` (Medium).

wfProcess

Owning process (composite business key with code).

code

Step code (up to 8 characters).

description

Human-readable name.

createAtProcessStart

Whether the step’s task is created immediately at process start. Default false.

skipInProcessStep

Whether the step is skipped during execution. Default false.

daysTillDue

Optional offset (days from creation) applied to the resulting task’s due date.

taskHandlerType

Whether the step is handled by a page or a batch job — see Task Handler Types below. Default PA (Page).

taskHandler

Optional fully-qualified Java class name of the handler.

handlerParameter

Optional parameter passed into the handler.

mailMessageGroup

Optional notification template group used when the step’s task is created.

assignToTeam

Default team the resulting task is assigned to.

assignToUser

Optional default user inside the team.

exceptionTeam

Optional team that picks up the task when it goes into an exception state.

initialTaskStatus

Optional initial status applied to the resulting task.

initialPriority

Initial priority applied to the resulting task. Default M (Medium).

Task Handler Types (`WFTaskHandlerType`)

Code Name Meaning

Code	Name	Meaning
`PA`	Page	The step is handled by a UI page; a user opens the task and acts on it.
`BA`	Batch Job	The step is handled by a batch job; the resulting task is processed automatically.

PA

Page

The step is handled by a UI page; a user opens the task and acts on it.

BA

Batch Job

The step is handled by a batch job; the resulting task is processed automatically.

Functionality

Process-step lookup

WFL_PRC_QueryApi exposes two thin lookups: every step of a process (in their stored order) and a single step by (process, code). Other modules use these when resolving the next step to instantiate during process execution and when wiring task creation to a specific step’s handler/assignment defaults.

Public API

`WFL_PRC_QueryApi`

Read-side facade.

Method Description

Method	Description
`findAllStepsByWfProcess(WFProcess)`	Every step of the process.
`findStepByWfProcessAndCode(WFProcess, Code8)`	Step by (process, code), or `null`.

findAllStepsByWfProcess(WFProcess)

Every step of the process.

findStepByWfProcessAndCode(WFProcess, Code8)

Step by (process, code), or null.

`WFL_PRC_CommandApi`

This submodule does not provide a command API class. Processes and steps are maintained through the standard CRUD pages.

ViewModel actions

The submodule defines view models for WFProcess and WFProcessStep but does not declare any custom UI actions.