Transact Explorer

(R23-AMR Build)

Information in this document is subject to

change without notice.
No part of this document may be reproduced
or transmitted in any form or by any means, for
any purpose, without the express written
permission of TEMENOS HEADQUARTERS
SA.
© 2022 Temenos Headquarters SA -
all rights reserved.
Transact Explorer

Table of Contents
Document History ............................................................................................................................... 3
Introduction ........................................................................................................................................ 4
Artefacts............................................................................................................................. ...........................4
Pre-Requisite ..................................................................................................................................... 4
Launch Transact Explorer ................................................................................................................... 4
Login- Transact Explorer ..................................................................................................................... 5
Logout- Transact Explorer ................................................................................................................... 6
Defect dashboard URL ........................................................................................................................ 7
Transact Explorer FAQ ....................................................................................................................... 8

2
Transact Explorer

Document History

Author Version Date

Santhika M 202302 28 FEB 2023

Comments:

3
Transact Explorer

Introduction
 Transact Explorer developed with Angular Framework using web components and UUX under the hood.
 Light-weight deployment and scalable architecture.
 Readymade UI components for faster and customized screen development.
 Supports both auto-generated and hand-crafted screens

Artefacts
 UI artefact - transact-explorer-wa.war
 API artefact - tb-server.war

Components
 Login Component
 Menu Component
 Query Component (Enquiry, Chart & Fast-path Enquiry)
 Screen Component (Application & Version)
 Composite Component (COS & Tabbed screen)
 Performance Component
 Web Component wrapper components for all standalone web application components.

Pre-Requisite
 202212 or above demo system MB should be downloaded and installed
 DB and application server should be up and running

Launch Transact Explorer

Launch Transact Explorer URL in browser http://<MachineIP>:<Application Server Port number>/transact-

explorer-wa

Eg: IP- http://localhost:9089/transact-explorer-wa

Shortcut Menu can be used to launch transact explorer

4
Transact Explorer

Login- Transact Explorer

Enter valid Username and Password and Click Login (Refer to Password doc in Demo guides)

User Able to login successfully.

5
Transact Explorer

Logout- Transact Explorer

1. Click on Logout Button

6
Transact Explorer

2. Click Yes to Logout

3. User Logged out successfully.

Defect dashboard URL

This dashboard has the list of all defects raised as a part of TE with the current status.
Transact Explorer Web Application - Master Dashboard - JIRA PROD (temenos.com)

7
Transact Explorer

Transact Explorer FAQ

What is it?
The latest Browser for Transact Version, Enquiry & COS.
When will it be ready / released?
AMR23.
Is it mandatory?
It is mandatory for new clients taking AMR23.
What about upgrading clients?
It is optional for clients upgrading to AMR23. The have the right to continue using their current Browser
(UXPB or legacy).
Can it be backported?
We are NOT supporting this option right now despite it being technically possible. We do have a beta
client who is working with us to check the feasibility. Wait for further announcements.
Can I try it out now? Where can I get it?
Yes. It’s part of the 2301 build. Take a standard download from UTP, spin up the model bank and
enter: http://localhost:9089/transact-explorer-wa/#/login
Does it work?
All 411 UXP Browser automated tests have been converted to test Transact Explorer. This includes
platform test and the model bank scenario tests. The vertical development teams have been using it as
part of their daily work. BSG have been testing it. Based on this I am confident we will be ready for AMR.
Why is Temenos doing this?
Transact Explorer introduces a much simpler architecture which means it runs faster on less
resources. This means lower cost on the Cloud.
The second benefit is ease of installation and management. The UXP Browser has been tricky to set up
for some clients.
Is new training needed?
No. If you can use UXP Browser or Legacy Browser you can use Transact Explorer.
Is this a 100% functional replacement for UXP Browser/Legacy Browser?
No. There may be certain arcane features going back to the Legacy Browser that we will not agree to
support. That said, ALL of the UXP Browser tests are now running against Transact Explorer.
What issues might I face?
Apart from not supporting arcane functions, it’s worth pointing out Transact Explorer has a newly designed
screen layout engine.
This may lead to familiar screen’s fields being laid out in a new way. Most of the time the feedback is that
it is a great improvement. Occasionally there is a genuine objection; mostly concerning composite
screens. We are constantly taking on feedback and improving the layout engine.
Ultimately composite screens will be replaced by designed user agents.
What is the future of UXP Browser?
UXP Browser will no longer be an option for new clients from AMR23. There are many clients who have
UXP Browser live, and as such they will receive great gsupport. That said, there will no longer be any
strategic investment or roadmap. Any enhancements will either be funded by the clients or, if a case can
be made, funded by Product if the improvement warrants it.
What are the physical artefacts and how do they work?
Today the Transact Explorer is deployed as 2 WAR files: tb-server.war & transact-explorer-wa.war. tb-
server provides the APIs the manage connectivity with Transact. These APIs are used by the transact-
explorer-wa to render the screens using Javascript.
It reuses all the Transact code that underpins the legacy browser.

8
Transact Explorer

Can it be run in parallel with UXP Browser / Legacy Browser?

Yes.
Does it support single sign on?
Yes. It has been tested with Key Cloak.
Does it support user externalisation?
User externalization is under development. What we support in TE now is to link Keycloak (SSO) users
with Transact users.
Does it support XACML?
Yes. This is configured in the same way as legacy browser.
How does it relate to the proposed user agents and ‘Temenos Explorer’ (ex
Temenos Middle Office)?
User agents are pixel perfect hand coded screens written in UUX (or Visualiser for mobile). Transact
Explorer works only with Transact using COS, Version and Enquiry. Temenos Explorer is the new middle
office staff single pane of glass used to house the new user agents AND Transact Explorer.
Transact Explorer has been written in a way where it can be seamlessly embedded within a user agent.
Why do we still need a Browser for Transact if we are moving to user agents?
The are 20000 versions, enquiries, and COS in Transact. It’s not economical to hand build user agent
equivalents for them all. User agents are needed for key dashboards, sales demos and high traffic
screens. The Browser model is still a highly productive way of producing simple input and report screen.
As a business vertical what should I do to make business vertical compatible
with Transact Explorer?
There should be no work involved other than testing.
For new feature functions being built is there any additional effort we need
to park in from a Transact Explorer perspective?
No.
Is there any change to Transact L2 behaviour in Transact Explorer?
No.
Is there any change to Transact L3 behaviour in Transact Explorer ?
It's identical to Legacy Browser / simpler than UXPB.
Can clients do same extensions in Transact Explorer layer like how they were
doing in the UXPB layer?
No. UXPB Browser allowed clients to create extensions using the UXP IDE dev platform and also had its
own Javascript mechanism.
Are we changing our user guide and mode workflow document to reflect
Transact Explorer screens?
This task is on the backlog.
Will pre-sales no longer use UXPB from R23 ?
Yes. That is the plan.
What happens to in-flight projects that are now implementing but will
upgrade to R23 for going live?
Upgrading clients have the choice to stick with their current Browser or use Transact Explorer.
How are the client communications being managed ? Do verticals need to
do anything?

9
Transact Explorer

TBA
Is there a roadmap for Transact Explorer in terms of improving generic
screens with more ‘patterns’ so that we avoid writing additional user agents?
No. But this is a reasonable suggestion. A lot work has already gone into this in order to support COS.

10