why were conditions on the dynamic attributes forbidden and mandatory removed?
#223
-
|
Ref. commit: https://github.com/OP-TED/eForms-SDK/blob/d27a7bfe31ee5ba930bc26fa7d428233f0c71d05/fields/fields.json As far as I can see, all condition constraints on all dynamic attributes (except |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
As indicated in the release notes for SDK 1.3.0, we have removed those constraints in order to make it initially easier to fill in notices for end users of applications like eNotices2 but also making them more responsible for providing coherent data. |
Beta Was this translation helpful? Give feedback.
As indicated in the release notes for SDK 1.3.0, we have removed those constraints in order to make it initially easier to fill in notices for end users of applications like eNotices2 but also making them more responsible for providing coherent data.
The rules will be added back in future SDKs, allowing users and systems to integrate them progressively and to improve data quality, while also improving the user experience of filling in the notices.