I think what the OP said is that once the Status of the Transaction is Set on the Orchestrator, the Process will disappear from the Item, so In case you would like to to retry (meaning Retry with the Queue feature), you will not be access this “progress” then.
Unless you made a quick hit that I missed, I think the issue is still outstanding.
Hi,
One thing to note is that the queue exports only contain the item status (so failed,in progress, success, etc) and then another column for the level of failure (so business or application) If you put any specific reason for the success or failure it is not exported.
So if you want to view the reason in the queue, you can, but exporting as a report is not so useful. The other thing is that the data fields come down as one cell per transaction so you will need to parse this out to other cell…
Hi Team.
Me again. It seems that the Transaction Progress is not persistent once the status of the queue item has been changed. E.g. if set back to New or postponed any update to the Transaction progress is lost.
Could you check this please and amend for next version?
RD
Hi there @richarddenton ,
You are absolutely correct.
The feature is soooo close to being perfect, but has one minor oversight.
Setting the progress and failing the item (granted queue retries are applicable), creates a new case, with the same information/history, which can be pulled and its progress retrieved!
This means we can more accurately perform retries, directing the case to the relevant segments of the process.
BUT, as you’ve noted, postponing the item does not achieve this …
Cheers