Rapid prototyping can be useful in defining user requirements and determining what inputs are needed to drive the outputs. You can create new functions and applications, collect user feedback, and make changes quickly and easily. Then — when the prototype is developed and tested — you can focus on building the business logic to drive the business process. During rapid prototyping projects, make sure there is constant communication in daily standup meetings among developers, administrators, and process owners. This ensures that development progresses smoothly and the final product meets users’ needs.
![]() | Best Practice #4: Use different color schemes for each instance. |
Using different color schemes for each instance makes it obvious which instance users are working in and prevents accidental changes to the wrong environment. ServiceNow Product Documentation explains how to customize the user interface appearance and provides a link to cascading style sheet — or CSS — color names.
![]() | Best Practice #5: Document your procedure for migrating data. |
Because the people who migrate changes from development to test to production may not be the same people who implemented the changes, it is important to document your procedure for migrating data. To ensure that the migration goes smoothly, identify which update sets need to be retrieved, verified, previewed, and committed, and their order.
![]() | Best Practice #6: Know when to create or modify objects on the system.
|
To ensure easy customer configuration, it is important to know when to modify base system objects and when to create new ones. When you make changes to the system, make sure to document these modifications.