Data Model/Repository
Object-Based Structure: Conga CLM organizes contract data using a modular object model. The central object is the Agreement (often displayed as "Contract"), which acts as the hub for all contract-related information. Other objects like Contract Clauses, Obligations, Line Items, Team Members, and Locations are linked to the Agreement object via one-to-many relationships. This keeps data organized, scalable, and easy to maintain.
Schema Manager: Admins use Schema Manager to view, customize, and control these objects and their relationships. You can add fields, create custom objects, and manage how data is stored and connected—all without code.
Best Practices for Platform Architecture & Data Model
Leverage modular object model: Use the Agreement object as the central hub, linking related objects (Clauses, Obligations, Line Items, Team Members) for scalability and maintainability.
Use Schema Manager: Customize objects, fields, and relationships without code. This keeps your data model aligned with evolving business needs.
Synchronize data with external systems: Use ETL processes to keep contract data accurate and current across platforms like Salesforce and ERP.
Application Schema Management
Schema Manager enables system administrators to create and manage the schema of any object. You can either use the Schema Manager User Interface REST APIs or as per your business needs.
- Customize standard objects by adding more fields, picklists, and complex fields.
- Create custom objects and custom fields, picklists, and complex fields.
To open Schema Manager, go to the Conga Advantage Platform Administration dashboard and select Schema Manager. To learn more about Schema manager, objects, fields, record types, see Application Schema Management.