If we are using get queue item activity to generate report and if we set property field from to last two days for report genenration
Now the query is if we have a functionality in logic where we might need to post the item after 4/5 days and it will be process after 4/5 days
Now based on this activity it will not get this item in report because as per activity it will check the created item from last two days.
Can u suggest
Orchestrator api activity we can note use is there any way to handle this with this activity only or by some Twiks
As per my understanding you can handle this by using “get queue items” with an empty or extended “from” date to include older items, or by filtering items based on reference, status, or specific custom date fields inside the queue item’s specific content, instead of relying only on the creation date filter.
If you found helpful please mark as a solution. Thanks
Happy Automation with UiPath
I want to prepare report using get queue items activity
In the proper I am setting from field as last two days
Now the query is in my process there is logic to postpone items to 3/4 days
Now after 3/4 days those postpone items will be process but won’t be included in report
How to manager to get them in report without using orchestrator api
Hey hi
I can’t run without from property
Else it will go through numbers of items present in orchestrator
The processing time to generate report is increasing day by day if we don’t set that field
I think you can play here with creation time and postpone property of queue item.
Per my understanding, even if queue item is postponsed, its postponed property is changed but its creation date still remains the same.
So, would be a good idea to fetch the items create din last 2 days.. now in this case, even if the item is postponed, it would still show up on the report as its creation date is within last 2 days.
you can set the “from” field in get queue items to cover a longer range like last 7 days to include postponed items, and then inside your workflow filter items by their actual processing date (store this date in output or progress field when the item is processed), so your report includes only items processed in the last 2 days while keeping orchestrator query optimized.
I see you mentioned you would like to do without orchestrator api.
In that case, I think, have the datetime in your reference while creating queue item would help.
whenever adding queue item, add datetime to the reference along with whatever reference you are providing right now.
then for get queue items, you can create a condition to fetch the items where reference contains datetime from last 2 days.. now in this even if the item is postponed, it won’t matter. Those items would still be fetched for the report.
I dont think postponing the queue item would update your reference… reference would contain when that item got created in the queue.
After that if that has been postponed, reference would still contain the datetime you created that queue item on , not the date you are postponing that item to..
whenever you are creating queue item, have datetime.now added in reference
So what i understand is you are running report generation every n days and you want the count of all processed queue items within this time period but when items are postponed since their creation date is of a earlier date you are not able to fetch them and if you dont use the from filter you get mulitple result and increase in run time
So a quick thing i can think of is to have 2 assets. asset a will have report last run time updated whenever you run the report and asset b will also have last run time but you should check whether last run time is greater or equals to 15 days since that your max postponed time. If its greater update else leave as it is.
Then take 2 get queue item activities and fetch the result. in 1 activity use asset a as from property and in the other as asset b. then loop through the output of the 2 get q item and check the processed time if its less than asset a runtime that means it is already picked up in your previous report if greater it means it is not picked up so you will add those to your report and discard others.
hope this will works this is theoretical i didn’t have the time to test this approach.
edit: You mentioned you don’t want to use orch api i assume this is because of your admin not providing access but you can still use orchestrator HTTP request activity. You wouldn’t need to authenticate your request since its originating from the robot itself