Allow dots in JSON property names when using REST Delivery Endpoints
When configuring a Noification with a REST Delivery Endpoint, there is no way to escape a dot (".") so it doesn't gets interpreted as a path delimiter. There are cases when the dot must be part of the property name. One way to solve it would be to allow escaping it with a backslash or even better (IMHO) to use the JSONPath way to solve this: being able to specify arbitrary property names putting them between brackets and single quotes: ['prop.erty'].
Gonzalo Merciel commented
Another way to overcome this limitation would be an option to construct the raw request body in a similar way we can construct an email body. This would also allow to use other content types (like XML) and the use of dynamic property names (linked to attribute values).