{"id":31838,"date":"2015-03-09T12:51:19","date_gmt":"2015-03-09T20:51:19","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/2019-1-2\/moduleplugin-configuration\/extraction-module\/scripting-plugin-2\/"},"modified":"2020-11-24T09:52:51","modified_gmt":"2020-11-24T16:52:51","slug":"scripting-plugin-2","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/features-and-functions\/administrator\/moduleplugin-configuration\/extraction-module\/scripting-plugin-2\/","title":{"rendered":"Scripting Plugin"},"content":{"rendered":"
Available<\/b>: on-premises, cloud<\/p>\nOverview<\/h1>\n
This plug-in reads the batch\u2019s batch.xml file and works upon the given document as per the scripts given in the scripts folder. All the scripts are placed inside \u201c{SharedFolder}batch class folder (ex:-BC1)scripts<\/strong>\u201d.<\/p>\n For any script there are two ways to write it, either it could be written in \u201cIScript\u201d or \u201cJDOM\u201d. For running any type of script user needs to place the script inside the \u201cscripts\u201d folder inside batch class folder for the respective batch class on which the script needs to be run.<\/p>\n Following are the configurable properties available for the Fuzzy Db plug-in in the dcma-scripting-plugin properties file in META_INFdcma-scripting-plugin:<\/p>\n This is shown in the screen shot given below:<\/p>\n <\/p>\n META-INF\/dcma-scripting-plugin\/dcma-scripting-plugin.properties file. Also give the parser type for the script to run.<\/p>\n There is only one dependency of this plug-in. The \u201cimport-batch-folder\u201d plug-in needs to be executed before \u201cscripting-plugin\u201d to generate the files required for processing of \u201cscripting-plugin\u201d. If the batch goes into \u201cError\u201d state then proper logs will be generated in log file kept at {Application}dcma-all.log.<\/p>\n NOTE:<\/strong> There are some scripts placed in the \u201cscripts\u201d folder which are required for the system.<\/p>\n Following are few common error messages seen due to mal-functioning of the plugin:<\/p>\n <\/p>\n","protected":false},"featured_media":0,"parent":31802,"menu_order":10,"comment_status":"closed","ping_status":"open","template":"","doc_tag":[],"yoast_head":"\nConfiguration<\/h2>\n
Configurable properties<\/h3>\n
\n\n
\n Configurable property<\/strong><\/td>\n Type of value<\/strong><\/td>\n Value options<\/strong><\/td>\n Description<\/strong><\/td>\n<\/tr>\n \n Script Parser Type<\/strong><\/td>\n String<\/td>\n \n \n
\n
This value defines the type of scripts that will run. There could be two types of scripts that could be run i.e. JDOM and ISCRIPT. For script to run in JDOM user has to give the parser type as \u201cjdom\u201d. For script to run in ISCRIPT user has to give the value as \u201ciscript\u201d.Default jdom.<\/td>\n<\/tr>\n \n Script Switch<\/strong><\/td>\n String<\/td>\n \n \n
\n
This switch is used to set the execution of scripts on or off. If this switch is off then no script will run otherwise scripts will run.Default ON.<\/td>\n<\/tr>\n \n Script<\/strong> Class<\/strong> Name<\/strong><\/td>\n String<\/td>\n NA<\/td>\n This tells the user as to what is the name of application level script file.<\/td>\n<\/tr>\n \n Script<\/strong> Folder<\/strong> Name<\/strong><\/td>\n String<\/td>\n NA<\/td>\n This tells the user about the name of folder where application level script is lying.<\/td>\n<\/tr>\n \n A<\/strong>pplication<\/strong> Level<\/strong> Script <\/strong>cron<\/strong> Expression<\/strong><\/td>\n String<\/td>\n NA<\/td>\n This tells the user about the cron job expression.<\/td>\n<\/tr>\n \n Script<\/strong> Optimizer<\/strong> Switch<\/strong><\/td>\n String<\/td>\n \n \n
\n
This property is used to implement the optimization of scripts.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Steps for configuring the plugin<\/h3>\n
\n
Steps of execution<\/h2>\n
\n
\n
Dependency<\/h2>\n
Troubleshooting<\/h2>\n
\n\n
\n S no.<\/strong><\/td>\n Error message<\/strong><\/td>\n Possible root cause<\/strong><\/td>\n<\/tr>\n \n 1<\/td>\n Script having invalid parser type or invalid arguments. Throwing workflow in error<\/td>\n This occurs when the entered parser type and the present script types does not match for ex. If parser given is dom and user puts in an iscript script then this error occurs.<\/td>\n<\/tr>\n \n 2<\/td>\n Script error out. Throwing workflow in error.<\/td>\n This happens when the custom script that has been put error out and needs to be corrected.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n