...

The dossier is stored in aggregate format, meaning the data can only be interpreted by loading the data (user-set attributes from the database) together with a consistent model. All information will be derived again when needed in the rule-engine. When you want to change the model, it is likely you'll want to change the data that goes with the change.

Make sure the data from the database can always be loaded into the profile. Attributes that can not be loaded are ignored, with the risk of data loss. Simply renaming an attribute means that any existing data in the database might be lost, since the attribute is not longer known in the model. Make sure to deal with this possible impact, possibly by actively migrating your data.

For example, when an attribute has been renamed. Any cases where the original value was stored need migration. There needs to be a model containing the old attribute and the newly created attribute. The old value should be set in the new attribute. Only after this migration the old attribute can be deleted from the model. Now the migration is complete.

For each situation, you have to determine what to do and if a migration is needed. For some changes (for example additions to the model), it might not be necessary to actively migrate cases.

Case Migration