Release R19: Design Studio (DS) Release Notes

Release R19
Design Studio (DS)

Release Notes
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.
© 2016 Temenos Headquarters SA - all rights reserved.

Contents
Contents............................................................................................................................................... 2
1. Introduction................................................................................................................................. 4
2. Release Highlights .................................................................................................................... 4
2.1 Enhancements........................................................................................................................ 4
2.1.1 Enterprise Deployment Pattern (EDP) Tooling in Design Studio ................ 4
2.1.1 Menu for Creation of T24 Models ............................................................................ 6
2.1.2 Enhanced Enquiry Designer ...................................................................................... 7
2.1.3 Feature switch to enables Data ESON validation............................................ 10
2.1.4 Data ESON Importer .................................................................................................. 10
2.1.5 Application Import by Name ................................................................................... 11
2.1.6 Headless import for System definition file. ....................................................... 11
2.1.7 Data ESON handling of Multi Company .............................................................. 12
2.1.8 Headless import for Bulk Import using CSV..................................................... 13
2.1.9 Data ESON Importer .................................................................................................. 13
2.1.10 Headless import of LT, LRT and AAProduct .................................................... 13
2.1.11 Data ESON handling of Multi Company – Quick fix ..................................... 14
2.1.12 Audit fields in Data ESON ...................................................................................... 15
2.1.13 Import of T24 models such as COS, TAB, Menu .......................................... 16
2.1.14 Automated L3 Impact Analysis ........................................................................... 16
2.1.15 Documentation on creation of multi-value local reference field ............ 20
2.1.16 Documentation on L3 Impact Analysis ............................................................. 21
2.1.17 Version Designer – Addition of new property “layout” .............................. 21
2.1.18 Packager Improvements ........................................................................................ 22
2.1.19 PWD Designer – Option to arrange PWD diagram from left-to-right... 23
2.1.20 PWD Designer – New wizard to have mandatory fields ............................ 24
2.1.21 PWD Designer – Tooltip added to elements in palette .............................. 24
2.1.22 T24 Data Packager ................................................................................................... 25
2.2 Defects .................................................................................................................................... 36
2.2.1 PACS00794734 - Require INSERT files to be packaged using DS
packager ..................................................................................................................................... 36
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.
© 2016 Temenos Headquarters SA - all rights reserved.

Design Studio Release Notes R19
2.2.2 PACS00794949 - Require only Temenos artefacts as part of the t24-

binaries ....................................................................................................................................... 37
3. Changes incorporated in DS R19.1 .................................................................................. 37
3.1 DS R19.7 ..................................................................................................................................... 38
3.2 DS R19.27 ................................................................................................................................... 38
3.3 DS R19.29 ................................................................................................................................... 39
3.4 DS R19.30 ................................................................................................................................... 39
3.5 DS R19.36 ................................................................................................................................... 39
3.6 DS R19.40 ................................................................................................................................... 39
3.7 DS R19.41 ................................................................................................................................... 40
3.8 DS R19.45 ................................................................................................................................... 40
3.9 DS R19.49 ................................................................................................................................... 40
4. Migration..................................................................................................................................... 40
3
1. Introduction
The Design Studio (DS) Workbench application is an integrated graphical environment that
enables business and IT professionals to design elements for T24 Model Bank. The application
provides his own "designers" using editors and text-based tools for developing elements called:
models.
Design Studio is the Integrated Development Environment (IDE) for realizing T24 design time
tasks. It provides import and edition of resources (local ref, versions, enquiries...). All items
edited in DS intend to be packaged and deployed on T24 runtime environment
2. Release Highlights
This section provides an overview of any new DS components or features and advice regarding
any components which have been replaced, deprecated or modified.
DS version is R19 AMR
2.1 Enhancements
2.1.1 Enterprise Deployment Pattern (EDP) Tooling in Design
Studio
Enterprise Deployment Patterns is a new feature to handle deployment of multiple

packages more effortlessly.
The template project -TAFJ DS Package Installer is available to create a war file that
bundles different types of packages like DS, IF etc. war that is deployable
4
To get the packages bundled into WAR file, they must be added as maven dependency as
shown below.
Running maven install on project TAFJDSPackageInstaller results in a war file as shown

below.
The WAR file contains all packages bundled inside.
The folder packages contains the bundles defined in the dependency that user wishes to
deploy into T24 environment.
5
DSPackageInstaller.war is used to deploy the bundles that are packaged into one single
war file. We can check whether the war file is deployed in application server in the browser
at http://localhost:9089/DSPackageInstaller/.
2.1.1 Menu for Creation of T24 Models
When there are projects in the workspace and user has not selected any project for import.
The File --> New click should display menu for all the models creation.
Shortcuts ALT+SHIFT+N and CTRL+NDesign Studio T24 must provide the model
creation options.
If there is no project selected, in such scenarios container / destination selection page is

displayed during the model creation operation. Similar approach is ensured in Tool bar icon
operation as well.
6
2.1.2 Enhanced Enquiry Designer

Enquiry designer has been enhanced to increase the usability. Major changes are in Data
Output and Presentation tabs.
Changes in Presentation Tab

The Presentation View displays the fields sorted according to field types such as Headers,
Columns (Displayed fields), Invisible and Footer panels which are collapsible and
expandable.
7
User can add Header titles and enquiry fields using the add icon near the panel. Hovering
over the add icon will show the appropriate tooltip description.
Each field under the panels is displayed as a box with field name on the top.
Field box contains conversions where the user can use the add icon to open the “Field
Operation Selection” dialogue box and add new conversions.
Hovering over items will display the full item name. The displayed fields are shown as a
blue box and the hidden fields as orange box. Clicking on the action bar (top right corner
of box) or a right click anywhere inside the box will open a context menu.
8
Changes in Data Output Tab

The fields are colour coded according to their types. Yellow- Header Fields, Blue- Displayed
Fields, Orange- Hidden Fields, Grey- invisible Fields & Green- Footer Fields. When the user
creates a new field or adds a field, it would be created with “Displayed” visibility in blue
colour.
The tabs ‘Operation’ and ‘Break’ is removed from the Properties view. A field will have
a field name followed by its visibility and may or may not have any of these three –
Operation (OP), Break Condition (BC) and Format (FMT).
Double click on the Operation will open the “Operation Selection” dialogue box. A single
click on OP/BC/FMT will open the respective tabs in the “Properties” view.
Drag and drop can be done to move the fields.When we select a field and right-click, a
context menu opens. User can also open the context menu by clicking on the colored action
bar icon. New icons are added for “Move Up”,”Move Down” and “Copy Enquiry Field”.
Operation, Break, Format can be added from the context menu list.
9
If a field already have any of these OP/BC/FMT, then a right click on the field will not show
add option for those which is present i.e. a field can have only 1 OP,BC and FMT.
The context menu will display “Make Invisible” option for Displayed and Hidden fields. If a
field is already marked Invisible then the option “Make Invisible” is not shown. A Header
cannot be made Invisible, so the option is not shown here too.
Making a field invisible will change the colour to grey.
2.1.3 Feature switch to enables Data ESON validation

Design studio has introduced few business validation for Data ESON records such as
maxlength for fields, Enum values and mandatory fields. These validations must be
enabled based on the user requirement. To enable such control we have introduced a
new feature switch. By default the validation is applied, to disable it the use has to use
the below mentioned feature switch as mentioned below.
-Dds.t24.data.eson.validations=false
2.1.4 Data ESON Importer

Import wizard of Data ESON has been improved by making the application text editable.
Before user has to browse through application to select even if he knew the application
name. Since it is made editable user can directly enter the application name for which
data record must be imported.
Be sure of the application name, else we get T24 exception “Application Missing” error.
10
2.1.5 Application Import by Name

Import of an application by name has been improved.
If T24 environment is not up and running, then on launch of this import will inform user
User can select application name using the content assist or manual entry.
In case application is moved to a different component in T24 environment, on import

using this feature for component mode, will delete existing application in the domain
file and imports this in a proper domain file as per T24 entry.
2.1.6 Headless import for System definition file.

Feature has been added to support headless import of System Definition xml file.
A new DS parameter has been provided to perform this action.
-Dds.t24.models.toImport=sysdef:sysdefs
11
2.1.7 Data ESON handling of Multi Company

Data ESON records which are company agnostic must not contain the company code
either in filename or in its content. To support this request Design studio improved Data
ESON importer to not add CO.CODE for INT type of data records in the filename or file
content.
Any deviation in this, is shown as error in Problems view of Design Studio
To rectify or correct such erroneous records Migrate option is provided. This works on
both file and folder levels.
12
This option is available only if Data ESON records have errors related to CO.CODE.
The packager build is not stopped if there are any such errors, as this is allowed in T24.
2.1.8 Headless import for Bulk Import using CSV.

