Menu
This article explores the various types of data locks that can be set in ResourceFirst.
(Set via Admin–>Periods)
There are two checkboxes that can be set for periods:
Locked – Financial and labor forecasts and actuals
Inactive; Time tracking is disabled in inactive periods (but not direct entry of actuals on assignment pages)
(Set via Admin–>OBS)
There are two checkboxes that can be set for each OBS node:
Locked – Prevents modifying, deleting, and adding objects in the node.(such as projects, resources, or assignments)
Active – If unchecked, the node and all related records are in the database but are not visible/loaded in ResourceFirst.
Note: Administrators can update resources in locked nodes, preventing the need to unlock the node before changes (this also applies to POST/PUT calls from the API when the token is for an administrator)
(Set via Admin–>Lists, and then the appropriate state list item)
Project, Effort, and Scenario states are each set up as Lists in ResourceFirst, and each has two checkboxes that can impact the ability to enter certain data. A project, assignment, or scenario can be locked implicitly by having its state field set to a state that is locked.
| (Project) State | Effort (Assignment) State | Scenario Status (State) |
 |  |  |
Lock Assignments; Assignments cannot be added to a project with a Project State value that is locked for assignments (such as Complete, Canceled, or Closed in the screenshot above), No fields on the project’s labor and financial forecasts and actuals can be modified. Assignments CAN be deleted if the user has proper rights.
Lock Time Tracking; Timesheets cannot be entered on a project with a Project State set to locked for time tracking (such as Complete, Canceled, or Closed in the screenshot above), .
Locked; Assignment attribute field values, and labor and financial forecasts and actuals cannot be modified on an assignment with an Effort State set to a state that is locked (such as “Proposed” in the screenshot above). Assignments with an Effort State value that is locked CAN be deleted and CAN be copied to another project.
Project Data Locked; You cannot add or modify project attribute fields in a scenario with a Scenario Status (state) set to a state that is locked for project data – the scenario owner CAN delete projects from a locked scenario.
Forecast Locked; In a scenario with a Scenario Status (state) set to a state that is locked for forecast data, labor and financial forecasts can not be added to or updated.
Fields marked “External” are read only. External means the field values are imported by an API and cannot be modified in ResourceFirst.
Some locks can be set directly by users with sufficient non-Administrator rights:
Forecasts or actuals on a given project
Forecasts or actuals on a given labor or financial assignment (field name configured as “ALocked” in assignment column headings)
Managers with Resource Administration (R3) rights to resource OBS nodes can lock them. The result of the lock is identical to when an administrator locks a node in administration.
(Set via Admin–>Lock OBS)
There are two checkboxes that can be set for each OBS node:
Locked – Prevents modifying, deleting, and adding objects in the node.(such as projects, resources, or assignments)
Inactive – Node and all related records are in the database but are not visible/loaded in ResourceFirst.
Data locks can also impact the ability to import data:
