Transact

⌘K
  1. Home
  2. Transact
  3. Developer Documentation
  4. Scripting Resources
  5. Display Error Cause for Default Scripts

Display Error Cause for Default Scripts

Versions: 4.5.0.0 and newer

In Transact versions prior to 4.5.0.0, default scripts did not include information on the exceptions thrown. If any default script went into error, the batch status reflected the “Error” but the “Error Cause” was not populated on the Batch Instance Management screen.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Worderror4.png

Default scripts include error comments.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordscript1.png

The Transact administrator can also view script error details in the dcma-all and catalina logs in the Application folder.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Worddcma.png

The Batch Execution Details on the Batch Instance Management screen will include the error message if the batch goes into error state at any level of the batch processing workflow.

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Worderror3-1.png

Error comments are included in all default scripts except ScriptPageProcessing and ScriptValidation. Below is the list of error messages found in the Ephesoft Transact default scripts:

Ephesoft Transact Default Script Error Messages Scripts
“Document doesn’t exist.” ScriptAddNewTable
“Input document is null.” ScriptAddNewTable

ScriptAutomaticValidation

ScriptDocumentAssembler

ScriptExport

ScriptExtraction

ScriptFieldValueChange

ScriptFunctionKey

ScriptNewTableRowInsert

ScriptTableCellValueChange

“Unable to find the local folder path in batch xml file.” ScriptAddNewTable

ScriptAutomaticValidation

ScriptDocumentAssembler

ScriptExport

ScriptExtraction

ScriptFieldValueChange

ScriptFunctionKey

ScriptNewTableRowInsert

ScriptTableCellValueChange

“Unable to find the batch instance ID in batch xml file.” ScriptAddNewTable

ScriptAutomaticValidation

ScriptDocumentAssembler

ScriptExport

ScriptExtraction

ScriptFieldValueChange

ScriptFunctionKey

ScriptNewTableRowInsert

ScriptTableCellValueChange

“Unable to read the zip switch value. Taking default value as true. Exception thrown is:” ScriptAddNewTable

ScriptAutomaticValidation

ScriptDocumentAssembler

ScriptExport

ScriptExtraction

ScriptFieldValueChange

ScriptFunctionKey

ScriptNewTableRowInsert

ScriptTableCellValueChange

“************* Error occurred in scripts.” ScriptAddNewTable

ScriptAutomaticValidation

ScriptDocumentAssembler

ScriptExport

ScriptExtraction

ScriptFieldValueChange

ScriptFunctionKey

ScriptNewTableRowInsert

ScriptPageProcessing

ScriptTableCellValueChange

ScriptValidation

 

You can find all default scripts in the Batch Class folder created at the time of Batch Class configuration (UNC folder):

C:UsersEphesoftAppDataLocalMicrosoftWindowsINetCacheContent.Wordscripts.png

It is recommended to leave error messages in default scripts unchanged. If required, you can customize the entire script and provide any error message as needed.