Feature has been added to support headless import of bulk import using CSV.
A new DS parameters has been provided to perform this action.
-Dds.t24.models.toImport=BulkImportCSV:csv
-Dds.t24.bulkImport.models.csvFilePath=<location of the csv file>
Note - The present functionality only works when the destination in the destination
column of csv file exists and that should be mymb-models/Models
2.1.9 Data ESON Importer

Design Studio has added feature to import all data records for a given application using
the wild character “*”. By giving * in place of record Id imports all the data records
available in the T24 environment for a given application.
This option must be used very cautiously, when there are thousands of records involved
we recommend to use bulk import option.
2.1.10 Headless import of LT, LRT and AAProduct

Design Studio has modified headless import of LT, LRT and AAProduct to not default
import folder or destination folder. Instead respect the destination folder provided by
user.
13
2.1.11 Data ESON handling of Multi Company – Quick fix

Data ESON more user friendly in multi company environment. In this we placed an error
marker if the record related to INT type tables contained CO.CODE references.
To rectify such errors other than “Migration” menu option, quick fix is also provided as
shown below in this release.
14
2.1.12 Audit fields in Data ESON

In the Data ESON record we had option to include audit fields which are of no use to
user. Audit fields such a give below
o RECORD.STATUS
o CURR.NO
o INPUTTER
o DATE.TIME
o AUTHORISER
o CO.CODE
o DEPT.CODE
o AUDITOR.CODE
15
o AUDIT.DATE.TIME
Except CO.CODE we have no use of other fields in our T24 design inside Design
Studio. In Design Studio it is decided to remove these unwanted audit fields and
Reserved fields from properties view for USER. This ensures any unwanted code
being stored in our source control. Migration option is provided for removing
these fields from the data ESON records for existing source controlled records.
2.1.13 Import of T24 models such as COS, TAB, Menu

T24 models such as COS, TAB, Menu, Main Menu and Context Enquiry can be imported in
Component or Product mode. For models which does not contain component or product
defined in T24 results in getting imported into the destination folder selected by user
during import operation.
Clients who wanted to maintain T24 core models in COMPONENT or PRODUCT structure
find such models deviating their structure setup. To overcome such issues, we had to
default a component and product in design studio during import.
For component, the default value is NO_Component and for product, default value is
NOPROD
2.1.14 Automated L3 Impact Analysis

T24 Core Model comprises of enquiry, version, composite screen, menu and context
enquiries which are typically UI related models in T24. Impact Analysis of L3 models at
customer can be done with the help of L3 Impact tool provided in Design Studio that will
mark L3 models which need user attention based on T24 update / upgrade actions. It
provides a 3 way merge tool which allow developers to check changes made in T24 Core
Models and corresponded impact on L3 models.
16
The L3 Impact Tool provides a menu option to perform following operations
1. T24 Refresh Upgrade

a. Operation to be executed after a T24 upgrade activity. This provides the upgrade
versions available in T24 environment for user to select. This performs Import
domains and Import Core Models.
2. T24 Refresh Update
a. Operation to be executed after T24 update activity. This provides the update
versions available in T24 environment for user to select. This performs Import
Core Models only based on the version selection.
Refresh command retains the old Core Model in the workspace to use it for compare. The
L3 models impacted is marked either as warning or error marker. The impact of T24 Core
Upgrade or Update on L3 models in Design Studio is generated as an L3 Impact Report.
The report summarizes Release ID(s) selected, Number of Applications imported (for T24
Refresh Upgrade), Number of Core models imported and Number of Local Models (L3)
Linked. Impact report as text file would be generated for command line execution of
refresh command.
A marker will be created on each L3 model (Customized Core Model). It is possible to

convert the warning into error by setting the following system property in the
DesignStudioT24.ini file: -Dds.t24.l3.reconciliation.asWarning=false (default value is
true)
Compare Tool has capability to compare 3 models in single window. The 3 models are:
1. Existing T24 Core Model

