CREVIA V11 · ENGLISH USER GUIDE
Glossary
On this page
8.4 Glossary
Terms include product labels and general database/print concepts. Matching terminology does not make fields, permissions, or parameters interchangeable between systems.
8.4.1 Products and Work Objects
| Term | Meaning | Distinction |
|---|---|---|
| CREVIA | Credential design/operations/output system | Not one database or driver. |
| CDPS | Credential Design & Policy Studio | Design/data configuration/policy, not routine operations. |
| COC | Credential Operations Console | Personnel/production under layout policy, not a design replacement. |
| CREVIAUpdata | Delivered updater name | Launch/handoff is not completed installation. |
| Layout | Card design and related configuration | Not personnel database or driver settings. |
| Card face | Designed/output card region | Card size is not paper size. |
| Static element | Content independent of current person | Static does not mean uneditable. |
| Dynamic element | Content from fields/numbering/configured sources | Source availability is not guaranteed. |
| Default layout | Saved startup project entry | Not necessarily the newest modified disk file. |
8.4.2 Databases and Fields
| Term | Meaning | Distinction |
|---|---|---|
| Data source | Records and connection configuration | Not a UI view. |
| Provider/driver | Access component | One driver does not cover every database. |
| DSN | ODBC named driver/connection settings | Same name across PCs need not mean same target. |
| Connection string | Target/access parameters | Can contain secrets; do not publish. |
| Main table | Primary business read/write target | Not determined by screen position. |
| Primary key | Field(s) uniquely identifying a row | Not any column named Number. |
| Foreign key | Reference to another record identifier | Stored ID can differ from displayed name. |
| Match key | Import update locator | Must meet main-table uniqueness rules, not inherently a name. |
| NULL | Missing/unknown database value | Not zero, empty text, or simply unchecked. |
| Binary photo | Image byte contents | Not a path string. |
For example, a stored numeric department ID can display Visitor Services. Verify that mapping when importing names or grouping; do not write the name into the ID.
8.4.3 Queries, Scope, and Views
| Term | Meaning | Distinction |
|---|---|---|
| SQL | Query/operation language | Dialect and writability depend on engine/structure. |
| Main SQL | Layout's primary query | Not always every user's effective query. |
| User group SQL | Role-specific query | Takes precedence, not merely an added filter. |
| INNER JOIN | Matching related combinations | Can omit people without related photos/categories. |
| LEFT JOIN | Retain left-side records, unmatched right may be NULL | Left is defined by SQL, not canvas placement. |
| Search/filter | Narrow relevant displayed scope | Clearing UI conditions does not remove SQL conditions. |
| Grouping | Categorize/select existing results | Does not redefine main SQL or create tables. |
| Grid View/GV | Row/column data presentation | Shares data with card view but saves layout separately. |
| Card View/LV | Card-arranged personnel fields | Not the printable credential face. |
| In-place editor | Cell editor control | Editor selection does not guarantee saving rights. |
Counts can reflect group SQL, joins, search, filters, and grouping simultaneously. Establish scope before statistics/export.
8.4.4 Printing, Imposition, and RFID
| Term | Meaning | Distinction |
|---|---|---|
| Credential preview | Current record applied to design | Not proof of physical dimensions/color/device completion. |
| Sequential printing | Record-by-record task order | Different unit from an imposed group. |
| Copies | Repetitions of output content | Separate from people and slots. |
| Duplex | Front/back of one card | Not two-up. |
| Two-up | Two cards on a page | Single-sided; incomplete groups retain blanks. |
| Free imposition | Row/column cards on a sheet | Capacity rows times columns; no duplicate person to fill blanks. |
| Overall rotation/alignment | Transform/position the group | Not individual design-object editing. |
| Registration holes | Page positions for finishing | Require physical-process validation, not personnel fields. |
| RFID encoding | Writing chip business data | Printed numbers are not chip data. |
| Manual integrated production | Print, operator presents card, write, automatic next | Does not require SDK-driven internal transport. |
| Automatic integrated production | Device-coordinated printing/encoding | Requires compatible hardware/SDK/workflow, not just any reader. |
| Post-print writeback | Configured business-field updates | Stored status alone does not prove delivery. |
Automatic printing is a continuous rule-based task with separate conditions/writeback checks. Pause does not recall queues. Submission, physical output, encoding, and recipient collection are separate outcomes.
8.4.5 Licensing, Identities, Publishing, and Maintenance
| Term | Meaning | Distinction |
|---|---|---|
| Product license | Edition/term/features | Not role/database rights. |
| Licensing account | Registration/service identity | Not directly a COC role login. |
| Role user/group | Business access/policies | Admin role does not grant database administration. |
| Open-access mode | No role-login requirement under configured policy | Licensing/database authentication still apply. |
| Renewal/validation | Periodic verification or renewed license | Not necessarily buying a new perpetual license. |
| Grace period | Policy-defined additional time | Not universal or a fixed duration for every license. |
| Publishing/synchronization | Save release and retrieve by client settings/version | Not personnel replication or driver deployment. |
| Backup | Consistent recovery data/dependencies | Ordinary export or same-name copy is not automatically recoverable. |
| Recovery | Rebuild and verify usable state | Copy completion is not business acceptance. |
| Debug/Release | Development/formal build modes | No Debug logs in Release; not an excuse to bypass formal checks. |
Product, role, and database permissions are independent layers. Supply actual UI wording and location for ambiguity rather than only saying "account problem."