Temenos Digital
R24 AMR | Min(s) read

Card Management

The Card Management Micro App (CardsMA) is used to view all saved debit and credit cards including supplementary cards, activate or deactivate a card, request a replacement for a card, report a lost or stolen card, cancel the usage of a card, request a new PIN for a card, set purchase and withdrawal limits, and add a card to digital wallet.

Prerequisites and Dependencies

Prerequisite/Dependency Details
Required Visualizer Micro App

  • ArrangementsMA

  • CardsMA
Required Fabric Micro App CardManagement
Front Office Enterprise Service Request Microservice
Back Office Enterprise

Mock service
Fabric Engine

Entitlements

Card Management Visualizer App

The Visualizer app contains the required forms and associated artifacts bundled together in the Micro App architecture. The Visualizer App contains the following features:

  • View My Cards
  • Manage Credit Card
  • Credit Card Usage Limits
  • Manage Debit Card
  • Debit Card Usage Limits
  • Card Transaction (Mobile Native)
  • Card Statement (Mobile Native)
  • Travel Plan (This feature is available only in desktop mode)
  • Card Wallet

This feature is applicable to Web Channel and Mobile Native channels of the digital banking application.

Card Management Fabric App

The Fabric app contains the object services and APIs related to the following functionality:

  • View My Cards
  • Manage Credit Card
  • Credit Card Usage Limits
  • Manage Debit Card
  • Debit Card Usage Limits
  • Card Transaction (Mobile Native)
  • Card Statement (Mobile Native)
  • Travel Plan
  • Card Wallet
  • The Fabric app can be deployed on its own.

  • The functionality of the Fabric app is verified using the request/response payloads to ensure that the Fabric app supports standalone in a headless architecture.

RTL Support

The application provides RTL (Right to Left) alignment support for Arabic language for Web Channel and Mobile Native. RTL is a locale-based property which indicates that the text is from Right to Left. The UX elements in the application are designed to enable the formatting of the Arabic content in an RTL layout. Refer to ISO language codes for more information on the most common ISO language codes.

The application framework supports RTL for the Arabic language, which includes:

  • Displaying content with the right to left layout.
  • Supporting Arabic localizations.
  • Displaying data configured in i18n file (static data, master data and more) and dynamic content with some limitations in Arabic.

Constant data based on the information defined in the i18n configuration of the Visualizer application supports RTL layout and displays the data in a right-to-left layout and Arabic. The following data are configured in the i18n file: Static data, Master data, Client side error messages, Fabric side error messages, and Back-end error messages.

  • Static data includes the data used to populate different labels and buttons or displayed as constant information to the user. This data is displayed as configured in the i18n file and does not depend on any other configurations. The application displays the data in a right-to-left layout and in Arabic.

    • Welcome messages (for example - Good morning user)
    • User prompts (for example - Please enter username and password)
    • Informative text (for example - Incorrect username or password)
    • Acknowledgment messages (for example - User has successfully enrolled)

  • Master data includes the information used to set options in menu lists or drop-downs. The master data is in the DBX DB, and the corresponding configuration is maintained in the i18n file. The application displays the data in a right-to-left layout and in Arabic. The master data includes, but is not limited to,

    • Accounts module - Account type (for example - Savings, Checking)
    • Transfers module - Recipient list (for example - name and contact details for different recipients)
    • Generic (common across modules) - Country names (for example - India, China)

  • Client side error messages: The application displays the error messages bound with the client-side in a right-to-left layout and Arabic. Examples of client-side error messages:

    • Dashboard module
      • Cannot read property null of undefined.
      • Container is not defined.
    • Payments module
      • Presentation controller is not defined.
      • Payment amount cannot be greater than the total outstanding amount.

  • The application displays the equivalent client-side mapped messages of every Fabric layer error message to the user in a right-to-left layout and in Arabic. All exceptions or error messages displayed as-is from the middleware and do not have corresponding client-side mappings will not be translated into Arabic. Examples of middleware error messages:

    • Dashboard module
      • Invalid Token: Token expired
      • Session has been timed out.
    • Payments module
      • "dbpErrCode": 12403
      • "dbpErrMsg": "SECURITY EXCEPTION - UNAUTHORIZED ACCESS"

  • The application displays the equivalent client-side mapped messages of every backend-related error message to the user in a right-to-left layout and Arabic. All exceptions or error messages displayed as-is from the backend/Microservices and do not have corresponding client-side mappings will not be translated into Arabic. Examples of backend error messages:

    • Dashboard module
      • errCode 12504: Transaction is denied due to max transaction limit
      • Incorrect username or password.
    • Payments module
      • "dbpErrCode": "15001"
      • "dbpErrMsg": "Backend Integration Failed"

Dynamic data includes data directly retrieved from Microservice or Transact and has no corresponding mapping in the i18n file. The information is subject to change based on specific configurations. Any data entered by the user on the screen also count as dynamic data. The dynamic content includes, but is not limited to,

  • Terms and conditions
  • Alerts and notifications
  • Campaign and marketing data
  • The application displays the dynamic data keyed in by the user in the app as-is. For example, the application displays the information entered in English as in English itself and does not apply any format or language changes to the keyed-in data.
  • The characters and digits across the application will not undergo any formatting or language conversions. All the dates, times, and amounts displayed will remain without conversion.
  • In the current release, the application supports only Arabic (U.A.E) ar- ae as the browser supports this language by default.
  • Before packaging the code, the RTL Support is enabled at the composite app level by default. However, for reference purposes, the following section provides instructions on enabling the RTL support for a new project.

Enable RTL Support for a New Project

  1. Configure Internationalization (i18n) in the Quantum Visualizer app project to enable the RTL support in the application. Follow the steps mentioned in Internationalization and Supporting RTL Languages documentation for details on i18n settings, configuring locales, and completing other configurations to enable RTL support in Quantum Visualizer.
  2. After configuring the locale, go to Project Explorer and select Responsive web/ Desktop> frmLogin.
  3. On the Properties panel, go to the Action tab.
  4. Under General, beside init, click Edit. The Action Editor window appears.
  5. On the left pane, navigate to Function > Add snippet.
  6. Add the following code and click Save.
    kony.application.setApplicationBehaviors({"rtlMirroringInWidgetPropertySetter": true});
  7. On the main menu, click Build > Build and Publish Web.
  8. Modify the language in Web browser settings to Arabic. The RTL alignment is enabled in the application.

 

Copyright © 2020- Temenos Headquarters SA

Contact Us

knowledge@temenos.com

Published on :
Thursday, May 30, 2024 1:12:32 PM IST