Summary

Users would like the ability to configure parameterized (SpEL-based) payload contents for the embedded artifact used in the Lambda Invoke stage directly from the UI, without needing to edit the stage JSON.

Current Behavior

Today, when a Lambda Invoke stage needs to send a payload generated from pipeline parameters, users must manually modify the stage JSON to embed something like:

"payloadArtifact": {

"account": "embedded-artifact",

"artifact": {

"artifactAccount": "embedded-artifact",

"id": "685c650f-b852-4ec6-ab49-98926961f216",

"reference": "${#toBase64('{\"first_name\": \"' + parameters.name + '\", \"last_name\": \"' + parameters.functionName + '\"}')}",

"type": "embedded/base64"

}

}

Even using an Evaluate Variables stage doesn’t avoid the need to edit JSON, since the user still has to manually wire the artifact reference inside the stage config.

Requested Enhancement

Add a UI-level capability to:

Create or edit an embedded artifact payload directly in a text/JSON editor field within the Lambda Invoke stage.

Allow users to include SpEL expressions and pipeline parameters in that payload (e.g., ${parameters.name} or #toBase64(...)).

Automatically handle encoding (base64 or otherwise) and artifact creation behind the scenes, without requiring users to interact with the raw stage JSON.

Value / Rationale

Eliminates the need for advanced JSON editing, reducing user friction and error rates.

Makes parameterized Lambda payloads more accessible to non-expert users.

Aligns with the UI-driven configuration approach used in other stages.

Customer Quote

“Expectation is to be able to configure parameterized contents directly from the UI, instead of editing the stage JSON.”