View Process Validation results for all processes

[foehl]

Using the Process Validation Tool, I can see errors and warnings on coding best practices and issue for a process which I have open (this is related to the Design Control settings). What I'm looking for is a way to search for certain errors and warning types across ALL processes at once. For example, I want to find all processes which have warnings for "Page '*' is not called by any other page".

I had a quick look at the database tables and couldn't find anything that looks like this in the database, so I assume that the validation is done at run-time when you open the Validation Tool.

Does anyone know if it is possible to do what I want somehow?

[steven.boggs]

One suggestion that may help is to run an AutomateC.exe command to create a report with all your Processes and Objects and their validation errors:

AutomateC.exe /report C:/temp/REPORTNAME /user USERNAME PWORD

Note:

• The full path to AutomateC.exe will need to be specified.
• Use quotation marks when specifying long filenames or paths with spaces.
• You can utilize /sso or /user for your credentials depending on your environment.

This will generate a report with output like the following:

==Order Management System (Business Object)==
 *ID: 1cdba4a6-4c8c-4cf7-a699-0aff3e3f81a5
 *Created by X on YYYY-ZZ-XX 09:45:54Z
 *Modified by X on YYYY-ZZ-XX 09:45:54Z
 *Type: Object
 *Run mode: Exclusive
 *Pages: 13
 *Stages: 189
===Validation Issues===
 Total: 64
 *No 'Store In' mapping set{0} x4
 *Blank value supplied{0} x4
 *Application element '{0}' is not referenced x2
 *No preconditions are defined x11
 *No postconditions are defined x11
 *Published action does not contain a description{0} x10
 *No description given for parameter '{0}' x13
 *Data item '{0}' is not referenced x7
 *Action stage has no description x2

You could then parse this report and search for specific validation errors of interest, such as your example "is not called by any other page" to locate Processes and Objects that may contain them.

[EmersonF]

The Blue Prism team could create little hints like this, lol, I believe many people didn't know that

[foehl]

Thanks Steven. I don't want to be mean to you, because you've given me some useful information, but I'm so confused.

It's a hidden report that you can generate if someone is kind enough to tell you about it. You have to generate it via command line. It's a text file. It's human readable, but not in a standard format like XML or JSON so it's difficult to parse. Without parsing, it seems to be of limited use, especially when you have a large number of processes and objects.

What is the intended use for this report?

For my use case you mention that I can parse it to get instances of "is not called by any other page", but that's only useful if I can see which processes that occurs in, and that's really difficult to do without a standard parseable format

[steven.boggs]

The '/report' function for AutomateC.exe has been available in most versions of Blue Prism (I believe going back to v5.x when I started working here), and is documented as part of the available Command Line Options in our documentation.

I understand this may not be what you're looking for to achieve your specific purpose, but the suggestion was intended as a starting point since the report should contain the data you're looking for (albeit in a "dump" format). If you'd like to see this type of reporting improved within the product, I would suggest you submit this as an enhancement request on our Ideas Portal for consideration from our Product team. From what I understand, future versions of BPE (i.e. v7.4+) are also slated to contain improvements to the Process/Object Studios error validation and reporting functionality that may help with this as well.

I'd also recommend to browse the Digital Exchange to see if there's any ready-made reporting objects/assets that could provide the validation errors from Processes/Objects in a more usable format, or perhaps other BPE developers could share their suggestions in this thread going forward.