[Program Migration] Handle admin name collisions in program/question import about civiform HOT 6 CLOSED

@melanie-exygy this is what was settled on in the PRD (see comments here). It makes sense to me, since this is a manual process, I think it's less likely that an admin would be importing an identical program and more likely they would be importing a different program that happens to have the same admin name.

from civiform.

Yes, if an active status is not found for a give program, the code will throw an exception. If not importing the current status data, we should provide a way to create an empty status in the code.

// Create a new row in ApplicationStatuses table for the new program applicationStatusesRepository.createOrUpdateStatusDefinitions( adminName, new StatusDefinitions());

from civiform.

Couldn't we end up with a lot of duplicate programs? What about replacing the existing program if the name already exists?

from civiform.

I left a more detailed comment on the PRD. But I do see it being common that a program would be imported with the same name. Example

• Make program on Test environment
• Export -> Import to prod v1
• Make changes to program on Test
• Export -> import to prod making a v2

from civiform.

@rockycodes - Just letting you know we need to move the statuses data for that program from the ApplicationStatuses table too. So, if we are going with Option -1 (changing the admin name of the program, the admin name is the primary key in the statuses table. We should be changing it as well.)

from civiform.

@swatkat1 thank you for the reminder! I talked with Isabel/product a couple of weeks ago and the recommendation was to not migrate statuses for v1 of this work, but add that in for v2. Do you see any issues with ignoring statuses from a technical perspective?

from civiform.