Skip to main content
Skip table of contents

FAQ – Bunker Requirement – Troubleshooting Locked “Request Status” and “Port” Fields, and Understanding Operator and Bunker Manager Module Rights


In the course of the bunkering workflow, users may need to update or change the Request Status or Port on a Bunker Requirement. However, these fields may sometimes appear locked, which can cause confusion when edits are required.

This article explains the possible causes and how configuration flags and module rights affect the ability to edit these fields.

image-20251030-085630.png

Locked “Port” Field

When the Port field is locked, review the following configuration flag:

Flag/Name

Description

Lock Port Name in Bunker Requirements
CFGLockPortNameInBunkerReqs

 

When enabled, the user is prevented from changing the port name once a requirement is created and saved with any status. If the user wants to change the port in the same Bunker Requirement, they will have to cancel/delete it and create a new Requirement.

Locked “Request Status” Field

When the Request Status field is locked, review the following configuration flags to determine if either is set to Y:

Flag/Name

Description

Lock Cancelled Requirements
CFGLockCancelledRequirements

When enabled, the user is prevented from setting the status of a Bunker Requirement to any other status once it has been set and saved as Cancelled.

Lock Confirmed Requirements
CFGLockConfirmedRequirements

 

When enabled, the user is prevented from setting the status of a Bunker Requirement back to Preliminary once it has been set and saved as Confirmed/Pending Approval/Approved. Setting the requirement status to Cancelled will prevent users from further changing the requirement status to any other state.

 If the respective configuration flags above are disabled but the field is still locked, review the user’s module rights (see below).

Module Rights Affecting “Request Status” and “Port” Fields

Even when configuration flags are set to allow editing, module rights can still restrict access to these fields.

The “Request Status” field is controlled by the Module Right “Edit Operator’s Fields on Bunker Requirements”. Please refer to the screenshot below on fields affected by “Edit Operator’s Fields on Bunker Requirements”. 

image-20251030-090050.png

While the “Port” field can be controlled by “Edit Bunker Manager’s Fields on Bunker Requirements”. Please refer to the screenshot below on fields affected by “Edit Bunker Manager’s Fields on Bunker Requirements”.

image-20251030-090124.png
Related Configuration Flags

Name/Flag

Description

Lock Port Name in Bunker Requirements
CFGLockPortNameInBunkerReqs

When enabled, the user is prevented from changing the port name once a requirement is created and saved with any status. If the user wants to change the port in the same Bunker Requirement, they will have to cancel/delete it and create a new Requirement.

Lock Cancelled Requirements
CFGLockCancelledRequirements

When enabled, the user is prevented from setting the status of a Bunker Requirement to any other status once it has been set and saved as Cancelled.

Lock Confirmed Requirements
CFGLockConfirmedRequirements

 

When enabled, the user is prevented from setting the status of a Bunker Requirement back to Preliminary once it has been set and saved as Confirmed/Pending Approval/Approved. Setting the requirement status to Cancelled will prevent users from further changing the requirement status to any other state.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.