Temenos Digital Origination FAQs

App Workflow

1. Where is core integration managed?

   The core integration is managed by using the core systems such as Temenos Transact. For more information on the core integration, refer to Temenos Digital Origination Architecture.

2. How are the app workflows managed?

   The app workflows are managed by using the RedHat Process Automation Manager. For more information, refer to Temenos DigitalOrigination Architecture.

3. How is the application related data managed?

   The application data is managed by using the Origination Data Microservice (ODMS) until the application is approved. Post-approval, the data is stored in the core systems. For more information, refer to Temenos Digital Origination Architecture.

4. Is it possible to have different approval workflows based on the type of product?

   No. The approval workflow is the same for all products and is defined at the application level.

5. Can a bank change the workflow or the UI for Temenos DigitalOrigination?

   Yes, a bank can change the workflow or UI for Temenos DigitalOrigination. For example, a bank can:

   • Choose to call the Origination Data Microservice (ODMS). However, choosing not to call the ODMS is not recommended.
   • Choose to call KYC or its own rules.
   • Call its own analytics product instead of Journey Analytics.
   • Make a static navigation change such as calling Form A instead of Form B.

   All these changes are country-specific features(L2 features) or customer-specific features (L3 features) that can be delivered to customers as customizations and are not supported as part of a configuration framework.

6. What components of Temenos DigitalOrigination are customizable? Provide the applicable docs.

   Refer to Extensibility documentation.

7. Does the Temenos DigitalOrigination app work on Mobile and Tablet devices?

   Temenos DigitalOrigination is a responsive web app that works on the Mobile and Tablet devices by using breakpoints. No native app is available at this moment.

Identity Verification

1. How are the questions formulated for identity verification?

   The identity verification questions are formulated by using the IDology service provider. For more information on generating and answering the questions for demo purpose, refer to ExpectID Sandbox Guide and IDology PA TestCase.

2. Does the Temenos DigitalOrigination app perform fraud checks?

   Yes. The standard app contains an integration with IDology (a service provider from the USA) that identifies potential risks and provides recommendations to reduce the risks. However, you can choose a vendor based on a prospect or customer’s requirements which might include Screening, FCM, ID&V, and ID&A.

   This will be delivered to customers as a customer-specific feature (L3 feature) or a country-specific feature (L2 feature) on top of the core framework, which also includes the configuration of decision rules.

3. Does ID verification with IDology work across geographies?

   No, it is applicable only to the US, Canada, and Mexico.

   However, you can choose a vendor based on the customer’s requirements. This will be delivered to customers as a customer-specific feature (L3 feature) or a country-specific feature (L2 feature) on top of the core framework, which also includes the configuration of decision rules.

4. How do you ensure that the Identity verification vendor supports all countries? Is there a catalogue for the same?

   There is no L1 (core) feature that supports all countries. However, for the other regions, a local identity verification vendor can be implemented as an L2 (country-specific) or an L3 (customer-specific) feature to support the regional requirements.

Microservices

1. Can the Marketing Catalogue Microservice return the applicable images of the banking products in the Product Selection module?

   No, the Marketing Catalogue Microservice does not return images of the banking products. It only provides information about the product ID and description.

Rules

1. How can a bank map the DMN Rules decision to the application status?

   The DMN Rules is hosted as a set of services on Red Hat, and Quantum Fabric Integration services will be used to communicate to the Red Hat DMN services.

2. If you use DMN Rules, where can you find the audit log related to every decision that is made?

   The Temenos DigitalOrigination Audit Log does not support server-side calls. However, Quantum Fabric contains its own logs that can be used for DMN Rules as well.

3. As there are rules in Quantum Fabric, Transact, and DMN Rules, is there a common strategy as these require licenses too?

   Transact is a Core, and, as a core-agnostic solution, Temenos Digitalhas no control over it. Regarding Quantum Fabric or DMN Rules, there are two different types of rules and will continue to exist.

4. Are Orchestration services used for communication between Quantum Fabric and DMN rules?

   Currently, Integration Services in Quantum Fabric are used for communication between Quantum Fabric and DMN rules.

5. Is DMN Rules a part of the Temenos Digitallicense?

   DMN Rules requires a license, but it is not a part of the Temenos Digitallicense. The license for DMN Rules must be taken separately.

6. Are the rules stored in any database?

   No, the rules are not stored in the database.

Configurations

1. Can you make modifications to certain fields in the Address and Identification details based on the region?

   Yes, Spotlight offers a configuration to enable the sequence of address based on the US address format or the generic address format. For more information on the configurations, refer to Configurations in Spotlight.

Origination Data Microservice

1. Does ODMS support versioning?

   The ODMS contains versioning implemented within the Entity Definition and Entity Items for performance and data integrity.

2. Can I purge data in ODMS?

   Yes, purging data is possible in ODMS. The duration is in days and it is mentioned in purgeDuration field within the Entity Definition.

Language Support

1. Does Quantum Visualizer support the multi-language concept.

   Yes, Quantum Visualizer provides multi-language support.

2. Are Arabic and French-based forms supported?

   Arabic and French are not supported out of the box.

Miscellaneous

1. Why are the options in the Footer not working?

   Since the Footer is a country-specific feature (L2 feature) or a customer-specific feature (L3 feature), it can be delivered to customers as customization and is not supported out of the box. The footer in the Origination app is a standard reference menu that contains placeholders for content, call-to-action options, and icons.

2. How is the Scan ID module used?

   In case of mobile devices, you can scan the documents by using the Scan ID module, followed by the Selfie verification. Once authenticated, your details are auto-filled.

3. When does the status of a customer change from Prospect to Active?

   The status of a customer changes from Prospect to Active after the application is approved.

4. Can a main applicant share the app link with a co-applicant to provide the details?

   No, a co-applicant cannot provide the details directly.

5. If I am an existing customer, is it mandatory to use the Temenos DigitalOrigination app to access digital channels?

   No, it is not mandatory. You can directly enroll yourself from the Digital Banking app.

6. If I am an existing customer, is it mandatory to use the Temenos DigitalOrigination app to create a new account?

   Yes. As an existing customer, the Temenos DigitalOrigination app enables you to login with your credentials. You can login and then create a new account.

7. If I am an existing customer, can I register multiple times by using the Temenos DigitalOrigination app?

   Yes, you can register more than once. However, you can restrict the possible number of registrations by using extensibility.

8. What is the need of the eligibility criteria module?

   Some countries have the concept of a Credit Union (CU), which offers special conditions to their members. To become a member of a CU, the applicant must fit specific criteria that is defined at the Eligibility screen. note that you can show or hide this section by using the configurations in Spotlight.

9. Explain the roles of components such as Temenos Transact, Origination Data Microservice
   1. Temenos Transact handles the core responsibilities and provides some part of the master data and the final data for Party and Accounts.

      A Microservice is intrinsically dependent on Transact.

   2. ODMS is responsible for data storage and data management.

   For more information about Temenos DigitalOrigination components, refer to Temenos DigitalOrigination Architecture.