Common

1. <Notifications openAtStartup="false">

2. <View title="Transaction Data Signing">

3. ...

4. </View>

5. <NotificationRegistration />

6. <NotificationsList title="Select notification">

7. <TransactionDataSigningAction id="notificationTds_1".../>

8. <TransactionDataSigningAction id="notificationTds_1".../>

9. </NotificationsList>

10. </Notifications>

Functional customization

• Notifications: This element is used to configure common notification settings.

  • openAtStartup: Can be used to show the pending transaction directly at the startup of the application. This attribute is optional. The default value is false.

• NotificationRegistration: This element is used to configure the notification registration (see Notification registration). It is used to register the VASCO Notification Identifier on the server-side.

• NotificationsList: The NotificationsList element can contain one or multiple TransactionDataSigningAction elements. It is used for notifying the end user about pending transactions that are waiting for validation on the server-side. Each TransactionDataSigningAction id attribute is included in the push notification coming from the server-side. It is used to launch a specific notification TDS action.

  • title: This is the title of the notifications list popup. For more information, see Notifications list popup.

• NotificationsList > TransactionDataSigningAction: For more information, see Transaction Data Signing.

• NotificationsList > SecureChannelAction: For more information, see Secure Channel action.

The NotificationList element must contain TransactionDataSigningAction or SecureChannelAction. SecureChannelAction elements will be used only to manage push-and-login or push-and-sign operations using DIGIPASS Gateway.

Graphical customization

• Notifications > View: This element is used to configure the Mobile Authenticator Studio notification view.

• Notifications > View > Labels > Label:

  • id="GetTDSListWaitMessage": This is the wait message which is displayed while retrieving the transaction list.

  • id="TransactionValidationWaitMessage": This is the wait message which is displayed while internally validating the transaction.

  • id="TransactionRejectionWaitMessage": This is the wait message which is displayed while internally rejecting the transaction.

  • id="ReceivedHostCode": This is the label for the return host code.

  • id="TransactionAcceptRejectMessage": This is the message which is displayed to the user for transaction validation.

  • id="DetailsWaitMessage": This is the wait message which is displayed while downloading the transaction details.

  • id="RejectionWaitMessage": This is the wait message which is displayed while the rejection message is being sent to the server.

• Notifications > View > Dynamics > Dynamic:

  • id="TDSList": Can be used to customize the rendering of the transaction list.

  • id="TDSDetails": Can be used to customize the rendering of the TDS details.

  • id="Title": Can be used to customize the rendering of the transaction title.

  • id="Keys": Can be used to customize the rendering of the transaction keys.

  • id="Values": Can be used to customize the rendering of the transaction values.

  • id="Freetext": Can be used to customize the rendering of the transaction freetext.

• Notifications > View > Buttons > Button:

  • id="Accept": This is the button to accept a login/transaction. The default value is Accept.

  • id="Deny": This is the button to reject a login/transaction. The default value is Reject .

• Notifications > View > Errors > Error:

  • id="TDSListEmpty": No transaction pending.

  • id="TDSInvalidDataFields": The data fields contained in the transaction are invalid.

  • id="TDSInvalidDataFieldsNumber": The number of data fields in the transaction is invalid.