Functional Envelope Copy Rule

The Functional Envelope Copy feature allows the processing of the same envelope in more workflows and with the same data owners, with an intermediate end status for the original envelope. It can be triggered by any status in the UP and BP workflow. Once the original envelope has reached the status inventory, an exact copy of it is made and the cloned envelope is shown in a destination inventory, which is the starting point for new processing. The first data owner/user can still follow the new processing and view the original envelope into the end-status inventory.

During the copy:

All data that was available in the input file (functional data) is kept,

Unique own reference of the newly created envelopes and payments are generated

Data enriched during the enrichment phase, as Internal Classification Type, Data Owner, Confidential flag and Custom fields are kept,

While Number of Signatures, Processing History, the Representation, Approvals,...(processing data) are removed from the clone as compared to the original.

Moreover the clone will contain an entry in the Processing History, showing information about the database ID of the original file in the message: “This workflow object with {clone DBID} is a copy the workflow object with {original DBID} created at {datetime}.” There is no linking between the original envelope and its clone, neither via internal nor external Status Feedback.

The functional envelope copy rule (FunctionaEnvelopeCopyRule) makes a functional copy of the entire envelope. The clone is fully ready to be processed in a workflow. All technical and internal processing attributes are removed.

The functional envelope copy rule always expects a single Envelope or Payment value object as input which is why the “Invoke on Collection elements” option on the rule sequence must be turned on. This rule will only return the copy of the original and it has no rule parameters. All additional processing has to be done, leveraging other existing functionalities (e.g. setting the destination repository with the “setrepository” rule, generating a new Own Reference using the CEV framework).

Figure 153 FunctionalEnvelopeCopyRule

Example of integrating the FunctionalEnvelopeCopyRule into the BP-release step of the BP workflow where within the ApplyRuleSequenceRule the “FunctionalEnvelopeCopy” rule sequence is called and afterwards the copy of the original envelope is re-directed to a new repository using the “setrepository” rule.

Figure 154 FunctionalEnvelopeCopyRule integrated in BP-release rule sequence

Example of integrating the FunctionalEnvelopeCopyRule into the UP-release step of the UP workflow.

Figure 155 FunctionalEnvelopeCopyRule integrated in UP-release rule sequence