Creating barcodes with transactional data

You can submit a barcode containing transactional data using schema paths (called XPATHs). Expere identifies these schema paths that start with a /txn prefix.

To enter a barcode pattern: enter optionally standard Expere reserved variables, BRCD variables, static text, or schema points.

Note: A sample barcode pattern could resemble the following: Page %Page% of %totalpages% Loan Number %/txn/Notes/Note/LoanIdentifier%; Expere would translate this to display as "Page 1 of 1 Loan Number 123432"

Barcode Types (Fonts) and Patterns > Barcode Components (Patterns) contains detailed information on entering variables and the specific syntax required for the barcode pattern.

Common schema paths

Below are some common schema paths used in a transactional barcode:

  • Borrower: %/Txn/Borrowers/Borrower[#]/FirstName% %/Txn/Borrowers/Borrower[#]/LastName%
  • Loan Number: /Txn/Notes/Note/LoanIdentifier
  • Account Type (Checking; Savings): /Txn/Deposit/Accounts/Account/AccountType
  • Account Identifier: /Txn/Deposit/Accounts/Account/AccountIdentifier
  • Purpose Type (Consumer; Commercial; Agricultural): /Txn/Notes/Note/PurposeType

Wildcards for multiple instancing

Expere supports the use of a # symbol to iterate through a document and ensure account or party-specific data, per document, appears correctly in the barcode. For example, in instances where multiple borrowers exist, the correct borrower name will appear on the appropriate document.

Note: For example, a typical barcode pattern that would contain the # symbol: Txn/Borrowers/Borrower[#]/BorrowerName). The "#" symbol should be present on the element being indexed.

Troubleshooting schema path errors

Transactions can fail if the schema path (XPATH) contains incorrect formatting, syntax, or value. When reviewing log files (e.g. ExpereServices.log), search for either of the following error messages:

  • Unable to extract value for xpath
  • Invalid xpath expression