Being able to enable/disable taglock for PASS tasks
Problem/opportunity trying to be solved
We have the option to enable/disable taglock, expect for PASS tasks (confirmed by BST). |
|
Quantify the problem/opportunity
The customer has created its own performance reports and wants to per user identify all tasks done. And therefore all tasks should have taglock enabled to see all tasks having a user ID for 100% proper reporting |
|
What is the root cause of the problem/opportunity
For performance reporting, the customer wants to do every transaction with taglock enabled to understand who did what. Not being able to enable taglock for PASS tasks, we are not always seeing the userID corresponding to the tag when the PASS task itself was executed faster then the bot picking up the usertag via BT. It's not an urgent thing, but for the customer proper reporting it would be good to have this possibility. Not sure if it's difficult to set up. |
|
Customer need date | Feb 1, 2024 |
Urgent request | No |
Report Tag | CSM |