-
6.01-01 Create a Naming standard
New! The Planual can now be found on the Anaplan Support site. We will be transitioning it off Community in the coming months. 6.01-01 Create a Naming standard Be consistent with how you name your revisions. It is advised to use a Major.Minor nomenclature (e.g. R1.01, R1.02, R2 etc.). Remember, the description is permanent…
-
6.01-02 Create a Revision Tag at least once a day
During periods of intense development, ensure that revision tags are created regularly and tested against a "shell" model Best Practices article: Revision Tag Best Practices Questions on this topic? See 6.01-02 Create a Revision Tag at least once a day in our Planual forum.
-
6.01-03 Revision documentation
If you need a broader description of revisions, create a normal list (Non Production Data) and then house the revision details in a module with other fields such as Approved date User Story, Developer, Tested date, Sign off date etc. Best Practices article: Revision Tag Documentation Questions on this topic? See 6.01-03…
-
6.01-04 Synchronize Production regularly
Minimize the risk of sync errors by synchronizing regularly to keep Production and Development aligned Related to Rule: 6.01-02 Create a Revision Tag at least once a day Best Practice article: ALM Explained—Part 1: Compatibility Questions on this topic? See 6.01-04 Synchronize Production regularly in our Planual forum.
-
6.01-05 Dummy Test Model
Set up a "shell" model (using create from revision) that contains no production list members on which to test revisions and synchronises regularly Related to Rule: 6.01-02 Create a Revision Tag at least once a day Best Practice article: ALM Explained—Part 2: Testing Questions on this topic? See 6.01-05 Dummy Test Model in…