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 and cannot be changed - Be careful! Questions on this topic? See 6.01-01 Create a Naming standard in our Planual forum.
6.02-01 Define Production lists before the first sync
Don't set all lists to production initially. Setting a list back to Structural (after a synchronize) will remove data from the existing production list even if the members are the exact same Best Practices articles: Prepare Applications for ALM ALM Explained—Part 3: Avoiding Data Loss Questions on this topic? See 6.02-01…
6.03-01 Don't take the model out of deployed mode
Once ALM has been initiated, and Deployed mode is turned on, the Production model should NEVER be taken out of Deployed mode Exceptions: 6.03-01a Development Model creation - When copying a Production model to create the initial ALM environment, or when re-creating the DEV model as part of a “reset” 6.03-01b There are no…
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 Questions on this topic? See 6.04-01 Back to the Future in our Planual forum.
6.05-01 Make DEV the source for everything
DEV> Test, and DEV>Prod is more flexible; it allows multiple Test models, and Test models to be created and deleted without compromising Prod. It also supports segregation of duties Best Practice articles: ALM Explained—Part 1: Compatibility ALM Explained—Part 2: Testing Questions on this topic? See 6.05-01 Make DEV the…
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.02-02 Formula protection - Hard coding
You cannot hard code a reference to an item in a production list because that member may be deleted by an end user Best Practices article: Formula Protection Questions on this topic? See 6.02-02 Formula protection - Hard coding in our Planual forum.
6.03-02 Use deployed in Dev mode for additional security
Setting deployed mode for Dev models is OK and can prevent inadvertent structural changes being made outside of normal development cycles Questions on this topic? See 6.03-02 Use deployed in Dev mode for additional security in our Planual forum.
After a revision, create multiple revision tags with different switchover dates prior to starting new development Best Practice article: Managing Frequent Structural Changes During Development Questions on this topic? See 6.04-02 Switchover in our Planual forum.
6.05-02 Archived Models
Compatible models (DEV, TEST or PROD) can be archived without breaking the link between them Related to Rule: 6.05-03 Model modes Best Practice article: ALM Explained—Part 2: Testing Questions on this topic? See 6.05-02 Archived Models in our Planual forum.