Status Master

1What is this master? #

• One record per status. Use Find (F2) to load one, Add (F3) to create, Modify (F4) to edit, Save (F5) to store, Esc to cancel an edit.
• Opened as an embedded dialog from another screen, Use status returns the loaded status name to that screen.

2Step by step #

The status list is the shared vocabulary of record states across the application.

1. Press Add (F3) , name the status and its group/kind as the form asks, save with F5 .
2. Prefer adding new statuses to renaming built-ins — two dozen tables and the row-colour rules read this list.

3Fields #

• Status Name is the status text (up to 50 characters), is required and must be unique. On a reserved status the name is locked — the database refuses renaming it.
• Description is free descriptive text (up to 255 characters).
• Colour is the display colour of the status, stored as a hex code like #22aa55 . Type the code or pick it visually with the colour swatch beside the box — both edit the same value.
• Module names the module(s) this status applies to, so screens can offer only their own statuses.
• Is Reserved ? marks a system status. It can be set only while adding — once saved reserved, the row is permanently protected (no rename, no delete) and the switch is locked.
• Is New ? flags the status as newly introduced (on by default for new rows).
• Is Active ? keeps the status offered in pick-lists; switch it off to retire a status without deleting it.

4Integrity rules #

• The status name is unique — a second status with the same name is refused.
• Reserved statuses can be neither renamed nor deleted — database triggers refuse both, and this page locks the name box and the Delete button for them.
• User permissions (_PERM triggers) can refuse a save or delete even when the form allows it.
• Deleting a status also clears its document links (a database trigger cleans them up automatically).