2. Imported T24 Core Model
3. L3 model related to T24 Core Model
The existing T24 Core Model will be retained in workspace with .old suffix in the file name
and to be used during compare. This file will be removed after user takes action on it.
T24 Refresh mechanism is available as import option as shown below
In the next wizard page user can select T24 Refresh for Upgrade or Update. User has to
provide the prefix used at client side that is used to identify L3 models. Prefix can be
multiple with coma separated. User can decide to skip L3 analysis. User can decide to
fetch the core models from respective applications instead of DSL.MODEL.SOURCE.
17
In the next wizard page the user can select the upgrade or update version.
On clicking Finish, Core models for selected version is imported and L3 models are
marked for user review. Import report provides an overview to user.
User can take action on the marked L3 model using Quick Fix option.
18
The user can select from the 2 quick fix provided and the resource to which the quick fix
is to be applied.
1. Mark as Merged:
a. The old Core Model is deleted
b. The problem marker is deleted
c. No change in L3 model.
2. 3-way merge:
a. When this quick fix is selected, a 3-way merge tool is opened. The left part will
contain the L3 Model and right part will contain the Imported Core Model. User
can click on the Show Ancestor Pane icon on top to open the previous Core
Model as the common ancestor. Only the L3 model is editable and changes can
be copied with the help of comparator tool.
19
When the user has copied the required change, the Commit buttons becomes enabled and
on clicking it a message box opens and asks "Is the merge work finished”. If No is pressed,
then Message box closes without any action performed. If Yes is pressed, then following
actions are done:
a. The old Core Model is deleted

b. The problem marker is deleted
c. The 3-way merge editor is closed
2.1.15 Documentation on creation of multi-value local reference

field
DS Help Contents has been updated with information on how to add a new local field
reference, an entry for LOCAL.TABLE. This field is of type multi-value
20
2.1.16 Documentation on L3 Impact Analysis

Design Studio Help Contents has been updated with information on usage of L3 Impact
analysis feature.
2.1.17 Version Designer – Addition of new property “layout”

Version Designer has been improved now to add layout information to the screen. This
layout is an ENUM with values None, Grid and Linear.
This new property is available in the presentation tab in the screen designer as shown
below
In DSL it is shown as below
After code generation the version xml content for this will look like as shown below
21
2.1.18 Packager Improvements

Design Studio has brought new improvements in installing the package artifacts.
Previously we had option to install only one package at a time. It is now possible to
install multiple package in a desired sequence. Also an option has been provided to
ignore the failure cases of DS package install in T24.
For Single packages the steps remain same. When we have more than one package we
need to provide the package name as arguments in the sequence we want deploy to
happen.
For releasing the artifacts R17_XX_Sample and R18_AA_Test we execute the following
command:
tRun.bat -cf tafj T24PackageInstaller R17_XX_Sample_1_JAVA_17.0.jar,
R18_AA_Test_1_JAVA_18.0.jar
As a result the records are released into proper folders
For deploying the artifacts released first from R17_XX_Sample and then from
R18_AA_Test we run the following command:
tRun.bat -cf tafj packageDataInstaller
R17_XX_Sample_1,R18_AA_Test_1>YourLogMultiFile4.txt
22
On successful execution we can find that R17_XX_Sample was first deployed and later
R18_AA_Test related records.
To ignore the failure cases in the next deployment, we must provide –ignore as
argument as shown below:
tRun packageDataInstaller –ignore
Please note we cannot combine ignore and multiple deployment option.

For example: tRun packageDataInstaller –ignore R17_FT_ModelBank_1 (is invalid)
2.1.19 PWD Designer – Option to arrange PWD diagram from left-

to-right.
As of now in the PWD diagram editor, clicking on Arrange All action in the tab-bar results
in layout in only top-to-bottom direction.
It would be nice to have an option/preference to select the direction (left-to-right,
bottom-to-top and the default top-to-bottom) and do arrange PWD elements.
23
A preference page is provided to let user select the direction he wants to arrange PWD as
shown below.
2.1.20 PWD Designer – New wizard to have mandatory fields

Creation wizard for PWD is made to include the mandatory parameters needed for PWD.
2.1.21 PWD Designer – Tooltip added to elements in palette

In the Palette all the nodes should have a tooltip describing the usage on each element
to user.
24
Also element “Pre Req Ruleto” is changed "Pre Context Rule" in Palette.
2.1.22 T24 Data Packager

Data packaging is the ability to capture a set of T24 configuration changes and to deploy
them safely in a different environment.
The data packager allows packaging of any T24 data.
There are different use cases supported:

 Data packaging with connectivity to a Source Control Management tool like GIT,
SVN through an IDE
 Building/deploying data packages in a continuous integration chain
 Data packaging through Browser
A data package will include a list of T24 data records (like a T24 version, T24 menu …)
The key features of data packaging are:

 Same data packaging experience across Temenos products (for now only T24)
 Define the sequence in which the data records need to be deployed
 Data package dependencies against other data packages. For an explanation on
