Hey team!
Is anyone else a massive fan of the Documentation View feature shown below?
For those not familiar, if you build out your processes in the Forms Process Modeller and actually include a "description" with each node..
The Documentation View automatically references that description as part of the process documentation generator.
Seriously powerful feature.. when it works properly!
The thing I'm wondering is whether or not I'm the only one that is getting random nodes from what appears to be completely random parts of the process displaying at the start of the documentation.
This has been something I've tried to work around numerous times and beyond actually deleting and re-adding nodes there is no apparent workaround to get things to appear correctly.
For example.. using the following settings:
The order of events should go by column (from top to bottom, then move to the next column), and then limit each block of columns by stage.
So lets look at our process map..
As you can see we have a starting message event, then a parallel gateway which splits into two and then that is the end of the "Customer Order Confirmation" stage.
Technically, our documentation should show two nodes within the first stage.
But instead, we see:
Which is completely random, since, without grouping by stage, Contract Generation is about 60-70 steps away and actually requires approval..
Now if you're wondering, "ah, so it is a bug with the grouping by stages so just don't group by stages", I wish it were that simple!
See, without stages.. instead we get things like the "Process Completed" node among other random nodes showing up in the first stage. The process completed node is the final step of the final stage.
I actually *love* this feature of Laserfiche Forms, but I wish that it worked properly for things larger than 5-10 nodes. The worst part is, I can't even download the documentation as a Word document so I can reorder things.. I have to "print" it as a PDF or hack the HTML that is displayed. It's so painful.
Am I the only one seeing these types of issues? I've come across it on all of our large processes but after recently upgrading to 10.4.4.444 I thought it would have been fixed by now hence mentioning it here to see if others are having the same issues?
Does anyone know any tricks to get it to display correctly where we do not need to delete and re-add nodes (since they could currently be in use)?
CC: @████████ @████████ @████████