When I wrote this article I was using the OOTB bundle process and didn't have to make amendments. The OOTB bundle process will create all the child requests for any services linked to the bundle. Yes you select the one bundle service when you make the request but this has already been linked to a number of services so the child requests will be created automatically even though there is just one automatic action.
Just to add small comment to Karens - I think there is a difference between using the OOTB 7.4 database and using the delivered 7.4 design transfer files to get the same result. When I checked the request process after a design transfer at the point where there is a comment about firing off the collection of processes attached to a bundle, the value type wasn't set to do all the items in the collection. In the OOTB it was, so it's worth having both databases on line just to compare and contrast.
(If you are using the OOTB, please ignore the above!)
I do not remember the OOTB bundle process or if it was even created as I followed the design transfer instructions almost immediately after installing 7.4.
What I am referring to is the instructions for building the bundle process within the 74ServiceCatalogue.pdf doc. I gathered they were setting value types but didnt see how the system knew to go through and duplicate the automatic action for the collection of services within the bundle. Thats not required per Karens statement and therefore the process is not misleading and thats a huge factor for me because I just built a process to calculate how many items there were and a separate path for each and its certainly not as efficient as this OOTB process given the way it works. So this is really great news and a huge relief.
I looked at your document previously Karen but I needed a definite answer on the process piece to be sure we knew exactly how much testing was required.
Us OOTB process designers and builders do like to give you guys things that are useful.