Hi, We have an application in production with active instances.

The majority of changes caused by the CDT change can be dealt with by using impact analysis; this will update the various references tot hta CDT to be the latest version, so datastore writes etc will work correctly.

As far as SAIL is concerned, you should update the SAIL form in such a way that any reference to the new field is checked for null before displaying or editing; simply adding a new field to the CDT won't break the tasks using the old SAIL form, but any reference to that field which requires a value could cause issues. That said, it very much depends on how you're using the new field in the form.

The majority of changes caused by the CDT change can be dealt with by using impact analysis; this will update the various references tot hta CDT to be the latest version, so datastore writes etc will work correctly.

As far as SAIL is concerned, you should update the SAIL form in such a way that any reference to the new field is checked for null before displaying or editing; simply adding a new field to the CDT won't break the tasks using the old SAIL form, but any reference to that field which requires a value could cause issues. That said, it very much depends on how you're using the new field in the form.