- BizX Platform.
- If a company has both a test instance and a production instance, the instances are typically out of sync unless an instance refresh (from production to test) has been performed. When looking at the task of creating new items in production, many customers look to their test instance first as a place to create, do QA and then "move" the changes to production. While this may seem ideal, in many cases, this activity ends up being a busy exercise having nothing to do with the production instance.
- Here is some information regarding when to implement in the test instance first and when to implement in production directly thus bypassing the test instance:
FORMS (PM, 360)
- Implement the new form/changes directly into production. In order to see the form/changes, a form has to be launched. Since the form is created for a test user (for example, one of the alphabet people Alex Anderson, Brooke Brown, ...), the form will be transparent to the general population unless forms are launched to them too. The front end may look the same in test but the backend is typically different. This is because of the dependencies (competency ids, rating scale names ...) are typically different.
PLANS (GOAL, DEVELOPMENT)
- The results of implementation appear immediately. Initial implementation destination (test or production) is strictly optional based on comfort level with the changes and the system.
- The results of implementation appear immediately. As a result, some changes could be better implemented in the test instance first ... such as:
1. personal information such as date of birth.
2. company personal information such as salary.
3. organization personal information such as risk of loss and impact of loss.
- This is strictly optional based on comfort level with the changes and the system.
KBA , LOD-SF-PLT , Foundational Capabilities & Tools , How To