Digital DA tool - fixes/updates
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-08-22 07:22 PM
Does anyone have a newer version or list of changes needed to get the Digital DA tool working? There are a handful of small problems I've been encountering - inconsistent queue naming (bpreleases here, Releases there), places where output variables are not assigned, etc. At this point it is mostly workin, but is still failing on evaluating processes.
It seems like a potentially great tool if it worked....
------------------------------
Robert Latherow
Programmer
ADP
America/New_York
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-08-22 09:23 AM
Thanks for highlighting some errors within the Digital DA, I worked with the team who initially designed this to deliver the first verison.
Would you mind summarising the specific issues you are facing? I will then work internally to get those items addressed and an updated release provided to the DX.
Best regards,
James
------------------------------
James McLintock Program Lead
Intelligent Automation, Program Lead
Blue Prism
Europe/London
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-08-22 06:47 PM
Sure- here are the small changes that I've needed to make:
Digital DA - 01 - Populate Queue and Digital DA - 03 - Create Report = changed release queue name to 'Digital DA - Releases' for compatibility with Docs
Digital DA - 02 - Review Components > Validate Component > Read Release to XML - output XML not assigned
Digital DA - 01 - Populate Queue = changed release queue name to 'Digital DA - Releases' for compatibility with Docs
Subprocess Digital DA - 02 - Process Checks has the most issues by far. Main Page> Read Release to XML has no in or out variables set and can not function. Check infinite loops XPath is looking for 'Recovery' in the XML but it sems it should be looking for 'Recover' instead. It also errors out constantly on emtpy stageID errors. Same issue with 'Loops should not call sub-processes' check - no process checks are ultimately working for me.
Also, why are the queues and env vars not included in the release file? It would make things 100000x easier to get working.
-RJ
------------------------------
Robert Latherow
Programmer
ADP
America/New_York
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-12-22 03:35 PM
i am working on the digital DA tool as well and have encountered the same issues.
i have fixed all of them apart from the one in the Subprocess Digital DA - 02 - Process Checks where it "It also errors out constantly on emtpy stageID." Did you ever manage to solve this issue in the end?
if you did and have any help on how to fix the issue this would be a great help.
Thanks
Bradley
------------------------------
Bradley Brian
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-01-23 10:47 PM
Did you have a chance of solving this?
------------------------------
Eslam Ghandour
RPA Developer
------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-01-23 04:32 PM
------------------------------
Samad Shareef
------------------------------
