| SUPERVISOR|| {{guid}} || Reference to the supervisor login that finished the Task.
|}
== Implementation Guide ==
"This section provides detailed instructions for configuring and using Supervisor Tasks in UBIK."
=== Overview ===
The <code>MROCLS_MRO_SUPERVISOR_TASK</code> classification enables tasks that require elevated privileges to be completed by a designated supervisor. This feature is part of the '''MRO Supervisor Task''' functionality in UBIK and becomes available once the '''MRO Plugin''' is applied to the database.
Supervisor tasks enforce controlled execution of critical steps in a workpackage, ensuring that only authorized personnel can complete them using RFID and PIN verification.
=== Prerequisites ===
* MRO Plugin must be applied to the target database.
* A <code>SUPERVISOR</code> object must be created or configured.
* A custom MetaClass must implement both:
** <code>MROCLS_MRO_TASK</code>
** <code>MROCLS_MRO_SUPERVISOR_TASK</code>
=== SUPERVISOR Object Details ===
The <code>SUPERVISOR</code> MetaClass is derived from <code>LOGIN</code> and automatically implements <code>MROCLS_MRO_SUPERVISOR</code>. It includes the following MetaProperties:
* <code>RFIDTAG</code> (string): RFID code assigned to the supervisor’s card.
* <code>PIN_HASH</code> (string): Unlocking code required after RFID scan.
* <code>PERMISSION</code> (string): Semicolon-separated list of permission keywords (e.g., <code>WELDING;INSPECTION;APPROVAL</code>).
You can locate the default SUPERVISOR object using UID: <code>2938671d-4578-414f-9c44-8f37a7d0f689</code>.
=== Task Configuration Steps ===
# Apply the MRO Plugin to the database.
# Create or configure a SUPERVISOR object:
## Set <code>RFIDTAG</code>, <code>PIN_HASH</code>, and <code>PERMISSION</code>.
# Create a custom MetaClass implementing both required classifications.
# Add MetaProperties:
## <code>SUPERVISOR</code> (Guid): Reference to a SUPERVISOR object.
## <code>PERMISSION</code> (string): Required permissions for the task.
# Define permissions for each task using the <code>PERMISSION</code> field.
# Deploy and test using a tablet and RFID device.
=== Permission Matching Logic ===
To authorize a supervisor:
* The system compares the task’s required permissions with the supervisor’s.
* All required keywords must be present in the supervisor’s <code>PERMISSION</code> string.
* Matching is done via simple string comparison.
=== RFID Setup ===
* The RFID card must match the <code>RFIDTAG</code> of a SUPERVISOR object.
* It does '''not''' need to match anything in the task itself.
=== Typical Workflow ===
# Subordinate executes a workpackage.
# Upon reaching a Supervisor Task, they locate a supervisor.
# Supervisor scans their RFID card.
# If permissions match, they enter their <code>PIN_HASH</code>.
# If permissions do not match, access is denied.
# Supervisor completes the task.
# Subordinate continues with the workpackage.
== See also ==
* [[MROCLS_MRO_SUPERVISOR|Supervisor]]