dependencies against code, please check SDLC and deployment strategies section
The Data packager can be used in Eclipse IDE or in a browser
2.1.22.1 DSF Initial Setup

Application Server setup
 Place two war files dsf-iris.war (for API) and dsf-uxp.war (for UI) in application
server deployments folder (e.g.: ..\Temenos\jboss\standalone\deployments).
 Start the server and ensure both the war files are deployed successfully.
Eclipse plugin installation

 You need the p2 repository (e.g. dsf-p2repo-DEV.0.0-SNAPSHOT.zip).
 Then use Design Studio or Eclipse and install new software (menu Help/Install New
Software).
25
 Select DSF p2 repo.
 Click Next / Next / ... / Finish.

 Click OK on Security warning and wait for the installation to complete and restart
for the changes to take effect.
2.1.22.2 Data Packager in IDE

The goal of using Eclipse IDE is to rely on the IDE to bring connectivity to SCM (Source
Control, e.g. GIT) and other IDE tooling like history compare
This brings one of the key principles of an advanced SDLC
 Data in source control (or in Eclipse) becomes the source-of-truth instead of data
already deployed in a product
 No need to retain a reference environment
In IDE each project stands for one package.
Package Structure in IDE

The package consists of:
 An eclipse project.
 t-package.json file that described the package content (without the data records).
 A data folder that contains a list of JSON files that the package consists of.
 pom.xml that can be used to build and/or validate the package in a continuous
integration setup.
26
Package Designer in IDE
In IDE, the package content is stored in the application DS.DSF.PACKAGE when

package is saved/deployed.
 DS.DSF.PACKAGE only contains the list of data records, not the content itself
 The data record(s) content is the file in the data folder (this is the key difference
with browser mode)
 If the data record is modified in T24, then you need to synchronize the data record
or the full package to get latest changes in IDE/SCM
 Double-clicking on the t-package.json file will open by default the Package

designer:
If you add a data record in IDE mode, upon save the new data record will be
downloaded from T24. Save of the package just saves the definition, it doesn't
deploy/validate the package.
27
Package Definition in JSON format
You can also open t-package.json with a text or JSON editor.
2.1.22.3 Add/edit/delete package data record

Add/Edit the data records in the package from IDE:
 This follows the same steps as in creation but the difference is the package name
and version cannot be modified.
 From the Definition tab, we can modify either the description or the Status.
28
 From the Content tab, click on (+) Add Data Record and add a new data record
and click on Import.
 Click on Save will save the changes to T24 as well as update the workspace.
 We can also edit and delete an existing data record from the Content tab.
2.1.22.4 Validate Package

 We can validate a package both in Browser and IDE mode. We can also validate a
package through Maven/command line
 It is recommended to validate package at build time to reduce errors at deployment
time
 Validation is triggered through the validation button in package editor.
 Validate button is enabled once the package is saved.
 Validation of a package will always use OFS bulk mode without committing to T24
(only validation) with retry strategy to manage dependencies issues within the
same package
29
 Web editor will show validation errors in a collapsible error pane at the top of the
page when there are errors.
 Error pane will include typically product validation errors (code, message, and type)
and eventually screen validation errors.
 In IDE mode, import the package zip file. Navigate to [package-name] / src and
open the t-package.json file in Web Designer. Click on Validate button, will display
validation error if any in the error pane as shown below.
2.1.22.5 Deploy a data package

Deployment of a package is possible through several ways:
Deployment from IDE

 Import the package .zip into DS or eclipse workbench.
 Open t-package.json in Web Designer, click on Deploy button to deploy the
package.
30
 A popup window with title Package Deploy is displayed with two radio button
options - Single Transaction and No Transaction.
Deployment modes:
Single transaction Non-transactional
Single transaction Non-transactional
Validations Yes all records are validated
Atomicity Yes, all records are s No
Performance Good if deployment sequence Good

doesn't need a retry
Please check the logs to see if
there are multiple-retry attempts
and optimize the deployment
sequence accordingly
Retry strategy If there are Deployment failures If there are deployment failures in
in some of the records, a retry some of the records, a retry will
will again send all the records again send all failed records and
again with first all records that will continue to do so until success
succeeded and then the failed or no change in number of errros
ones
Control data Yes Yes

records
sequencing (retry strategy will always be (retry strategy will always be
active) active)
Multi-company Supported. 1 transaction per Supported

company
 When deploying a package, if a record has an error, the error will be shown
on top of the screen with errors.
31
2.1.22.6 Download a data package

 We can download a package to see the content with the download button.
 Launch Package Manager, do a search with your criteria's. Click on Download
