ShowMgr combines shared records and workflows with client configuration. Classes, attributes, statuses, navigation and access levels determine how work is presented and managed.
Order classes define the work context
An order class identifies a type of work and provides settings for its behavior. Client-specific class settings include the displayed name, creation and read access, grid visibility, web-request availability, quick-add behavior, allowed elements, conflict checking and booking rollups.
Two classes can therefore expose different fields, element choices and actions even when both are managed through the order module.
| Configuration area | What it controls |
|---|---|
| Order class | The type of work and its class-level behavior |
| Attributes | Additional information associated with orders, bookings, actuals or other records |
| Statuses | Workflow state and the actions available for the relevant record |
| Element rules | Which resources or items apply to a class |
| Hierarchy and rollups | Relationships and presentation of parent and child work |
| Navigation | Module labels, availability and visibility |
Attributes belong to a record
Order attributes, booking attributes and actual attributes have different owners. A similar label on two screens does not make them the same field.
When creating an actual, ShowMgr can copy applicable booking attribute values as starting values and then apply values supplied for the actual. The actual retains its own attribute values.
When comparing fields, identify the owning record, attribute ID, data type, available options and applicable class. This distinguishes a display difference from a difference in the stored information.
Status lists depend on context
Booking-status selection uses the client, element type and order class. Crew Portal settings can also exclude statuses or affect which actions are available.
Order status, booking status and actual approval status each belong to a different record or workflow. A status change in one area should be interpreted in that context.
The active/inactive flag is separate from workflow status. A report or integration filter must use the appropriate field for the result it needs.
Configuration and permissions work together
Class settings determine how a type of work is configured. User access levels determine the user's available actions and navigation. Record-specific controls provide further context inside a module.
When two users see different fields, statuses or actions, compare the client configuration, order class, user access levels and record state. When comparing two orders, also check whether they use the same class and hierarchy.