...

• When the titles for an additional field and a question are same, but the answer types are different, then that additional field is not migrated. A validation message with reference id for additional field is logged in the tomcat log. Data migration process for other additional fields continues
• When the string length of an additional field on the UI is greater than 50 characters, then the additional field is not migrated.
• Post migration, additional field responses are not editable.

Data migration for surveys and additional fields

Surveys can be are migrated by clicking on ‘Migrate Surveys’ link on the ‘migrate data’ page. ‘Migrate data’ ‘page can be reached by clicking the ‘Migrate data’ link on the admin page. Clicking on ‘migrate Surveys’ triggers the surveys migration.the surveys are migrated along with their timestamps. The user is navigated to the admin page once the migration is complete.Leila E deals with the migration of surveys and responses belonging to the client flow only.on upgrade to Leila E

Leila E deals with the migration of surveys and responses belong to all workflows

CAN

• Surveys and responses for client flow only are considered for all workflows migration as part of Leila E
• Validation messages during the migration process are logged in the tomcat log automatically.
• The existing survey definition and responses are not lost post migration.
• A new question group is created for each migrated survey for the same flow the survey belonged to.
• The survey title becomes the question group title
• The migrated survey questions are added under the 'Misc' section of the question group
• Post migration, the question groups are in the active state
• When the migrating survey and an existing question group have the same title and flow, then post migration, a duplicate QG is created with the same title as the existing QG.
• The order of the questions within the survey remains the same post migration.
• Question within a survey retains its mandatory/non-mandatory status after migration in the corresponding flow

...

• ‘Date of survey, surveyed by, entered into the system by’ fields and their corresponding responses are not visible on the UI after migration
• When the server is restarted, all the responses get migrated all over again if the earlier migration failed.
• When the string length of a survey title on the UI is greater than 50 characters, then the additional field is not migrated.
• The existing survey definitions and responses are not lost post migration
• The survey responses are not editable post migration.

If successful

• NO additional fields should be listed under "View Additional Fields" in Admin
• No more data exist in old Additional Fields tables in the DB
• In the workflows where these additional fields existed, these additional fields shouldn't be displayed as Additional Fields - should now be under Question Groups
• There should be no validation for mandatory additional fields - the validation should only be for QG's

If NOT successful

• The additional fields that did not migrate should be listed under "View Additional Fields" in Admin
• The additional fields that did not migrate and all data saved with them should still be in the DB
• In the workflows where these additional fields existed, these additional fields shouldn't be displayed as Additional Fields - the MFI must re-create them manually under Question Groups
• There should be no validation for mandatory additional fields - the validation should only be for QG's