Audit Panel & Read-Only Fields
Audit Panel
Click the info icon (i) on any row to open the audit panel for that record:
- Shows record metadata: created by, created date, last modified by, last modified date
- Displays a change history timeline with all saved changes for that specific row
- Unsaved pending changes appear at the top with an orange (unsaved) indicator
- Domain attribute values are displayed as
{Code} Nameinstead of raw database IDs - Only fields that were actually changed are shown per edit entry β unchanged fields are excluded
- The row is highlighted in teal while the audit panel is open
- Click the info icon again or click outside the panel to close it
Read-Only Fields
A lock icon (π) on a cell or field means it cannot be edited in the current context. There are several reasons a field may be read-only:
1. No Update permission
Your user role does not have the Update permission for this entity, or the attribute-level permission is set to Read. Permissions are checked at three levels:
- Model level β CRUD defaults for all entities in a model
- Entity level β CRUD overrides for a specific entity
- Attribute level β Read/Write for a single field
If you need edit access, ask your administrator to enable the U (Update) permission for your role in Settings β Access Management β Roles.
2. Record has a pending approval
If the entity uses the Requires Approval workflow, a record that has already been submitted for approval is locked for all users until the change is approved, rejected, or returned. You will see a lock icon on the entire row. Once the pending change is resolved, the record becomes editable again.
3. Preview As mode
When an administrator is using Preview As (testing another user's permissions), the entire grid is read-only regardless of permissions. The blue banner at the top of the screen indicates that preview mode is active.
4. License expired
If the Primentra license has expired, the application runs in read-only mode until a valid license is activated.