Posted: 30 Mar 2015 9:16 EDT Last activity: 17 Jul 2017 15:52 EDT
Expressing the details in process flow steps
Much of the auto-doc capabilities are concentrated in the button that generates a mega-document.
We need documentation that is more agile -- i.e., off of a standard button on each ruleform -- "Show Doc".
This will allow us to better review the rule development at any time, without having to rely on generating the full document.
the v7 stage-based flow process definition is an improvement over the process flows -- by recognizing that processing is generally linearly and ought to be depicted as such -- but it still requires multiple clicks to fish out all the details.
Is there any generated representation which exists, which can show the Case details, and then, for each process, and for each assignment therein:
Assignment type (worklist / workbasket / etc)
Routing (w/ Parameters)
Notification (w/ parameters)
SLA (w/ parameters -- and drawing in SLA times)
Actions available, with list of inputtable fields
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
>>> We need documentation that is more agile -- i.e., off of a standard button on each ruleform -- "Show Doc".
I agree, Jon. The particular subset of this that is a hot button for me is for activity rules. Here are two user stories (hi Kip!) :
1) My customer is having trouble with an activity, and I’d like to “see” the activity. My choices today are either have them rap/zip the activity, which can be cumbersome if I don’t have the supporting rulesets and objects referred to by the activity, or have them do “expand all” button on the activity ruleform and then snapshot it all for me or attempt select-all of the resultant html, which gives a lot of extra items that make it not so readable, such as all the unused fields, or they can click the “review” button and then expand all the portions of the screen and then snapshot that or select-all the resultant html. This last choice is closest to what I think we want.
2) I have an existing activity that I want to port back to an older version of Pega/prpc. It would be nice to export it in a format that can easily be used as input to a tool (and also be human-readable) on that older version and the output would be a real activity rule.
adding to this statement: Actions available, with list of inputtable fields
Remember, in a typical flow, there's 1-2 flow main flow actions. You've got to doublle click the flow action connector, open the flow action rule, look at the layout tab, look at the section rule, click that, and see the design... and then see the fields from there (or even click further to find the property names).
This is a mess, and it remains so through all these versions.
At some point, we've got to converge on a flow/process presentation that provides clarity.
(One memory I have working on PRPC years ago was showing a flow print-out to a very senior executive and having him pencil in the status field on the printed page. Because the status field is just another parameter to an an assignment activity, and as such, it's not special to the flow, so it doesn't show up in the diagram)