button on a relevant package from the Package List.
 Click on Download button will enable the user to download the package to its local
file system through a popup. (By default file is saved to Downloads folder of user
machine)
 Download option is also available in the Package editor screen once the package is
saved
32
 Package will be download in .zip format and the package content will be retrieved
from T24 data.
 All the data records will be stored in .json format as shown below
 A Package is an Eclipse project with predefined structure

a. pom.xml
b. src / data / -> data records
c. src / t-package.json -> package definition
 JSON files will follow following structure
[component].[type]![company]![recordid].json
2.1.22.7 Import a data package

 From the browser, we can do a import of a data package through a zip file.
 Launch the Package Manager and click on "Import Package from zip file" button
 A popup with title "Import Package From Zip" is displayed with a Import and a
Cancel button.
 Browse the package zip file from local file system and click on Import will import
and deploy the package.
 The import will create the definition and import all data records in system but not
the failed package.
 OFS bulk is used but not in transactional mode in order to still have all records that
succeed.
33
 On successful deploy, we get a confirmation popup as shown below and package

gets deployed to T24.
 Any failure in deployment will show failure popup with a error message on the top
of the screen and doesn't deploy the package.
2.1.22.8 Add data records to a package through a CSV file

 We can perform bulk import of records through a CSV file. This is useful to import a
large list of data records in one go.
 In the Content tab of the Package Editor screen, we have a button to provide an
option for bulk import.
 CSV should follow the format Component, Type, Record ID, Company
 Component should be "t24data" (in future tapdata, t24retail, t24pw etc)
 Type (eg:ENQUIRY) should be non-empty and takes a Application Name
 Record ID (eg: CUSTOMER.INFO) should be non empty and takes record ID of the
application
34
 Company can be empty or not (for each line)
 Click on "Import Data Records from CSV" button from the content tab will open a
popup to select the CSV file from the file system.
 Select a CSV and click on Open will load all the records into the Data Records
Section.
 Error message will be displayed if the CSV file is invalid. For example, If the
Component name is not "t24data" , if the Type or Record ID or CSV itself is empty,
then we get below import error
35
2.2 Defects
2.2.1 PACS00794734 - Require INSERT files to be packaged using
DS packager
Issue: Current design studio packager uses the TAFJ compiler to compile the L3 source files
and includes the same to package the generated class files into the jar created. However, the
packager doesn’t package the respective INSERT files available in the “-data-code” project. ABN
AMRO has over 105 repositories maintained component wise and would like to add the insert
files in the jar as well just like T24 libraries. A fix is required in the DS build such that these insert
files are also included while the packager prepare the package.
Fix: A new property and change in pom.xml of data-code project is introduced to include
INSERT files into the final jar.
Pom.xml must have the change shown below
Property ds.package.insertFiles=true entry should be made into launch file of packager as

shown below
36
2.2.2 PACS00794949 - Require only Temenos artefacts as part of

