Find and configure the workflow trigger
26R1 reference · Documentation-based tutorial draft · Not executed in IFS
Discover what actually runs
Section titled “Discover what actually runs”A page title is not an API name. In a development environment, enable the available IFS Cloud Web debug tools, reproduce one operation, and inspect its request. API Explorer supplies the metadata for the projection, entity set, keys, attributes, and call signature.
Record this mapping before opening the configuration wizard:
| Item | Example teaching value |
|---|---|
| User action | Save one handover |
| API | The projection actually observed |
| Operation | UPDATE, not simply “Save” |
| Entity set or call | Exact metadata name |
| Input field | Captured external reference attribute |
| Workflow type and timing | Validation / Before |
| Intended scope | One business operation and one test record |
Read operations can be frequent. A broad READ trigger can run while pages load or refresh, so measure how often the actual endpoint is invoked.
Configure a projection reaction
Section titled “Configure a projection reaction”- Deploy the intended workflow version.
- Open its Projection Action Information and add a projection action.
- Select the API. Choose DATA for entity CRUD or CALL for a function/action.
- Select the exact entity set and CRUD operation, or exact call signature.
- Choose the supported workflow type and timing.
- Enable the projection action and finish.
- Reproduce the originating request and capture the execution.
The APIs you can call from a task and the APIs available as reaction triggers are not identical. The tooling documentation excludes StandardEntity Entity Service APIs from projection reactions, even though an activated Entity Service API can be available inside an IFS API Task.
Configure an event reaction
Section titled “Configure an event reaction”Create or identify the custom event, then an Event Action of type Workflow. Set the workflow ID to the process key, select the type and permitted timing, and complete the event/action publication and enablement steps.
Use After for synchronous validation/enrichment or Asynchronous for enrichment. Before timing is for projection reactions.
Event inputs normally contain NEW values. Ticking an event’s Old Value option alone does not pass those values to the workflow. The documented workaround is an explicit event custom attribute mapping such as &OLD:ATTRIBUTE_NAME; verify its captured name and value in your event.
For a database/background-job change, the documented route is an asynchronous Workflow event action. Synchronous After processing does not provide the same trigger path there.
Commands and duplicate triggers
Section titled “Commands and duplicate triggers”A command captures the user’s explicit intention to run a workflow. Follow command eligibility and form design and configure it through Page Designer.
One user action may invoke several APIs and events. If both a projection and event reaction target the same outcome, the workflow can run more than once. Record the complete execution trace before adding duplicate-prevention logic.
Checkpoint: disable only your new trigger in development and confirm that the originating operation still behaves as expected. This isolates the workflow’s contribution without altering unrelated configurations.