Untag all the retries of the Item
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
23-03-21 08:44 PM
Is there a way to Untag all the retries of the Item?
------------------------------
Rajesh Kumar
RPA Developer
Highmark Health
America/Chicago
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
24-03-21 03:41 AM
You can use Get Report Data from Internal - Work Queues object to retrieve the items from the work queue. You may also set Treat Each Item Separately? Flag to true to get all retries as separate Items. Then you can you use the Untag Item action to untag the Items.
------------------------------
Shashank Kumar
DX Integrations Partner Consultant
Blue Prism
Singapore
+6581326707
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
24-03-21 06:41 AM
If you are trying to remove the entries of number of retries made on the specific item in the queue, I think it's not possible to do it.
If this is not what you are asking for, can you please elaborate the question?
Thanks,
------------------------------
Shashi Kumar
Senior Consultant
PwC
Asia/Dili
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
25-03-21 12:19 AM
Thank you for the response. I have already tried above before posting.
If four items are retried twice Each Item Separately? True will give me 4 item ID's but the count will be 8 (Current BP version 6.4.2). Untag is working for only for one and retried items are not exactly getting untaged.
We are trying to reduce and remove number tags been used. This is advised by Blueprism to improve performance.
------------------------------
Rajesh Kumar
RPA Developer
America/Chicago
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
25-03-21 12:23 AM
Thank you for the response.
I am just trying to untag all the retries of an item(Not delete). If an item is retried 4 times, untag will work only for one of them we will still see tags for other 3 retries of the item in control room. Let me know if you need more info.
------------------------------
Rajesh Kumar
RPA Developer
America/Chicago
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
25-03-21 01:49 PM
Can you add the logic to untag the items before marking them as exception for retries ?
Perhaps you can add the logic for untagging as the 1st thing you do on the retry Item ?
Maybe you can untag the items when you are creating a report ?
I don't know when these tags are used and what purpose they serve so it is hard to brainstorm more solutions.
------------------------------
Jekabs Rutkis
Developer / Dev Lead / Solution Designer
Accenture
Europe/Riga
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
26-03-21 07:55 PM
I think the basic reason for this is that items used to get unique IDs even for each retry. I cannot actually remember if that ever worked since I started using BP around v5.0.24. I probably just didn't think about it at the time.
So, I would imagine your workaround options are to either (1) edit the tags in the database if you need to handle existing items or (2) always untag items before marking them as an exception or perhaps as soon as you pick up an item that is being retried. If your goal is to lighten the database, I would consider archiving old Work Queue Items so that they're not bogging down the database, and then at the same time start ensuring that your developers use fewer tags. I'm guessing that there isn't consistency in what is tagged. The basic sort of 101 rule for tagging is that they're intended to be used for management information, and unique data shouldn't be in them.
------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------
Dave Morris, 3Ci at Southern Company
