I am working on a configurator with an output document that must support an unlimited number of configurations.
(This configurator has an unknown number of child configurators–its up to the user)
Currently, I have 2 sections of logic–Line Item and Line Detail.
Line Item - works fine, supports unlimited number of line items
The desired end result is a document which lists all line items on the first page, but each subsequent page expands on the line item as a line detail.
These line detail pages could be for Product A, Product B, Product C, etc.
To determine which configurator each line corresponds to, I intend to pass the configurator type as a global type, name, or message–whatever is less work.
I could manually set up the logic to support 50+ of each type of child configurator, but I was hoping to use something similar to an array of list to automate this process as manually setting up each section of the output document and snap logic would take a while and be prone to errors.
In case someone in the future finds themselves in a similar situation, I will briefly explain the approach I used.
SCENARIO
A parent configurator with a known number of child configurators.
GOAL
Allow external users to add as many child configurators to the parent as they want and receive an output document detailing everything they selected.
NOTES
The parent configurator serves a single purpose; to allow users to add as many child configurators as they want–there is no limit.
The parent configurator outputs a document which lists the line items the user configured.
The parent configurator will be embedded in a website–the header and bottom drawer will be inaccessible.
The child configurators are fully functional regardless of how they are started–standalone or otherwise.
Users can add each child configurator as many times as they want–there is no limit.
The “pool” of child configurators is known, but we do not know how many times a user will add it to the parent.
LOGIC
Ensure that each child configurator has a valid build, output, output template, fields, and rules.
Ensure that the parent configurator has a PDF bundle which grabs the parent’s output document AND each output document for all nested configurators.
OUTCOME
The user can add an unlimited number of child configurators to the parent configurator and receive an output document which contains the parent LINE ITEMS and the child LINE DETAILS.
LINE ITEMS is a short explanation of what something is and what it costs.
LINE DETAILS is an expansion of LINE ITEMS–it includes much more detail.
