User Setup — Custom Fields
The extension adds 1 field to the standard User Setup table.
Field Reference
| Field ID | Field Name | Data Type | Description |
|---|---|---|---|
| 51300 | Project Closed | Boolean | When enabled, the Project Closed and Project Open actions are visible on the Job Card for this user |
Config Package Notes
- Include in config package if the customer uses the project (Jobs) features
- Set to
Yesfor users who should see the close/reopen actions - Default is
No— the actions are hidden
Usage
This is a visibility flag, not a permission. When the Job Card opens, the page looks up a User Setup record for the current user with Project Closed = Yes; if one is found the two actions are shown, otherwise they are hidden.
Hiding an action is not a security boundary. The Job field Project Closed (Job field 51312) is declared Editable = false, so it cannot be typed into on the page — but the flag itself blocks nothing at table or permission-set level. Do not present it to the customer as an authorization control. If the customer needs a genuine restriction, it has to be implemented with BC permission sets.
Related
The Job Card also exposes a Project Closed checkbox (read-only) and the Job List shows it as "Closed Project". Job planning lines and job task lines check the Job's Project Closed value to prevent changes on a closed project.
The Jobs part of this extension is legacy code inherited from a previous developer and is scheduled for review and rebuild. Treat the behaviour above as a description of what the current code does, not as a stable contract.