Configuration of Data Fields
(Person Data, Global Data, One-To-Many, Global Data Table, Lookup)
Disabling Changes on Production Environment
All data field configurations are restricted to solely be made on staging, and will automatically be immediately published to production. This change improves the experienced performance of the UI, and decreases the number of configuration and publish issues experienced on production.
Disabling Publish of Global Data Values
The option to publish Global Data values from staging to production is exchanged with the possibility to specify values for staging and production directly in the staging environment, see screen-snippet below. Subsequently, values are restricted to be altered through the UI directly on production. However, changes through side effects or APIs on production are still fully supported. The respective value changes performed on staging to production are published right away to production.
Global Data Naming Rules
Global Data field names are limited from having dots (".") in their names. Dots have already been forbidden in the UI, but this changes now also affect API requests.
Values in Stored Copies on Staging
Due to changes above, stored copies on staging for executions that happened before the upgrade to version 23.1 will show no values for connected data fields.
Can this article be improved? Please let us know, and we will update the article
Please sign in to leave a comment.