I got the task to occasionally create TWO documents out of ONE Empower file with "essentially the same content but …"
I have no hint to do this when creating the Empower document in the first run. This is a decision in the "Interview page". The user may decide to create both a "long" and a "short" document that share 99% of their definition.
Here are my current findings:
- The API call for fulfillment (or creation) would return multiple outputs of the same document, like PDF + Empower without problem.
- Likewise I can receive multiple documents, if my trigger file contains multiple "Customers", but these do certainly end up in multiple Empower documents too.
- I cannot run a single customer twice in one run.
- I'd like to avoid duplicationg the structure, as it means to do every change twice or the documents drift apart.
- I obviously cannot "preview" multiple documents while in Empower
- I cannot communicate the user choice to the calling application, to get the document "fulfilled" twice with different parameters
- I cannot rely on a rule that does run during fulfillment. Yes I can create one of two choices, but I cannot just "run this document again with different settings".
- Creating a second output connector does not help me out.
In "Streamserve", I would just set a variable and call the output process (Storyteller) twice, either merging the documents or creating separate ones. No brainer.
But with "Exstream"? 😱