{"id":34699,"date":"2019-08-29T15:24:55","date_gmt":"2019-08-29T23:24:55","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?page_id=34699"},"modified":"2022-02-02T14:40:55","modified_gmt":"2022-02-02T21:40:55","slug":"custom-export-plugin-configuration-and-user-guide","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/features-and-functions\/administrator\/moduleplugin-configuration\/export-module\/custom-export-plugin-configuration-and-user-guide\/","title":{"rendered":"Custom Export Plugin"},"content":{"rendered":"
Available:\u00a0<\/strong>on-premises, cloud<\/p>\n This document describes the concepts, configuration, and additional information about using the Custom Export plugin with Ephesoft Transact. This plugin can be used with other export module plugins to maximize the desired outcome.<\/p>\n <\/a> The Custom Export plugin includes significant flexibility for data and metadata output from the workflow. Benefits of this plugin include the following:<\/p>\n <\/a> The Custom Export plugin is designed for the administrator responsible for configuring the batch class. This plugin provides two major output functions as follows:<\/p>\n 1. Exporting the data\/metadata file<\/strong>:<\/p>\n 2. Exporting the image files with ability to name the output files and target folders<\/strong>:<\/p>\n The Custom Export plugin in Ephesoft Transact has the following limitations:<\/p>\n Ensure that Ephesoft Transact is properly installed and licensed.<\/p>\n The Custom Export plugin is configured in Batch Class Management.<\/p>\n Perform the following steps to enable and configure the Custom Export plugin for the batch class:<\/p>\n 1. Log in to Ephesoft Transact as an administrator. Navigate to the Batch Class Management<\/strong> screen.<\/p>\n <\/p>\n Figure 1. Batch Class Management<\/strong> Screen<\/em><\/span><\/p>\n 2. Open the batch class that will use the Custom Export plugin. The components and settings for this batch class display.<\/p>\n <\/p>\n Figure 2. Viewing Current Configuration for a Batch Class<\/em><\/span><\/p>\n 3. Expand the Export<\/strong> module. The plugins that are configured for this module display in the left-hand navigation panel.<\/p>\n <\/p>\n Figure 3. Export Module Prior to Configuring Custom Export<\/em><\/span><\/p>\n 4. Add the Custom Export plugin to the Export<\/strong> module:<\/p>\n a. On the right side of the screen, locate the CUSTOM_EXPORT<\/strong> plugin in the Associated Plugins<\/strong> field. Select it and move it to Selected Plugins<\/strong> field on the right.<\/p>\n <\/a><\/p>\n Figure 4. Example of Adding the CUSTOM_EXPORT to the Export<\/strong> Module<\/em><\/span><\/p>\n Note:<\/strong> The CLEANUP<\/strong> plugin should always be the last plugin to run in the Export module. If the CLEANUP plugin is not last in the workflow, move it\u00a0below the CUSTOM_EXPORT<\/strong> plugin.<\/p>\n \u00a0 \u00a0c. Click Deploy<\/strong>. The CUSTOM_EXPORT <\/strong>plugin displays in the Export<\/strong> module for this batch class.<\/p>\n <\/a><\/p>\n Figure 5. CUSTOM_EXPORT Added to a Batch Class<\/em><\/span><\/p>\n 5. Enable the Custom Export plugin:<\/p>\n a. Select CUSTOM_EXPORT <\/strong>in the left-hand navigation pane.<\/p>\n b. In the Plugin Configuration<\/strong> section on the right, set the Custom Export Plugin Switch<\/strong> to ON<\/strong>. Click Apply<\/strong>.<\/p>\n <\/p>\n Figure 6. Custom Export Plugin Switch<\/strong><\/em><\/span><\/p>\n 6. Configure the Custom Export plugin:<\/p>\n a. Select Configure<\/strong> under the CUSTOM_EXPORT<\/strong> plugin on the left navigation pane. The current configurations for this plugin display.<\/p>\n <\/a><\/p>\n Figure 7. Configuring Settings for Custom Export<\/em><\/span><\/p>\n This screen contains the following columns and information:<\/p>\n b. Click Add<\/strong> to create new configurations, or click Edit<\/strong> to display and adjust the existing configurations. The Custom Export Configurations<\/strong> screen displays.<\/p>\n <\/p>\n Figure 8. Custom Export Configurations Screen<\/em><\/span><\/p>\n c. Configure the settings for this plugin to include the output format and folder structure.<\/p>\n <\/p>\n Figure 9. Sample Invoice and JSON Files<\/span><\/em><\/p>\n <\/p>\n Figure 10. Sample Invoice XML Files<\/em><\/p>\n Replacement variables and XPath syntax can be used as dynamic placeholders to provide custom names for folders and files, and to export specific metadata from your documents and batches.<\/p>\n Placeholder variables are available for several common elements within a batch.<\/p>\n The following table shows the variables and the syntax to be used to generate dynamic metadata file names, document file names, file locations, and metadata content. Refer to the Figure 10 above and the samples in the table below to see how placeholder variables in the table can be used.<\/p>\n To enter a replacement variable in any of the File Name<\/strong> or Folder Path<\/strong> fields, perform the following:<\/p>\n 1. Click into the text box (e.g., for the File Name<\/strong> field), and enter a tilde (~). A drop-down list with all available variables displays.<\/p>\n 2. Enter the variable values or select variables from the drop-down list.<\/p>\n 3. Separate the values by entering the desired separators (e.g., dashes (-) or underscores (_)).<\/p>\n <\/p>\n Figure 11. Enter Variable Values<\/em><\/span><\/p>\n The placeholder above must be replaced with the name of the batch class field.<\/p>\n Example: ~BCF$User_Name:Value~<\/td>\n<\/tr>\n The placeholder above must be replaced with the name of the index field.<\/p>\n Example: ~DLF$FED_TAX_FORM_1040:SSN~<\/td>\n<\/tr>\n Using XPath syntax provides a simple way of locating data in an XML file when nested XML header tags are separated by slashes. For example, the XPath expression ~<\/strong>\/Batch\/BatchSource~<\/strong> in Figure 12 can be used to extract any information from your batch.XML file to the exported metadata file.<\/p>\n <\/p>\n Figure 12. Using XPath to Extract Data from a Batch XML File<\/em><\/span><\/p>\n Also, consider Figure 13 below that shows a portion of an XML file for a batch.<\/p>\n <\/p>\n Figure 13. XML File for a Batch<\/em><\/span><\/p>\n See the following for examples of retrieving XML values using XPath:<\/p>\nIntroduction<\/h2>\n
<\/a>Benefits of the Custom Export Plugin<\/h2>\n
\n
<\/a>Primary Functions of the Custom Export Plugin<\/h2>\n
\n
\n
\n
\n
\n
<\/a>Limitations for Custom Export Plugin<\/h2>\n
\n
<\/a>Configuring the Custom Export Plugin<\/h1>\n
<\/a>Prerequisite<\/h2>\n
<\/a>Procedure<\/h2>\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\nThis section contains the following fields:<\/p>\n\n
\n
\nNote<\/strong>: \u00a0There are several limitations related to folder paths and file names.\u00a0 A combined folder path and file name must not exceed 255 characters. File names cannot contain \/*:<>|,? characters (if any of these characters appear in a file name at export time, they will be removed).<\/li>\n<\/ul>\n<\/li>\n
\nThis section displays a customer generated file containing placeholders and XPath expressions configured within it. For example, if you want to export metadata from Ephesoft Transact into a JSON file format, you must create a JSON schema file. The JSON schema file is a JSON file with placeholders for Ephesoft Transact values. When a batch instance is exported, Ephesoft Transact will replace those placeholders with their actual values and export the resultant file at the location provided in the Folder Path<\/strong> field. See the examples below for sample JSON and XML schema and output files:<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/a><\/a>Using Dynamic Placeholders<\/h2>\n
<\/a>Replacement Variables<\/h3>\n
\n
\n
\n
\n<\/strong>Note:<\/strong> Ephesoft Transact will append the appropriate file extension (i.e., .PDF or .TIF) to the exported files.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n
\n Variable Relates to<\/strong><\/td>\n XML Field Name <\/strong><\/td>\n Placeholder<\/strong><\/td>\n<\/tr>\n \n Batch class<\/td>\n BatchClassIdentifier<\/td>\n ~BC:Identifier~<\/td>\n<\/tr>\n \n Batch class<\/td>\n BatchClassName<\/td>\n ~BC:Name~<\/td>\n<\/tr>\n \n Batch class<\/td>\n BatchClassDescription<\/td>\n ~BC:Description~<\/td>\n<\/tr>\n \n Batch instance<\/td>\n ReviewedBy<\/td>\n ~BI:ReviewedBy~<\/td>\n<\/tr>\n \n Batch instance<\/td>\n UUID (Unique identifier for the batch)<\/td>\n ~BI:UUID~<\/td>\n<\/tr>\n \n Batch instance<\/td>\n BatchCreationDate<\/td>\n ~BI:CreationDate~<\/td>\n<\/tr>\n \n Batch instance<\/td>\n UNCFolderPath<\/td>\n ~BI:UNCFolderPath~<\/td>\n<\/tr>\n \n Batch instance<\/td>\n BatchInstanceIdentifier<\/td>\n ~BI:Identifier~<\/td>\n<\/tr>\n \n Batch instance<\/td>\n BatchInstanceName<\/td>\n ~BI:Name~<\/td>\n<\/tr>\n \n Batch instance<\/td>\n BatchInstanceDescription<\/td>\n ~BI:Description~<\/td>\n<\/tr>\n \n Batch instance<\/td>\n ValidatedBy<\/td>\n ~BI:ValidatedBy~<\/td>\n<\/tr>\n \n Batch class field<\/td>\n <Specified batch class field value><\/em><\/strong><\/td>\n ~BCF$<name of batch class field><\/em><\/strong>:Value~<\/p>\n \n Document level field<\/td>\n <Specified document level field value><\/em><\/strong><\/td>\n ~DLF$<name of index field><\/strong><\/em>:<name of index field><\/strong><\/em>~<\/p>\n \n Document<\/td>\n UUID (Unique identifier for the document)<\/td>\n ~DOC:UUID~<\/td>\n<\/tr>\n \n Document<\/td>\n Type<\/td>\n ~DOC:Type~<\/td>\n<\/tr>\n \n Document<\/td>\n Identifier<\/td>\n ~DOC:Identifier~<\/td>\n<\/tr>\n \n Document<\/td>\n Description<\/td>\n ~DOC:Description~<\/td>\n<\/tr>\n \n Document<\/td>\n Page count in the current document<\/td>\n ~DOC:PageCount~<\/td>\n<\/tr>\n \n System<\/td>\n SharedFolders location<\/td>\n ~SYS:SharedFolderLocation~<\/td>\n<\/tr>\n \n System<\/td>\n Date with specified format<\/td>\n ~SYS:Date(MM-dd-yyyy)~<\/td>\n<\/tr>\n \n System<\/td>\n Server name<\/td>\n ~SYS:ServerName~<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a>XPath Syntax<\/h3>\n
\n