Workflows and automation FAQ — page 2
All FAQ topics / Workflows and automation
156 questions · page 2 of 4
Is it possible to reliably capture the response of an outbound REST call made from a Custom Event Action (like a REST Call action type), including logging failures into a custom table, without relying on manually querying Application Messages?
A workflow that used to deploy fine now fails validation with errors about a missing `ifsBpaEnrichmentRegisteredVariables` list and a missing `ifsBpaProjectionETagVariableName`, after a task was changed from one type to another.
A BPA Failure End Event's message property is set to a variable (like `${errorMessage}`) populated by an earlier script task, but the variable never actually gets substituted into the message shown to the user.
Trying to set a default value via BPA/Process Enrichment for a standard (non-custom) field — including one backed by a fixed database enumeration — either fails outright or throws a serialization error when the field is explicitly registered as a Process Enrichment variable.
Is there a way to feed a workflow action a whole result set assembled by a query (the workflow equivalent of looping over a PL/SQL cursor), rather than only being able to read one record via a standard API Read task?
A workflow needs data from an external website that returns rendered HTML rather than structured JSON or XML — is there a way to get usable data out of that into IFS?
A BPA workflow triggered by Process Enrichment successfully updates a field's value in the database (confirmed via inspection and by re-querying the record), but the currently open page doesn't show the updated value until some unrelated action is taken.
A Custom Event needs to trigger off a read-only field (like "Active Work Assignments") that's computed and displayed on a page, but that field isn't stored in the entity's main underlying table, so a normal insert/update trigger on that table never fires when the computed value effectively changes.
Is it possible to customize Assistant page behavior (like dynamically setting a field's default value) using only configuration — Workflow/BPA and Custom Events — without a full Developer Studio customization?
A workflow sends an email correctly before a successful completion end event, but the equivalent email set up before an unsuccessful/failure end event never actually gets sent.
A BPA REST call fails with "HTTP Connection Delegate could not retrieve the data from the specified URL, Returned status code: 500," even though calling the exact same URL from a tool like Postman on the same machine works fine.
Is it possible to have shipment attachments print automatically whenever the shipment's operational delivery-note form is printed, via a workflow or Report Rule?
Calling `.includes()` on a string variable inside a workflow script task fails, even though the variable is confirmed to genuinely be a string.
A Process Enrichment workflow needs to behave differently depending on how a related record was created (for example, whether a Standard Operation was added by Copy versus by Reference), since one path has a reliable back-reference to use and the other doesn't.
A Custom Event set to trigger on new-object creation is meant to update a field on that same newly-created record, but the update ends up applying to the previous record instead.
Why do some modern JavaScript features (like `findIndex()`, `let`, and `const`) fail or behave unexpectedly inside a workflow script task, while older equivalents like `indexOf()` and `var` work fine?
Using the 24R2 "IFS REST Task Configurations" feature to externalize a REST call's Basic Authorization user/password out of a workflow's inline script doesn't work, since the inline script can't directly reference the individual user/password values stored there.
A workflow API task that creates a nested entity record (like a customer order line discount) fails with a conflicting-discount-type error, even though only one discount type (amount or percentage) is actually being set in the call.
A workflow calling a projection action (like releasing a Customer Order through `ProcessOrders`) fails with an "Arguments used to execute current operation are not allowed" error, even though the arguments being passed look correct when debugged.
Building a JSON payload in a workflow script task using Camunda's `org.camunda.spin.Spin.JSON` and its `.prop()` method works fine when stepping through in Debug mode, but throws an unexpected server error at actual runtime.
A workflow task meant to call a standard IFS Projection doesn't show "IFS Projection" as an option in its task-type menu while designing the workflow.
A workflow's IFS REST Call task shows only a generic top-level error (like a bare 500) instead of the more specific embedded error detail (like a "[422] Unprocessable Entity" message body) that the same call returns when tested directly in Postman.
An Event Action needs to trigger when a computed custom attribute's value is either a specific string or NULL, but a single condition expression combining both cases with NULL doesn't behave reliably.
External REST API endpoints called from workflows differ per environment (CFG/UAT/PRD each have their own base URL) — is there a way to avoid manually reconfiguring the workflow's hardcoded URL every time it's promoted to the next environment?
A workflow gateway condition checking that a value "is not null" doesn't behave as expected, letting execution through (or blocking it) inconsistently.
A workflow deployed as Process Enrichment fails with a compatibility error when it includes an IFS Failure Event meant to show an error message to the user, even though the same workflow deploys fine as a Validation type.
A workflow script task copy-pasted from an example (or another source) throws an unexplained syntax/execution error, even though the code looks correct on inspection.
Is there a way to trigger custom PL/SQL logic (not just a standard email) when a specific background job finishes, like a scheduled "Create Pick List for Customer Order" job?
Can a workflow send email directly through a generic mail-send connector/service task (like Camunda's built-in one), the way it might work in a plain Camunda deployment?
Can a workflow perform the same Work Order pre-posting update that's currently done manually through an Assistant, since there doesn't seem to be a matching direct API entity set for it?
A custom attribute that's published and visible on a page (and present in the projection's API documentation) still isn't recognized or selectable when referenced from a BPA workflow.
A BPA-driven update to a value shown in an Assistant/virtual-set page succeeds in the database, but the open Assistant window doesn't reflect the new value.
A workflow API task creating a new record (like a Maintenance Purchase Requisition line) fails with "Failed to create the entity as it would be unreachable from the current path," even though the payload looks correct.
A Custom Event fires immediately after a record is created (in the same transaction) and needs to act on that just-created record, but the event's own logic can't seem to see or find the record it was just triggered by.
Undeploying a Workflow to make changes requires first deleting the Commandgroup item that invokes it in Page Designer, and re-adding that command every time the workflow is redeployed — is there a way to just "disable" the command instead so it doesn't need to be recreated each time?
Can a Custom Event's "before object is changed" trigger be used to modify an incoming key field's value (like stripping characters out of a Lot/Batch Number) before it's saved?
A workflow API task tries to populate a CLOB/long-text attribute (like a RecordSelection-style field on an Engineering Revision Transfer record) but the value never actually gets set, no matter how it's formatted or escaped, and the rest of the process silently fails as a result.
A workflow user-task form built to show a popup/informative window fails to deploy or behave correctly, tracing back to one specific form field.
A BPA workflow using a Projection Delegate to read an unfiltered entity set (expecting to retrieve every record, like all customers) doesn't return the full result, failing during inspection.
No questions match. Try a broader term or reset the filters.