Servicing Micro Apps Overview
Micro Apps are applications with specific functionality which are fast and efficient than monolithic applications. While traditional monolithic apps contain a complex suite of functionality, including front-end and back-end operations leading to loading or build-time issues, Micro Apps are smaller and easily manageable resulting in enhanced loading and build times with targeted functionality.
Each Micro App is responsible for achieving specified business goals and has its own code base that can be developed, tested, and deployed separately.
- Front-end Visualizer Micro App includes a collection of forms and a business logic based on its functionality.
- Fabric Micro App is a collection of object services that cover all associated experience APIs and integration APIs.
Key Benefits
- Productivity: A separate code base that can be developed, tested, and deployed independently.
- Modularization: Functionality is modularized to fulfill specific business goals independently.
- Release: Only Micro Apps with changes can be released.
- Composite Structure: This will give full experience to the end-user.
INFORMATION
- Use Micro Apps in Quantum Visualizer: In Temenos Digital, different modules in various applications are modified into Micro Apps. These Micro Apps can be Visualizer Apps or Fabric apps. While a Visualizer app does not necessarily have a corresponding Fabric app, all Fabric apps have a corresponding Visualizer app. For information on how to use Micro Apps in Quantum Visualizer, refer Micro Apps documentation.
- Components Documentation: The Micro Apps may contain components. The components are of two types - with and without contracts. Developers can modify only the components that are with contracts. Information on how to modify the individual component is available in Temenos Digital Components documentation.
As a part of accessibility, the labels are intentionally retained to ensure visibility. For example, when the tab is on Skip to Main Content, pressing enter will directly navigate to the main content bypassing the labels in the header.
Micro Apps List
The following table provides information on the Micro Apps.
- For a quick view of all Visualizer and Fabric Micro Apps, click here.
- For details on service/feature catalog servicing packs (BOM details) with supporting information, click here.
- For Temenos Digital servicing Micro Apps, there will be no Microservices support from the 2024.01.
- By default, the Temenos Digital servicing Micro Apps supports Single Entity.
Visualizer Micro Apps | Micro App Name |
Prerequisites Visualizer Micro Apps |
Prerequisites Fabric Micro Apps |
---|---|---|---|
Resources | ResourcesMA | Not applicable | Not applicable |
Commons | CommonsMA | Not applicable | Not applicable |
Authentication | AuthenticationMA |
CommonsMA, ResourcesMA, AuthenticationMA, AboutUsMA, HomepageMA, ManageProfileMA |
Authentication, ContentManagement, Arrangements, ExternalUserManagement, ServiceRequestAPI, Approvals |
Self Service Enrollment | SelfServiceEnrolmentMA |
SelfServiceEnrolmentMA |
-- |
Servicing Home Page | HomepageMA |
CommonsMA, ResourcesMA, AuthenticationMA, AboutUsMA, HomepageMA, ManageProfileMA |
Authentication, ContentManagement, Arrangements, ExternalUserManagement, ServiceRequestAPI, Approvals |
Arrangements | ArrangementsMA |
ArrangementsMA, ManageArrangementsMA |
Arrangements, ExternalUserManagement |
Manage Arrangements | ManageArrangementsMA | ArrangementsMA, ManageArrangementsMA | Arrangements, ExternalUserManagement |
Account Aggregation | AccAggregationMA | ArrangementsMA, AccAggregationMA | AccountAggregation |
Savings Pot | SavingsPotMA | ArrangementsMA, SavingsPotMA | SavingsPot |
Transfers | TransfersMA | TransfersMA | Payments, TransactionLimitsEngine |
Wire Transfer | WireTransferMA | WireTransferMA | Payments, TransactionLimitsEngine |
Bulk Payments | BulkPaymentsMA | ApprovalRequestMA, TransfersMA, BulkPaymentsMA | Payments, TransactionLimitsEngine, BulkPayments |
Trade Finance | TradeFinanceMA | TradeFinanceMA | TradeFinance |
Lending Dashboard | LendingDashboardMA | LendingDashboardMA | Lending Dashboard |
Bill Pay | BillPayMA | BillPayMA | Payments, TransactionLimitsEngine |
ACH | ACHMA | ACHMA | ACH |
Self Service External User Admin | UserManagementMA | UserManagementMA | -- |
Approval Matrix | ApprovalMatrixMA | ApprovalRequestMA, ApprovalMatrixMA | Approvals |
Approvals and Requests | ApprovalRequestMA | ApprovalRequestMA, ApprovalMatrixMA | Approvals |
Card Management | CardsMA | ArrangementsMA, CardsMA | CardManagement |
Finance Management | FinanceManagementMA | FinanceManagementMA | FinanceManagement |
Alerts Management | AlertSettingsMA | AlertSettingsMA | AlertsManagement, DbpEventManager |
Secure Message | SecureMessageMA | SecureMessageMA | SecureMessage |
Manage Profile | ManageProfileMA | CommonsMA, ResourcesMA, AuthenticationMA, AboutUsMA, HomepageMA, ManageProfileMA | Authentication, ContentManagement, Arrangements, ExternalUserManagement, ServiceRequestAPI, Approvals |
Consent Management | ConsentMgmtMA | ConsentMgmtMA | ConsentManagement |
About Us | AboutUsMA | CommonsMA, ResourcesMA, AuthenticationMA, AboutUsMA, HomepageMA, ManageProfileMA | Authentication, ContentManagement, Arrangements, ExternalUserManagement, ServiceRequestAPI, Approvals |
Foreign Exchange Rates | ForeignExchangeMA | ForeignExchangeMA | ForeignExchange |
Campaign | CampaignMA | CampaignMA | Campaign |
WealthOrder | WealthOrderMA | PortfolioManagementMA, WealthOrderMA | Common: Authentication and Arrangements Wealth: Portfolio Management and Order Management |
Portfolio Management | PortfolioManagementMA | PortfolioManagementMA, WealthOrderMA | Common: Authentication and Arrangements Wealth: Portfolio Management and Order Management |
Smart Banking Advisor | SmartBankingAdvisorMA | SBAdvisoryMA, HomepageMA, ArrangementsMA, AuthenticationMA, AboutUsMA, CampaignMA, UserManagementMA, ResourcesMA, CommonMA | SmartBankingAdvisor |
Quick Links Availability
The quick links are displayed at the right of the screen. The user has an option to navigate to any of the available links. These quick links are only visible in desktop mode(>1024 pixels) and hidden in tablet(<1025 pixels) and mobile screens.
Multi Entity Support
Multi Entity Support: Customers can view the dashboard, perform transfers, or view any request summary and submit requests against the entity associated with the customer during login. The feature is enhanced with Experience APIs to retrieve and post based on the Entity ID of the signed-in user.
- The Entity ID selected by the signed-in user flows through the application through the respective Experience API.
- For all fetch (GET) API calls, the system retrieves the results based on the Entity ID of the signed-in user.
- For all add/update/delete calls, the system passes and posts requests against the Entity ID of the signed-in user.
The feature supports the following modules:
Authentication | Dashboard | Account Overview |
Credit Card overview | Cheque Management | Card Management |
Statements | Dispute Transactions | Service Requests |
PFM | Savings Pot | Account Settings |
Sign In Settings | Profile Settings | Consent Management |
Unified Transfers | Manage Transfers | Manage Beneficiaries |
Bulk Payments | Bill Payments | Foreign Exchange |
Portfolio Management | WealthOrder | Approval Matrix |
RTL Support
The application supports Right to Left (RTL) alignment support for Arabic languages in the following Micro Apps:
Authentication | Homepage | Arrangements |
Cards | FinanceManagement | AccAggregation |
ForeignExchange | BulkPayments | BillPay |
Transfers | ConsentMgmt | ManageArrangements |
AboutUs | Campaign | ManageProfile |
SecureMessage | AlertSettings | ApprovalMatrix |
ApprovalRequest | UserManagement | SelfServiceEnrolment |
Portfolio Management | WealthOrder |
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
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
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
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.
- Dashboard module
-
Middleware (Fabric side) error message
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"
- Dashboard module
-
Back-end error messages
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"
- Dashboard module
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
- 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.
- After configuring the locale, go to Project Explorer and select Responsive web/ Desktop> frmLogin.
- On the Properties panel, go to the Action tab.
- Under General, beside init, click Edit. The Action Editor window appears.
- On the left pane, navigate to Function > Add snippet.
- Add the following code and click Save.
kony.application.setApplicationBehaviors({"rtlMirroringInWidgetPropertySetter": true}); - On the main menu, click Build > Build and Publish Web.
- Modify the language in Web browser settings to Arabic. The RTL alignment is enabled in the application.
For information on the Revision History of this guide, click here.
Web Content Accessibility Guidelines (WCAG)
The Temenos Digital Application is a WCAG Complaint. All the Visualizer Applications supporting the Web Channel and Mobile native screens are WCAG compliant and are ranked as A and AA.
What is WCAG?
Web Content Accessibility Guidelines (WCAG) are globally adopted standards that provide technical instructions and success criteria for website owners, designers, and developers. This guidelines aim to make websites accessible to people with various disabilities, including sensory, intellectual, learning, and physical disabilities.
The following Micro Apps are covered as a part of this exercise.
About us | Cards MA | manage Profile MA |
Account Sweep MA | Consent Management MA | Profile management MA |
Alert Settings MA | Finance Management MA | Secure Messages MA |
Arrangements MA | Homepage MA | Self Service Enrollment MA |
Authentication MA | manage Arrangements MA | Transfers MA |
Bill Pay MA |
In this topic