Workflows and automation FAQ
Explore questions about workflow triggers, variables, validation, and automated actions. Connect a specific symptom to the workflow lifecycle, then use the related guides to plan and review a complete flow.
Related learning:
Release note: These answers include IFS Cloud and older IFS Applications topics. Confirm the product and release mentioned in each answer. They are written explanations, not procedures verified in an IFS environment.
Go deeper with focused guides
Section titled “Go deeper with focused guides”Explore other FAQ topics (23)
156 questions · page 1 of 4
How should error handling actually work inside a workflow?
How do we get the identity of the currently logged-in user inside a workflow?
An API Task's operation returns a structured or nested result instead of a flat record — how do we work with that?
A workflow query hits a result-set size limit when inspecting or debugging it.
A workflow trigger doesn't fire when the record was created by a background job instead of a user action.
A workflow doesn't trigger at all, but only for one specific user.
How do we send an email with a large attachment from a workflow?
Can a workflow refresh the client page automatically after it completes?
Can a workflow show the user an informative pop-up message mid-process?
Can one workflow call or trigger another, and how deep can that chain safely go?
In a workflow's EntitySet Name field, what's the difference between a plain entity set name and one prefixed with "Reference_"?
A workflow shows as "locked by another user" and can't be undeployed to deploy a new version — how is it unlocked?
Can a multi-choice (multi-select) custom enumeration attribute be populated from a workflow?
A "Send Email" toggle that used to default correctly for a document (like a PO) now has to be manually turned on every time, and it's not available as a Report Rule action.
Is there a way to start a workflow (BPA process) directly from a REST API call rather than only from an in-application trigger?
A BPA workflow's REST Call task fails specifically for larger payloads, apparently hitting some kind of character/size limitation.
Can a workflow generate a stream/notification message (the kind shown in the application's notification area), not just an email?
A User Interaction workflow throws a client error reading "cannot read properties of null (reading 'response')" when continuing the workflow after user input.
Passing a timestamp value (like the current date/time from a script task) into an IFS API call from a workflow fails with a data-type conversion error.
A Business Process Automation flow can't pre-fill a value into a field that isn't updatable in the underlying entity.
A BPA workflow needs to either add a new value to a field or replace an existing one, depending on what's already there.
A workflow's API task for updating a record sends a field value to the wrong place, causing the update to fail or silently do nothing.
A page needs to react to a record's status changing, but the status field isn't shown anywhere in that page's layout.
A scheduled Quick Report needs to run against a rolling period (like "the current fiscal period") without a person re-entering the parameter each time.
Is a Message Box style confirmation achievable from a page command, or does it require a full Workflow?
Inspecting/debugging a large Business Process Automation workflow fails with a message about taking too long and needing less data.
A workflow's API task creates a record successfully (confirmed working the same call via Postman), but running the workflow itself doesn't seem to produce any visible effect, without an error.
Passing a date or datetime value to a workflow's API task keeps failing, even after reformatting it in a script task first.
A workflow API task calling an action discovered from the browser's network log fails with a "does not have the expected parameters" error, even though the same parameters worked in the direct UI call.
A workflow's API task works when a numeric parameter is hardcoded but fails with an Integer-to-BigDecimal cast error once the same value is passed in through a workflow variable.
A BPA validation observation that used to correctly block saving a record stops being enforced by the user interface after the underlying validation script is extended to check an additional custom field.
Sending a large report (like a Quick Report's full results) as an email attachment from a workflow hits a size limit, since the straightforward mail-sending function's parameter is too small to hold it and the large-object-capable overload isn't usable directly from a custom projection action.
A BPA workflow fails to correctly use the value of a custom attribute that is itself a reference (LOV-backed) field, while other persistent custom fields on the same entity work fine as workflow parameters.
A workflow tied to a database-insert event on a table (like invoices) triggers correctly for records created interactively online but seems not to trigger for functionally-equivalent records created by a background job (like an intercompany invoice generated by a connectivity outbox job).
A workflow scheduled to run Asynchronously doesn't seem to execute at all (it doesn't show among currently running workflows), while the identical workflow scheduled as "After" runs fine.
A BPA Process Enrichment script setting a custom Date/Time attribute's default value (using a plain JavaScript `Date` or its ISO string) fails, even though setting a text or user-identity default value in the same flow works fine.
A BPA Process Enrichment flow setting a value (like a Price Freeze flag) via Default timing on a customer order line works from a data standpoint, but then the page stops treating the record as genuinely new — for example, blocking entry of a part number.
A workflow needs to show a confirmation message via a User Task when it succeeds, but also needs to show a distinct error message when a Failure/Termination End Event is reached — and combining both in the same workflow isn't accepted.
A workflow calling a custom API always shows the user a generic success message, even when the custom API actually returned a specific error — the real error is only visible by inspecting the workflow's own execution trace.
No questions match. Try a broader term or reset the filters.