/
_JSONEscapingRequirements

_JSONEscapingRequirements

 

 

JSON escaping requirements

If a parameter within the JSON formatted parameters template is a JSON structure in itself (e.g. the Lambda function payload), it needs to be escaped before adding it as a value - this has two implications:

  • custom content needs to be escaped, which can be achieved by Composing action payloads with utility functions, specifically the $util.escapeJson() function

  •  variables with conflicting content (e.g. multi line variables like JIRA's $issue.fields.description or Bamboo's $notification.textEmailContent or JSON structures retrieved via JSONPath) need to be escaped twice, via $util.escapeJson($util.escapeJson(...)) - we are exploring options on how to make this easier in a future release

Related content

_JSONEscapingRequirements
_JSONEscapingRequirements
More like this
_JSONEscapingRequirements
_JSONEscapingRequirements
More like this
Invoke Lambda Function
Invoke Lambda Function
More like this
Automation with AWS 1.2 Release Notes
Automation with AWS 1.2 Release Notes
More like this
Send SQS Message - structured JSON payload
Send SQS Message - structured JSON payload
More like this
Composing action payloads with utility functions
Composing action payloads with utility functions
More like this
Atlassian®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2024 Utoolity GmbH. All rights reserved.