From the component instructions:
Moving the refactored solution to Quality or Production
A few questions regarding this step:
Are these actions performed in Dev and then we use lifetime to deploy to Quality and Production as normal? Or does this mean we need to deploy to Quality and Production using .osp files we create in Dev?
What are the contents of solution 1? When it says <Target eSpaces> is that the <Source eSpace> and <Target eSpace> referred to earlier in the instructions?
For solution 2, does "complete solution" mean the <Source eSpace>, <Target eSpace>, plus the consumers of those eSpaces?
Hello Greg!
Do you have any update about this topic?I'm also trying to understand better this move step.
Hello @Francisco Menezes !
First of all, congratulations on this excellent solution.
Would you be able to help us with this question about the "move to production" step?
Thanks in advance.
Hello, let me try to help.
Please test the process with dummy modules first to make sure you are doing it right.
Steps in DEV:1. Copy Entity from Source to Target Module2. Apply Refactor Tool (add the server action to move Entity from Source to Target) and publish the refactor module. (at this point entity preview in SS will start showing your data in the target module, but not in runtime)3. Update all consumer references to use the entity of target module4. Remove entity from source module5. Create a solution with the target module and all its consumers and publish the "current running version" using "full compilations"6. Test application to check if data is showing up as expected7. Tag solution with a version nameDeploy to next environment
Step 1 - Put your application offline for users. Make sure your end-users can’t use your application during this process to avoid losing data.
Step 2 - Deploy the modules with the new entities
First deploy the modules with the new entities so the entities and respective physical tables are created in this environment.
Step 3 - Deploy the refactor tool
By deploying the refactor tool, the EntityMove code will be run, since the refactor tool has a Timer that runs “OnPublish”. Look at the platform logs to check for possible errors coming from the Refactor Tool. If no errors are detected, proceed.
(step 2 and 3 can be done together if you deploy a solution with the modules and refactor)
Step 4 - Deploy the solution version previously created/tagged in DEV
Deploy the solution version previously created and tagged in DEV and make sure to publish it using “with full compilations”
Step 5 - Test Application and make it Live
Test your application to make sure everything is working as expected and make it again available for end-users.