[APIM] Policy expression support in policies - 5

Author: dlepow

articles/api-management/set-body-policy.md

@@ -33,7 +33,7 @@ Use the `set-body` policy to set the message body for incoming and outgoing requ
 | Attribute         | Description                                            | Required | Default |
 | ----------------- | ------------------------------------------------------ | -------- | ------- |
 |template|Used to change the templating mode that the `set-body` policy will run in. Currently the only supported value is:<br /><br />- `liquid` - the `set-body` policy will use the liquid templating engine |No| N/A|
-|xsi-nil| Used to control how elements marked with `xsi:nil="true"` are represented in XML payloads. Set to one of the following values:<br /><br />- `blank` - `nil` is represented with an empty string.<br />- `null` - `nil` is represented with a null value.|No | `blank` |
+|xsi-nil| Used to control how elements marked with `xsi:nil="true"` are represented in XML payloads. Set to one of the following values:<br /><br />- `blank` - `nil` is represented with an empty string.<br />- `null` - `nil` is represented with a null value.<br/></br>Policy expressions aren't allowed. |No | `blank` |
 
 For accessing information about the request and response, the Liquid template can bind to a context object with the following properties: <br />
 <pre>context.

articles/api-management/set-header-policy.md

@@ -30,15 +30,15 @@ The `set-header` policy assigns a value to an existing HTTP response and/or requ
 
 |Name|Description|Required|Default|
 |----------|-----------------|--------------|-------------|
-|exists-action|Specifies  action to take when the header is already specified. This attribute must have one of the following values.<br /><br /> -   `override` - replaces the value of the existing header.<br />-   `skip` - does not replace the existing header value.<br />-   `append` - appends the value to the existing header value.<br />-   `delete` - removes the header from the request.<br /><br /> When set to `override`, enlisting multiple entries with the same name results in the header being set according to all entries (which will be listed multiple times); only listed values will be set in the result.|No|`override`|
-|name|Specifies name of the header to be set.|Yes|N/A|
+|exists-action|Specifies  action to take when the header is already specified. This attribute must have one of the following values.<br /><br /> -   `override` - replaces the value of the existing header.<br />-   `skip` - does not replace the existing header value.<br />-   `append` - appends the value to the existing header value.<br />-   `delete` - removes the header from the request.<br /><br /> When set to `override`, enlisting multiple entries with the same name results in the header being set according to all entries (which will be listed multiple times); only listed values will be set in the result. <br/><br/>Policy expressions are allowed.|No|`override`|
+|name|Specifies name of the header to be set. Policy expressions are allowed.|Yes|N/A|
 
 
 ## Elements
 
 |Name|Description|Required|
 |----------|-----------------|--------------|
-|value|Specifies the value of the header to be set. For multiple headers with the same name, add additional `value` elements.|No|
+|value|Specifies the value of the header to be set. Policy expressions are allowed. For multiple headers with the same name, add additional `value` elements.|No|
 
 ## Usage
 

articles/api-management/set-method-policy.md

