As we know F-Tag is also known as Issue Tracker, the tracking of the F-Tag is the main part of its proceedings.
F-Tag proceeds through 4 stages:
Open
Pending Verification
Overdue
Close
These stages proceeds in the same manner as numbered above with some internal connections.
Below is a step wise process to explain how an F-Tag would operate in a real-life scenario according to the stage-wise process mentioned above.
Stage 1
Let us assume an issue arises and en employer raises an F-Tag.
The employer puts in various information required and the Due date is 3 days from now.
Tag Status : Open
Stage 2
When an F-Tag is created successfully it is saved in the database as an open F-Tag. It has been saved but not sent for verification i.e. not submitted.
An Open F-Tag has to be submitted for it to process to the next stage.
Click on Submit button next to the Attach button (both in the Side Window & Detail View)
Once you submit, the F-Tag’s becomes available for analysis and feedback.
Tag Status: Pending Verification
Step 3
The F-Tag is now being analyzed and the issue raised is being analyzed by the concerned authority.
A new Mark as Complete drop-down menu becomes available.
Useful Facts!
While creating an F-Tag, the information field Default Assignee lets you assign a person for the issue therefore indicating towards the concerned authority/employee responsible for it.
You can set an assignee for an F-Tag each time you create one or can set a standard default assignee based on priorities and pillars!
There are two options available in this menu:
Mark As Complete | This selection confirms the issue has been dealt with and solved. Therefore, the F-Tag gets closed hence the status changes to Close. |
Send Back | The F-Tag is sent back by the assignee with an attached send back Reason. |
Tag Status: Closed (When Marked as Complete)
Tag Status: Open (When Sent back)
Useful Facts!
The Add Reason field inside the window is a required field, therefore the Send Back Button (Greyed out) becomes active only when there is some text or data in the field above.
The status of the F-Tag changes to Open. It has to be submitted again by changing the assignee. It can be done by editing the information of the F-Tag concerned.
Useful Facts!
The process of “sending back” a Tag is called User Re-Assignment.
Follow the Smart Connection to learn more!
Smart Connections
Step 4
It is possible that the concerned authority (F-Tag Assignee) might not be able to analyze and act on the issue raised in time.
In such cases, if the F-Tag remains in Pending Verification status past the due date mentioned while creating it, its status changes indicating the fact that the problem was not resolved in the time period that was mentioned by the tag creator.
Tag Status: Overdue
Useful Facts!
Notice the Tag above has overdue status with the Submit button?
Whenever the tag is sent back and the date is past due date, it will have an overdue status while being open.
It indicates that the tag has not been handled and creates urgency by marking the overdue status. It needs to be submitted after every instance where it is overdue or sent back i.e. Re-Assigned.
Step 4
When all issues are dealt and the F-Tag proceeds through all its stage without being late, the F-Tag is finally marked as complete by the assignee on record.
In real life scenarios where the issue might be important and needs urgent attention, sending back an F-Tag (User Re-assignment) may lead to crucial time loss and subsequent delays in resolving the issue.
To prevent this from happening, the User Re-Assignments can be limited.
Congratulations! We have successfully learned how to operate an F-Tag!
At times there are scenarios where a similar issue arises again and an F-Tag is required to be created or an issue may require more than one person’s attention.
In such situations, a pre-existing F-Tag can be cloned and raised by editing some details as per requirement rather than creating a tag from scratch !
Let’s go ahead and learn how to clone an F-Tag!