4.1.8. Streamlined Document Archival – Push Templates & Files to EPC

We have introduced a new feature that streamlines document archival by automatically sending templates and files linked to a form directly to EPC.

How It Works:

Upon the feature’s activation in a form, a new folder is automatically created within the specified EPC document folder or set. This new folder, timestamped with the date and time of creation for easy reference, contains the generated form template along with any attached files.

• Additionally, if configured for archival, the reference ID will be used to uniquely identify the newly created folder.

!To effectively utilize this feature, users must manually create the destination document folder or set in EPC beforehand.

*Please note that the archived template includes any digital signatures provided during the workflow.

How to Implement:

This feature can be adapted to various scenarios, offering flexibility in its application.

*Users, for example, can integrate the feature directly within the form interface by linking the provided code to a button control. They can also enhance its functionality by incorporating additional business logic into the code. This includes specifying conditions for archival, different destination locations, and more.

To implement the primary use case, however, wherein the feature is triggered upon form submission, follow these steps:

1. Create Post-Form Action: Begin by creating and saving a post-form action for the form.
   

   **Note that only one post-form action is permitted per form. If one is already linked, proceed to step 2.

2. Launch Code Designer: Launch the Code Designer for the post-form action by clicking the Edit Code option in either the menu bar or the context menu (accessible via right-click).
   
3. Add, Build, & Save Code: In the Code Designer, input and save the following code snippet:

var errors = new List<string>();
if (bpmAppService.BPMSServices.EPCService.Login(out errors))
{
  bpmAppService.BPMSServices.EPCService.ArchiveTemplateWithAttachments("EPCFolderID", new List<string> {domainObject.FileAttachmentAttribute}, domainObject.ReferenceID);
}

*

Code Implementation Notes:

• Required Parameter:
  • Replace ‘EPCFolderID’ with the specific ID of the EPC document folder or set where the files/templates should be sent.
  
  
• Optional Parameters:
  • Replace ‘FileAttachmentAttribute’ with the attribute of the file attachment control holding the intended files.
    • If pulling from multiple file attachment controls, separate the attribute names with commas.
      • For example: domainObject.Documents1, domainObject.Documents2
    
    
  • Replace ‘ReferenceID’ with the attribute of the control representing the reference ID.
    • For example: domainObject.IncidentID
    
    

4. Link Action to Form Behavior: Finally, link the post-form action to the relevant form behavior.
   

   **To enhance flexibility when sending templates by email or to EPC, we now provide users with the option to rename the template file. For more information on this option, click here.

*For a more detailed step-by-step guide on implementing this use case, click here.