Blueprints Good to Know
- A Blueprint is a working copy of changes to your CSM system definitions (Business Objects, Fields, Forms, Grids, etc.) that allows you to make offline changes and then publish them to your live system at a later time.
- A Blueprint is typically identified by the Blueprint icon .
- Because Blueprints affect system definitions, Blueprints are used and managed from within CSM Administrator. Access Blueprints and Blueprint functionality from the CSM Administrator Blueprint page.
- Use the Blueprints page to quickly access common Blueprint operations.
- When creating and working with Blueprints, the CSM Administrator interface changes to the Blueprint Editor, which allows you to:
- A Blueprint is unnamed until it is saved to a named .bp file. The name of the open (working) Blueprint is displayed at the top of the CSM Administrator window and at the top of the Blueprint Editor.
- If you try to close a Blueprint before saving it to a named .bp file, CSM prompts you to name and save the Blueprint. If you try to close a named Blueprint without saving changes, CSM prompts you to save the changes.
- Publish a Blueprint to commit definition changes to a test or live system.
Always consider the following:
- CSM is highly configurable: Users decide what to track, how to track it, and how it looks. To help get the system started, CSM ships with Out Of The Box (OOTB) content in a Starter Database (includes OOTB Business Objects (including Forms, Grids, and Relationships), Dashboards, Calendars, Reports, One-Steps, a security design, etc.). With security rights, Users can add, edit, and delete almost anything in CSM. Therefore, the system's structure, design, and UI might greatly vary from the examples in our documentation.
- Security rights control access to Blueprint functionality and are configured in the Security Group Manager in CSM Administrator (CSM Administrator>Security>Edit Security Groups). For more information, see Configure Blueprint Security Rights.