Workflow reference and operating checklist
26R1 reference · Documentation-based tutorial draft · Not executed in IFS
Task selection reference
Section titled “Task selection reference”| Need | Starting element or feature |
|---|---|
| Compute or normalize a small value | Script Task |
| Choose one branch | Exclusive Gateway |
| Expose extra entity-result variables | IFS Process Enrichment Task |
| Invoke supported IFS business operations | IFS API Task |
| Make an HTTP call | IFS REST Task |
| Request current-user input | User Task |
| End with a validation error | IFS Failure Event |
| Repeat a bounded set of activities | Sequential multi-instance subprocess |
| Invoke an enabled Industrial AI model | IFS AI Task |
An engine’s full BPMN feature set is not the IFS supported subset. Check the deployment and command validators before designing around timers, messages, external workers, or asynchronous transitions.
What must be validated separately
Section titled “What must be validated separately”- Diagram structure, mandatory fields, and one process definition key.
- Trigger type/timing compatibility.
- Command eligibility where the workflow is attached to a command.
- API contracts, entity identity, ETags, and writable fields.
- Error handling when Log Errors allows execution to continue.
- Runtime grants and post-deployment grant-review state.
- Transaction boundaries and externally persistent effects.
- Performance under realistic volume and concurrent triggers.
Operational review
Section titled “Operational review”Use Workflow Status and runtime/history views to watch duration, open tasks, and active instances. Use Asynchronous Workflow Executions for queued work, failures, and version review.
Relevant system-parameter areas include debug timeout, async concurrency/batching/delay, async-version behavior, REST blocked URLs, and AI invocation settings. Record current values and measure before tuning.
Cleanup schedules cover process history, observations, async audit data, troubleshooting data, and AI invocation history. Retention changes can remove evidence needed for support or audit; agree the retention requirement and inspect the installed schedules first.
Scheduling a cleanup task is not a general workflow scheduling feature. The documentation does not describe a built-in workflow scheduler for arbitrary recurring runs. A recurring business requirement needs a separately designed supported trigger.
Download the working materials
Section titled “Download the working materials”- Design worksheet
- Test matrix
- Original validation BPMN template
- Template walkthrough and verification limits
Coverage and verification
Section titled “Coverage and verification”This section covers the workflow lifecycle: suitability, registration, modeling, inputs, supported task patterns, security, testing, packaging, execution, and support. Examples use original fictional names.
The tutorials are documentation-based 26R1 drafts. The teaching BPMN is locally checked for XML structure and decision-script behavior, but it has not been imported, compiled, or executed in IFS. No screenshot of an IFS session is presented as execution evidence.
Outstanding verification includes the actual target release/tooling, import behavior, role grants, real API mappings, transaction outcomes, and specialist review. Industry-specific workflow recipes depend on installed components and are not claimed as covered by a generic example.
If two documentation pages disagree, the guide calls out the conflict rather than silently treating a draft as verified.