[go: up one dir, main page]

0% found this document useful (0 votes)
6 views35 pages

TEMENOS WORKBENCH - 2

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1/ 35

TEMENOS WORKBENCH

PRESENTED BY: -
VIJAYALAKSHMI S
CREATION OF LOCAL TABLE
FOR SINGLE VALUE FIELD
CREATION OF LOCAL
TABLE
 Go to Transact from
homepage -> Click on User
Field

 Give the mandatory field and


click on the save.

 Once we give Min Char field,


it will become Mandatory
field for that respective
application.
CREATION OF LOCAL REFERENCE TABLE

 To attach it to the respective


application.

 Go to Data Model -> User Table


Reference

 Select the application and attach


the field name.
CREATION OF LOCAL REFERENCE TABLE CONT…

 Since, it is single value field


validate and commit the
record.
CHECK IN T24 BROWSER - LRT
LAUNCH THE APPLICATION
CREATION OF LOCAL TABLE
FOR MULTI VALUE FIELD
CREATION OF LOCAL
TABLE
 Go to Transact from
homepage -> Click on User
Field

 Give the mandatory field and


click on the save.
CREATION OF LOCAL REFERENCE TABLE

 To attach it to the respective


application.

 Go to Data Model -> User


Table Reference

 Select the application and


attach the field name.
CREATION OF LOCAL REFERENCE TABLE
CONT…

 For multi value field, give ->


Xx. In the Sub Assoc Code.

 Validate and commit the


record.
CHECK IN T24 BROWSER - LRT
LAUNCH THE APPLICATION
CREATION OF VERSION
WITHOUT APIs
.
.

 This feature enables the users to design screens for any Transact
model.
 This section provides the steps to create a new version, search
and edit an existing version.
 Version is created in 4 stages -

1. CORE DEFINITION
2. FIELD SELECTION
3. ADDING FIELD DETAILS
4. VERSION ASSOCIATIONS
CORE DEFINITIONS

 Enter the Application Name,


Screen Name and Description.
 Select the number of
authorisers from the No of
Auth dropdown.
 The field Version Full Name
will form automatically using
the values in Application and
Screen name fields.
 The maximum number of
character allowed for version
full name is 54.
 The format will be :
<Application>,<Screen Name>
FIELD SELECTION

 Select all the mandatory


fields from the fields list.
 Select the required fields
from the left pane and
move them to the right
pane.
 To include one or multiple
fields in the new version.
ADDING FIELD DETAILS
VERSION ASSOCIATIATION

CUSTOMER,ADDRES CUSTOMER,ACCOUNT.
S DETAILS
CHECK IN T24 BROWSER - VERSION
LAUNCH THE VERSION
AMENDING THE VERSION
To edit an existing version.
 From the Transact Standard dashboard’s left pane, click
Configuration -> Version.
 Search for the Version and make the necessary changes for it.
 Validate and commit the changes to the database.
CREATION OF VERSION WITH
APIs
.
WHY TO CREATE AN API VERSION

 Change fields or routine after an API is released.

 Change payload structures, such as changing a variable from an


integer to float, for instance.

 Remove endpoints to fix design or poor implementation of HTTP.


.

 This section explains how to create a new API version, search


and edit an existing Version and add it to a package.

 Create or update a REST API through Update API Definition.

 Download updated swagger for an existing REST API after adding


a field to an existing API definition.

 Execute the API Version to test the APIs fields and logics
(example: Input Validation).
CREATION OF AN API VERSION

 Select API With Version -> click on Add New Option


CREATION OF AN API VERSION CNT…
 APPLICATION NAME : Give the required
application name using content assist.
 API NAME : Provide the API name based on
an action. For example, GET.CUST.NO
 API VERSION : Provide the API Version. By
default, 1.0.0 is displayed.
 PRODUCT NAME : This field is auto
populated based on the application name
and can be modified as required.
 VERSION Name : This field is auto
populated based on the product, API Name
and Version.
 The maximum number of characters allowed
for Version full name is 54.
 The format will be like
<Application>,<Product Name>.API<API
Name>.<API Version>
CREATION OF AN API VERSION CNT…

 In the Additional Details,


Provide all the validation
routines like (Input Routine, ID
Routine, Check Routine, etc.,)
that must be applied during API
execution.
CREATION OF AN API VERSION CNT…
CREATION OF AN API VERSION CNT…

Enable the
Required check box
to make the
allowed values
Mandatory

Read Only check


box to make the
field No Input
(Read Only)
CHECK IN T24 BROWSER
AMENDING THE VERSION
To edit an existing version.
 From the Transact Standard dashboard’s left pane, API -> API with
Version.
 Search the Version to add, delete or edit the fields associated with
this API and increment the API Version.
CONCLUSION
.
TEMENOS WORKBENCH – OUTCOMES

 Web – based, single entry point for configuration

 Accelerate development with autonomous agile teams

 Boost productivity

 Get changes to market faster

 Automated deployments

 Future proof solution


THANK YOU 

You might also like