the t24-binaries
Issue:
ABN have a central tooling team called SOLO. They manage all the ABN CICD standards. We
shared our T24_BINARIES.zip, which we are getting as part of DS delivery for uploading it
under ABN nexus. They directly rejected the request as it’s not ABN standard, stating most of
the components in the ZIP file is coming from Maven Central
(https://repo.maven.apache.org/maven2/). ABN already have proxy for maven central
repository. As per SOLO recommendation, it is required that only the binaries which are
created/customised by Temenos are uploaded. Require a solution to upload only the Temenos
artefacts.
Fix: Python script has been provided as part Design studio delivery to achieve t24-binaries
with only Temenos artifacts.
Readme.txt documents on usage of python script on how to extract temenos artifacts and
upload into nexus for a given t24-binaries zip file.
3. Changes incorporated in DS R19.1
Internal
 DS Version Upgrade
 DS - Upgrading Version of Contributor components
 DS-15236: Enquiry Generation - Generate Fixed Sort fields with NO or NULL order
 DS-15234: WS options “Use labels” and “Exclude enquiry selection criteria” are not
disabled
 DS-15232: Disabled SetSortingValueToEnquiry.test Script due to API designer failure
 DS-15230: Security issue to remove sql query disclosure
 DS-15228: ESON - HELPTEXT.MENU unit cases failing with an OVERRIDE
 DS-15145: Change DS and EDS logo image to latest
 DS-14583: Remove double DS release cut need Simplification
 DS-15226: DSF-554: Menu pushback for external URL
 DS-15224: 201904 version update for IRIS generator
 DS-15223: DS Data Framework DFR - SOLR artefacts generation
 DS-15214: Update SVN Connectors in DS and DS TAP
 DS-15192: T24API generation failure due to Sys-number invalid format
37
 DS-14690: RTC-2722136 - Update Template Projects to have R19 as the Released

version
 DS-14796: Enquiry: Unable to set value for Sorting Field in DS
 DS-15206: Check for -SNAPSHOT in contributor m2repos
 DS-15074: The file in &SAVEDLISTS& folder for .d records suggest different record
names
 DS-15200: New cartridge named "T24 UXPB COS"
 DS-15190: Add new DS-PAT scripts for importing COS scenarios
 DS-15191: Update t24-core/pom.xml to make version update possible in DS code
 DS-15189: Generated Metadata verification during design time
 DS-15187: Changes are done to show Consolidated Report of Design Time and Run
Time
 DS-15185: pom.xml changes for iris and edge metadata to populate
Client
No Client defects
3.1 DS R19.7
POM version is 19.7
Internal
 DS-15321: Solr R19 Backpatch
 DSF-1117: CLONE R19 - GOD - Resolve EB.COMPOSITE.SCREEN/EB.TABBED.SCREEN
name-spacing issue
 DS-15302: CLONE R19 - Add DS promoted version to release file in t24 binaries (Only
release binaires)
 DSF-1012: CLONE R19 - Documentation Generation On Demand
 DSF-938: CLONE R19 - Add new CatalogService attributes for T24 enquiry
 DSF-937: CLONE R19 - Add new CatalogService attributes for T24 version
 DSF-936: CLONE R19 - COS eson files to be converted to JSON files included in a data
ESON record
 DS-15275: Comma characters present in the child OFS response are not processed
correctly by TWS.
 DS-15262: CLONE R19 - Cannot import TAP meta-dict
Client
No client defects
3.2 DS R19.27
POM version is 19.27
Internal
 DS-15255: CLONE R19 - Bulk import of CSV fails in Product structure if destination is
not specified for Models
Client
38
 DSF-1743: CLONE R19 - PACS00778033 - RTC-3314193 - Multi language field is not

deployed in T24 for EB.COMPOSITE.SCREEN and EB.TABBED.SCREEN
3.3 DS R19.29
Internal
Client
No client defects
3.4 DS R19.30
Internal
Client
 DS-15360: CLONE R19 - PACS00775911 - RTC-3328493 - While importing a
LOCAL.TABLE with value in field MAX.CHAR as some number prefixed by 0, the “0”
gets lost during import.
3.5 DS R19.36
Internal
 DS-15382: R19 Import Application by name script update
Client
 DS-15373: CLONE R19:PACS00792614:RTC-3378448: L3 Templates are not available

in Design Studio R19.7
3.6 DS R19.40
Internal
39
 DS-15384: CLONE R19 - Importing of Enquiry with SAVE option as a drilldown throws
error.
Client
No client defects
3.7 DS R19.41
Internal
Client
 DS-15390: CLONE R19 - PACS00794734 - RTC-3394642 - Require INSERT files to be
packaged using DS packager
3.8 DS R19.45
Internal
Client
 DS-15388: CLONE R19 - PACS00794949 - RTC-3394674 - Require only Temenos
artefacts as part of the t24-binaries.
3.9 DS R19.49
Internal
Client
 DS-15409: CLONE R19 - Follow on the Nexus IQ T24 binary scan - t24-binaries.
4. Migration
Update DS T24-binaries
POM referencing old t24-binaries versions must be updated to the new version: 19.49
40
Source code / continuous integration

 Upload the t24-binaries to Nexus (or their maven repository)
 Update all the relevant POMs (see POMs migration guide below)
POM migration upgrade guide

To update to the latest version all POMs must be updated to version 19.49
Sample projects to be updated:

- xxxx-models\pom.xml
- xxxx-models-gen\pom.xml
- xxxx-packager\pom.xml
- xxxx-packager\module\pom.xml
- xxxx-data-code\pom.xml
- xxxx-iris\pom.xml
- xxxx-iris-parent\pom.xml
- xxxx-embedded-server-tafj\pom.xml
Migration path is described below: replace NEW_VERSION by 19.49
Original POM New POM
<groupId>com.temenos.maven</groupId> <groupId>com.temenos.maven</groupId>
<artifactId>t24-core</artifactId> <artifactId>t24-core</artifactId>
<version>OLD_VERSION</version> <version>NEW_VERSION</version>
<groupId>com.temenos.maven</groupId> <groupId>com.temenos.maven</groupId>
<artifactId>t24-core-tafj</artifactId> <artifactId>t24-core-tafj</artifactId>
<version> OLD_VERSION</version> <version>NEW_VERSION</version>
If you reference any other internal t24-binairies

artefact then you also need to update it
<groupId>xxx.yyy.zzz</groupId>
<groupId>xxx.yyy.zzz</groupId> <artifactId>aaa-bbb</artifactId>
<artifactId>aaa-bbb</artifactId> <version>NEW_VERSION</version>
<version> OLD_VERSION</version>
41
In xxxx-embedded-server-tafj\pom.xml
,xxxx-iris\pom.xml , xxxx-iris-
<parent>
parent\pom.xml
<groupId>com.temenos.examples</groupId>
<artifactId>testds</artifactId>
<parent>
<version> NEW_VERSION </version>
<groupId>com.temenos.examples</groupId> <relativePath>../xxxx-iris-
parent/pom.xml</relativePath>
<artifactId>testds</artifactId>
</parent>
<version> OLD_VERSION</version>
<relativePath>../xxxx-iris-
parent/pom.xml</relativePath>
</parent>
API Designer update

No Change in API Designer.
42

Release R19: Design Studio (DS) Release Notes

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Release R19: Design Studio (DS) Release Notes

Hochgeladen von

Copyright:

Verfügbare Formate

Release R19

Design Studio (DS)

Information in this document is subject to change without notice.

© 2016 Temenos Headquarters SA - all rights reserved.

Information in this document is subject to change without notice.

© 2016 Temenos Headquarters SA - all rights reserved.

2.2.2 PACS00794949 - Require only Temenos artefacts as part of the t24-

DS version is R19 AMR

Enterprise Deployment Patterns is a new feature to handle deployment of multiple

Running maven install on project TAFJDSPackageInstaller results in a war file as shown

The WAR file contains all packages bundled inside.

2.1.1 Menu for Creation of T24 Models

If there is no project selected, in such scenarios container / destination selection page is

2.1.2 Enhanced Enquiry Designer

Changes in Presentation Tab

Changes in Data Output Tab

2.1.3 Feature switch to enables Data ESON validation

2.1.4 Data ESON Importer

2.1.5 Application Import by Name

In case application is moved to a different component in T24 environment, on import

2.1.6 Headless import for System definition file.

2.1.7 Data ESON handling of Multi Company

Any deviation in this, is shown as error in Problems view of Design Studio

2.1.8 Headless import for Bulk Import using CSV.

2.1.9 Data ESON Importer

2.1.10 Headless import of LT, LRT and AAProduct

2.1.11 Data ESON handling of Multi Company – Quick fix

2.1.12 Audit fields in Data ESON

2.1.13 Import of T24 models such as COS, TAB, Menu

2.1.14 Automated L3 Impact Analysis

The L3 Impact Tool provides a menu option to perform following operations

1. T24 Refresh Upgrade

A marker will be created on each L3 model (Customized Core Model). It is possible to

1. Existing T24 Core Model

T24 Refresh mechanism is available as import option as shown below

a. The old Core Model is deleted

2.1.15 Documentation on creation of multi-value local reference

2.1.16 Documentation on L3 Impact Analysis

2.1.17 Version Designer – Addition of new property “layout”

In DSL it is shown as below

2.1.18 Packager Improvements

As a result the records are released into proper folders

Please note we cannot combine ignore and multiple deployment option.

2.1.19 PWD Designer – Option to arrange PWD diagram from left-

2.1.20 PWD Designer – New wizard to have mandatory fields

2.1.21 PWD Designer – Tooltip added to elements in palette

2.1.22 T24 Data Packager

The data packager allows packaging of any T24 data.

There are different use cases supported:

The key features of data packaging are:

The Data packager can be used in Eclipse IDE or in a browser

2.1.22.1 DSF Initial Setup

Eclipse plugin installation

 Select DSF p2 repo.

 Click Next / Next / ... / Finish.

2.1.22.2 Data Packager in IDE

Package Structure in IDE

Package Designer in IDE

In IDE, the package content is stored in the application DS.DSF.PACKAGE when

 Double-clicking on the t-package.json file will open by default the Package

Package Definition in JSON format

You can also open t-package.json with a text or JSON editor.

2.1.22.3 Add/edit/delete package data record