System

Entity Fields

Manage durable field definitions used by forms, layouts, conversion, and workflow saves.

Export fields

Export, amend, and re-import field definitions. Existing field IDs keep their entity type, backend key, and system-managed ownership protected.

Entity approval routing · 5 enabled team(s)

Entity approval routing

Give each approval team one priority level. When several fields change, CMIForge routes to the highest applicable team.

TeamApproval levelFallback
Compliance Team
Contact Data Team
Partner Approvers
Entity Data Team
Finance Team

Create entity field

Only needed for Select, Multi-select, and Lookup fields.

Definitions

System-managed fields can be relabeled, hidden, or reordered. Backend keys stay durable behind the scenes.

52 fields
Entity Label Field key Type Section Order Approval team List / length Flags
Client primary-contactRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client emailRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client phoneRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client addressRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client client-numberRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client nameRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client client-typeRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client statusRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client opened-dateRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client closed-dateRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client client-partnerRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Client named-access-personRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Contact contact-numberRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Contact display-nameRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Contact organizationRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Contact titleRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Contact emailRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Contact phoneRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Contact mobile-phoneRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Contact named-access-personRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter requires-time-approvalRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter time-increment-minutesRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter time-code-setRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter primary-contactRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter emailRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter phoneRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter addressRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter matter-numberRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter nameRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter descriptionRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter practice-areaRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter matter-typeRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter statusRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter opened-dateRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter closed-dateRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter responsible-userRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter lead-partnerRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Matter named-access-personRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party primary-contactRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party emailRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party phoneRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party addressRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party party-numberRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party nameRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party party-typeRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party statusRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
Party named-access-personRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
User system-idRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
User display-nameRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
User emailRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
User titleRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System
User entra-upnRead-only reference Priority comes from the team routing setup above. Only needed for Select, Multi-select, and Lookup fields.
System