List item fields

List item overview

Figure 221 Payment overview item

Each displayable field in the mobile GUI has a default setup that will select values from the payments/envelopes in a hierarchical way: if the first property is empty, it will select the next one instead. All amounts and dates will be formatted according to the user’s regional settings.

• • 1. Data owner code
    2. Ordering customer holder code
    3. Multiple ordering customer accounts

  | | LargeField2 (e.g. ITP1) | 1. Internal classification type | | SmallField1 (e.g. REF: HWC/PAYM0001) | 1. Counterparty reference | | SmallField2 (e.g. CHRIS P. BACON) | 1. Counterparty name | 1. Number of payments | | SmallField3 (e.g. MainCompanyAccount) | 1.Ordering customer code | 1. Ordering customer code (when unique) | | AmountField | 1. Instructed amount + instructed currency | | DateField | 1. Cut-off time | | SignatureField | 1. Given signatures (green) + required signatures (grey) | | PaymentTypeField | 1. Single note icon | 1. Multiple notes icon |

Table 6 Default values for each field.

Customizing list item fields

The administrator can change which payment/envelope properties are displayed when the defaults are unclear or unused. This can be done by setting the xpaths for the desired values in the “customfields.properties” file, found in “%PROJECT%/trax/trax-config/src/main/config-mobile”.

The fields can be altered individually and separately for payments and envelopes. This allows for a maximum of 16 custom property fields to be set.

For each property field, the administrator can select one or more (in a comma separated list) xpaths. In case of multiple xpaths, AvantGard Trax will try to get a value from the first one, and fall back to the next one until a value is returned.

In case no value is found, the administrator can select a translation to be shown in the field instead with the “translationKey” key. When setting up this translation in trax, note that the translation will be taken from the GUI translations. This means the translation must be prefixed by “gui.”, but this prefix must not be set in the “customFields.properties” file.

As a safety net in case the translation is not found, a hard-coded translation must also be set with the “translation” key.

When a field is not desired, it can also be removed by setting the “disabled” key to “true”. This will display nothing in the mobile GUI.

The amount field, date field, signature field and payment type field cannot be customized. Only largeField 1-2 and smallField 1-3 support this customization feature.

Below is an example configuration for setting the “LargeField1” field for envelopes to a custom value (for more information, see the explanation in the “customFields.properties” itself):

list.Payment.Envelope.largeField1.disabled=falselist.Payment.Envelope.largeField1.xpath=orderingCustomerAccount/codelist.Payment.Envelope.largeField1.translationKey=mobile.noDatalist.Payment.Envelope.largeField1.translation=No ordering cust code found!