Difference between revisions of "Keeping the Test and Live Environments in Sync"
Jump to navigation
Jump to search
Max.Stroud (talk | contribs) |
|||
Line 1: | Line 1: | ||
− | + | Any changes to these items in live after a copy of live has been made and put into your test environment need to be tracked or duplicated in test. As the configuration of the new V11 system is completed there are attributes assigned to these items (ex. menus, picklists, clinical desktop views and other views are assigned to users). If the chanages to these items are not tracked or dulplicated, the attributes will not be assigned and will be missing after go-live. Our reccomendation is that when you change any of the following items in your live environment that you do the same in your test environment. This prevents having additional information to load and configure on Go-Live weekend. | |
*Any New Users | *Any New Users |
Revision as of 13:24, 17 September 2008
Any changes to these items in live after a copy of live has been made and put into your test environment need to be tracked or duplicated in test. As the configuration of the new V11 system is completed there are attributes assigned to these items (ex. menus, picklists, clinical desktop views and other views are assigned to users). If the chanages to these items are not tracked or dulplicated, the attributes will not be assigned and will be missing after go-live. Our reccomendation is that when you change any of the following items in your live environment that you do the same in your test environment. This prevents having additional information to load and configure on Go-Live weekend.
- Any New Users
- Any changes to System or TWAdmin Preferences in V10
- Any changes to the OID
- Any Changes to the RID