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.

All FAQ questions / Workflows and automation

Answer

Rather than trying to reference the separate user and password fields from script, consider pre-building the complete Basic-Auth header value itself (the already-encoded "AuthHeader" string) and storing that single combined value in IFS REST Task Configurations, then referencing that one pre-built value directly from the workflow — this sidesteps needing the inline script to assemble the header from two separate externalized values.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Workflows and automation questions