6.04-01 Back to the Future
This is a technique that reverts the model to a previous revision, allows you to make a fix, sync to Production, and then return Development back to where it was
Best Practice article:
Saving incomplete changes during development
Comments
-
Rule 6.04-01 Back to the Future. This is a technique that reverts the model back a revision state, allows you to make a fix, sync to Production, and then return Development back to where it was
Use Case: You are developing a functionality which is not yet complete and Production environment needs an urgent bug fix/hotfix
Here is how it was done in Pre Planual Era: We used to revert the Dev model to previous RT and then do the bug fix and push the changes to Prod
What is wrong with this method? You lose all the development that you had done since last revision was synced before bug was fixed.
Here is how it should be done in Planual Way:
- Add a new revision tag to the development model as a temporary placeholder. (Note the History ID of the last structural change as you'll need it later.)
- On the development model, use History to restore to a point where development and production were identical (before any changes were made in development).
- Apply the hotfix/bug fix
- Save a new revision of the development model.
- Sync the development model with the production model
- On the development model, use the History ID from Step 1 to restore to the version containing all of the development work (minus the hotfix).
- Reapply the hotfix to this version of development.
- Create a new revision of the development model
2
Title
- Preface
- PLANS
- Planual Conventions
- Zen of Anaplan
- Chapter 1 - Central Library
- Time
- Versions
- Users and Roles
- Contents
- Lists
- Subsets
- Line Item Subsets
- Emojis
- Chapter 2 - Engine
- Modules
- Formulas
- Line Items
- Saved Views
- Chapter 3 - UX Principles
- Hierarchy of Information
- Smart Grouping
- Reduce Visual Load
- Progressive Disclosure
- Use Consistency and Standards
- Provide Help and Guidance
- Use The Correct Data Type
- Give Users Visibility Into Status
- Match With Real World Scenarios
- Check In With End Uses Frequently
- Chapter 4 - UX Build
- Apps
- Dashboards
- Filters
- Chapter 5 - Integration
- Actions
- Processes
- Source Models
- Imports
- Exports
- Import Data Sources
- Data Hub
- Chapter 6 - Application Lifecycle Management
- Revision Tags
- Production Lists
- Architecture
- Deployed Mode
- Managing Changes During Development
- Chapter 7 - Extensions
- Excel
- PowerPoint