The policy will not beĮnforced even if it remains attached to a flow. Set to true to have flow execution continue even after a policy Set to false to return an error when a policy fails. The management UI proxy editor with a different, natural-language name. Optionally, use the element to label the policy in The value of the name attribute canĬontain letters, numbers, spaces, hyphens, underscores, and periods. The following table describes attributes that are common to all policy parent elements: Attribute EdgeĪutomatically uses the content of this variable as the message for next processing step.įollowing are elements and attributes you can configure on this policy. JSON-formatted message that is populated in the response OutputVariable.

JSON-takes an XML-formatted response message as the source, and then creates a This configuration-which is the minimal configuration required to convert XML to See Flow variables and conditionsįor a detailed discussion on converting between JSON and XML, see. XML, the response format can be dynamically set by configuring JSON to XML and XML to JSON By combining policies this way,Ī JSON API can be exposed for backend services that natively support only XML.įor scenarios where APIs are consumed by diverse client apps that may require either JSON or Paired with an XML to JSON policy on the outbound response flow. In a typical mediation scenario, a JSON to XML policy on the inbound request flow is often Response, the policy would be attached to a response Flow (for example, Response / ProxyEndpoint

Object Notation (JSON), giving you several options for controlling how messages areĪssuming that the intent is to convert an XML-formatted response into a JSON-formatted

This policy converts messages from the extensible markup language (XML) format to JavaScript You're viewing Apigee Edge documentation.

Xml to json convert