ChrisDibble | 2018-12-13 18:39:46 UTC | #1
Summary: We are adding an additional restriction to input contracts for data actions. Input properties will only be allowed to contain alphabetic (a..z,A..Z), numeric (0..9), hyphen (“-“), and underscore (“_”) characters. Property names must start with an alphabetic character. We are making this change because variables that do not follow this convention are incompatible with action templates.
Impact: Any custom data actions with input contracts using property names containing restricted characters will need to be cloned and modified to use a different name. Actions that continue to use property names containing restricted characters will fail due to failing input validation.
Date of Change: On or after February 11, 2019
Let us know if you have any questions or concerns about this change.
Ana_Laia | 2018-12-14 14:58:08 UTC | #2
Hi Chris,
So, just to be ensure that this won't have impact on our Bridge Data Actions, we won't have any problem if on Request Schema we use something like:
"properties": { "nameProperty": { "type": "string", "title": "Name", "description": "A property example" }
Thank you in advance
Best regards, Ana Laia
ChrisDibble | 2018-12-14 15:19:17 UTC | #3
Hi Ana,
Correct, the schema you posted would still be valid and continue to function as you expect.
Here is a list of examples that will be invalid after the change:
- "name with space"
- "name.with.periods"
- "3startsWithNumber"
- "speci@lCharacter$"
-Chris
system | 2019-01-14 15:19:18 UTC | #4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 4185