@@ -23,7 +23,7 @@ The `set-method` policy allows you to change the HTTP request method for a reque
 <set-method>HTTP method</set-method>
 ```
 
-The value of the element specifies the HTTP method, such as `POST`, `GET`, and so on.
+The value of the element specifies the HTTP method, such as `POST`, `GET`, and so on. Policy expressions are allowed.
 
 ## Usage
 

articles/api-management/set-query-parameter-policy.md

@@ -29,14 +29,14 @@ The `set-query-parameter` policy adds, replaces value of, or deletes request que
 
 |Name|Description|Required|Default|
 |----------|-----------------|--------------|-------------|
-|exists-action|Specifies what action to take when the query parameter is already specified. This attribute must have one of the following values.<br /><br /> -   `override` - replaces the value of the existing parameter.<br />-   `skip` - does not replace the existing query parameter value.<br />-   `append` - appends the value to the existing query parameter value.<br />-   `delete` - removes the query parameter from the request.<br /><br /> When set to `override` enlisting multiple entries with the same name results in the query parameter being set according to all entries (which will be listed multiple times); only listed values will be set in the result.|No|`override`|
-|name|Specifies name of the query parameter to be set.|Yes|N/A|
+|exists-action|Specifies what action to take when the query parameter is already specified. This attribute must have one of the following values.<br /><br /> -   `override` - replaces the value of the existing parameter.<br />-   `skip` - does not replace the existing query parameter value.<br />-   `append` - appends the value to the existing query parameter value.<br />-   `delete` - removes the query parameter from the request.<br /><br /> When set to `override` enlisting multiple entries with the same name results in the query parameter being set according to all entries (which will be listed multiple times); only listed values will be set in the result.<br/><br/>Policy expressions are allowed. |No|`override`|
+|name|Specifies name of the query parameter to be set. Policy expressions are allowed. |Yes|N/A|
 
 ## Elements
 
 |Name|Description|Required|
 |----------|-----------------|--------------|
-|value|Specifies the value of the query parameter to be set. For multiple query parameters with the same name, add additional `value` elements.|Yes|
+|value|Specifies the value of the query parameter to be set. For multiple query parameters with the same name, add additional `value` elements. Policy expressions are allowed. |Yes|
 
 ## Usage
 

articles/api-management/set-status-policy.md

@@ -28,8 +28,8 @@ The `set-status` policy sets the HTTP status code to the specified value.
 
 | Attribute       | Description                                                | Required | Default |
 | --------------- | ---------------------------------------------------------- | -------- | ------- |
-| code  | Integer. The HTTP status code to return.                            | Yes      | N/A     |
-| reason | String. A description of the reason for returning the status code. | Yes      | N/A     |
+| code  | Integer. The HTTP status code to return. Policy expressions are allowed.                            | Yes      | N/A     |
+| reason | String. A description of the reason for returning the status code. Policy expressions are allowed. | Yes      | N/A     |
 
 
 ## Usage

articles/api-management/set-variable-policy.md

@@ -26,8 +26,8 @@ The `set-variable` policy declares a [context](api-management-policy-expressions
 
 | Attribute | Description                                                              | Required |
 | --------- | ------------------------------------------------------------------------ | -------- |
-| name      | The name of the variable.                                                | Yes      |
-| value     | The value of the variable. This can be an expression or a literal value. | Yes      |
+| name      | The name of the variable.  Policy expressions aren't allowed.                                               | Yes      |
+| value     | The value of the variable. This can be an expression or a literal value. Policy expressions are allowed.  | Yes      |
 
 ## Usage
 

articles/api-management/trace-policy.md

@@ -35,14 +35,14 @@ The `trace` policy adds a custom trace into the request tracing output in the te
 
 | Attribute | Description                                                                                                               | Required | Default |
 | --------- | ------------------------------------------------------------------------------------------------------------------------- | -------- | ------- |
-| source    | String literal meaningful to the trace viewer and specifying the source of the message.                                   | Yes      | N/A     |
-| severity  | Specifies the severity level of the trace. Allowed values are `verbose`, `information`, `error` (from lowest to highest). | No       | `verbose` |
+| source    | String literal meaningful to the trace viewer and specifying the source of the message. Policy expressions aren't allowed.                                   | Yes      | N/A     |
+| severity  | Specifies the severity level of the trace. Allowed values are `verbose`, `information`, `error` (from lowest to highest). Policy expressions aren't allowed. | No       | `verbose` |
 
 ## Elements
 
 |Name|Description|Required|
 |----------|-----------------|--------------|
-| message  | A string or expression to be logged.                                                                                                                 | Yes      |
+| message  | A string or expression to be logged. Policy expressions are allowed.                                                                                                                 | Yes      |
 | metadata | Adds a custom property to the Application Insights [Trace](../azure-monitor/app/data-model-complete.md#trace) telemetry. | No       |
 
 ### metadata attributes