DSF Packager 202302

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 DSF 202205.0.1............................................................................................................................. 4
2.1.1 Enhancements ...................................................................................................................... 4
2.1.2 Defects ................................................................................................................................... 4
2.2 DSF 202206.0.1............................................................................................................................. 4
2.2.1 Enhancements ...................................................................................................................... 4
2.2.2 Defects ................................................................................................................................... 4
2.3 DSF 202207.0.1............................................................................................................................. 5
2.3.1 Enhancements ...................................................................................................................... 5
2.3.2 Defects ................................................................................................................................... 5
2.4 DSF 202208.0.1............................................................................................................................. 5
2.4.1 Enhancements ...................................................................................................................... 5
2.4.2 Defects ................................................................................................................................... 5
2.5 DSF 202209.0.1............................................................................................................................. 5
2.5.1 Enhancements ...................................................................................................................... 5
2.5.2 Defects ................................................................................................................................... 8
2.6 DSF 202210.0.1............................................................................................................................. 8
2.6.1 Enhancements ...................................................................................................................... 8
2.6.2 Defects ................................................................................................................................... 8
2.7 DSF 202211.0.0............................................................................................................................. 8
2.7.1 Enhancements ...................................................................................................................... 8
2.7.2 Defects ................................................................................................................................... 9
2.8 DSF 202212.0.1............................................................................................................................. 9
2.8.1 Enhancements ...................................................................................................................... 9
2.8.1.1 Deploying Data Package Using API V4 ....................................................................... 9
2.8.1.2 Deploy response to show FLU, Company specific & Action records ..................... 10
2.8.2 Defects ................................................................................................................................. 10
2.9 DSF 202301.0.0........................................................................................................................... 10

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.

DSF Packager Release Notes 202302

2.9.1 Enhancements .................................................................................................................... 10

2.9.2 Defects ................................................................................................................................. 10
2.10 DSF 202302.0.0......................................................................................................................... 10
2.10.1 Enhancements .................................................................................................................. 10
2.10.2 Defects ............................................................................................................................... 10
3. Changes incorporated in DSF Packager ......................................................................... 10
3.1 Changes in DSF Packager 202205.0.1 ..................................................................................... 10
3.2 Changes in DSF Packager 202206.0.1 ..................................................................................... 11
3.3 Changes in DSF Packager 202207.0.1 ..................................................................................... 11
3.4 Changes in DSF Packager 202208.0.1 ..................................................................................... 11
3.5 Changes in DSF Packager 202209.0.1 ..................................................................................... 11
3.6 Changes in DSF Packager 202210.0.1 ..................................................................................... 12
3.7 Changes in DSF Packager 202211.0.0 ..................................................................................... 12
3.8 Changes in DSF Packager 202212.0.1 ..................................................................................... 12
3.9 Changes in DSF Packager 202301.0.0 ..................................................................................... 12
3.10 Changes in DSF Packager 202302.0.0 ................................................................................... 13
4. Migration..................................................................................................................................... 13

3
DSF Packager Release Notes 202302

1. Introduction
DSF Packager introduces Data packaging 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

2. Release Highlights
This section provides an overview of DSF Packager and advice regarding any features which
have been replaced, deprecated, or modified.

Design Framework version is 202302

2.1 DSF 202205.0.1

2.1.1 Enhancements
N/A

2.1.2 Defects
N/A

2.2 DSF 202206.0.1

2.2.1 Enhancements
N/A

2.2.2 Defects
N/A

4
DSF Packager Release Notes 202302

2.3 DSF 202207.0.1

2.3.1 Enhancements
N/A

2.3.2 Defects
N/A

2.4 DSF 202208.0.1

2.4.1 Enhancements
N/A

2.4.2 Defects
N/A

2.5 DSF 202209.0.1

2.5.1 Enhancements
• DSF is not built and compiled using Openjdk – 1.8.0_232 of Redhat. It can be
downloaded t https://developers.redhat.com/content-gateway/file/java-1.8.0-
openjdk-1.8.0.232-3.b09.redhat.windows.x86_64.zip

• Packager API Reconciliation Tool

Packager API verifies the content of a single or multi-package deployed in an

environment and enables the user to identify the records that are displayed
successfully and the ones that failed along with the reason for the failure.
When you enable the incremental mode, the system checks for only those
records that have a different hash code between package(s) and the target
environment.

This section provides the details of the API request in normal mode and with
incremental hash, sample response, and API behavior for various types of
records.

API Request:

{{baseUrl}}/meta/dsfpackages/inspect

API Request with Incremental Hash:

{{baseUrl}}/meta/dsfpackages/inspect?incremental=hash

5
DSF Packager Release Notes 202302

The below link is an example with hostname as 10.11.12.13 and port as

9089.

http://10.11.12.13:9089/dsf-iris/api/v1.0.0/meta/dsfpackages/inspect

You need to attach the single or multi-package zip/jar file to the body of the
API.

Sample API Response

API response returns the package details along with the details that are same,
and the records which are different than the target environment.

{
"packageStatus": [
{
"name": "RECON-1.0.0",
"synchronized": false,
"totalRecords": 8,
"syncRecords": 5,
"notInSyncRecords": 2,
"undefinedRecords": 1,
"dataRecords": {
"insync": [
"t24data.LANGUAGE!2.json",
"t24data.RE.STAT.RANGE!AAACCT.json",
"t24data.EB.DICTIONARY!%[email protected]",
"t24data.PW.PROCESS.DEFINITION!ACCEPTED.OPPORTUNITY#FLU1.json",
"t24data.CURRENCY!GBP.json"
],
"notinSync": [
{
"id": "[email protected]",
"diffText": [
{
"op": "remove",
"path": "/body"
}
]

In the above sample response, the available details are:

6
DSF Packager Release Notes 202302

name: Indicates the name of the package that is compared.

synchronized: Indicates the overall status of the package by comparing the

package contents with the target environment. If all the records are identical
between the package and target environment, the status will be true. The
status will be false, if otherwise.

totalRecords: Indicates the total number of records available in the package.

syncRecords: Indicates the number of records whose contents in the package

and the product are same.

notInSyncRecords: Indicates the number of records which are different from

the target environment.

undefinedRecords: Indicates the number of records which failed to retrieve

records from the product. For example, application not found, record not
found, and so on.

dataRecords

inSync: Indicates the list of all the data records of the package which are
same as that of the target environment.

notInSync: Indicates the list of data records that failed with the diffText which
provides the difference in the content of the package and the product.

id: Indicates the record id

diffText: Indicates the suggestion on what needs to be done.

op: Indicates the operation. For example, remove, replace, and so on.

path: Indicates the relative path to the field or body for action records.

value: Indicates the value to be replaced with.

undefined: Indicates the list of data records which failed to retrieve from m
the product. This contains the id and errorText.

API Behavior for Various Record Types

Record Description

For a new record, the system calls the reconciliation tool API on a package containing
New
new record but the response is not defined as the record does not exist in the target
record
environment.

For FLU records, this API first applies the FLU and then compares with the content in
FLU
the product. In case the comparison matches, the system returns the value as true.
records
If the comparison does not match, the system returns the value as false.

7
DSF Packager Release Notes 202302

Record Description

For action records, the status depends on whether the API is called before or after
the deployment.

• If a record in the package is with Action as R (reverse) and status of the

record in Product is LIVE,

o notInSync - Indicates that the API is called before deployment

o inSync - Indicates that the API is called after deployment and status
in product will be REVE

• If a record in the package is with Action as D and status of the record in

Action Product is INAU,
records
o notInSync - Indicates that the API is called before deployment

o inSync - Indicates that the API is called after deployment and the
record gets deleted

• If a record in the package is with Action as proof and publish and an auto-
publish record,

o inSync - Indicates that the API is called after deployment and status
of the record is publish. In this case, the content is compared
excluding the action.

2.5.2 Defects
N/A

2.6 DSF 202210.0.1

2.6.1 Enhancements
N/A

2.6.2 Defects
• Issue with the Incremental hash of deployment is fixed to fetch the latest
deployed package and compare before deploying the current package

2.7 DSF 202211.0.0

2.7.1 Enhancements
N/A

8
DSF Packager Release Notes 202302

2.7.2 Defects
N/A

2.8 DSF 202212.0.1

2.8.1 Enhancements

2.8.1.1 Deploying Data Package Using API V4

When deploying a data package through V4 deploy API in async mode, it will be running as a
background process. By default, value for "async" will be false.
Single package deployment response for async = true includes the below information:

Parameters Description

deployId Displays a unique ID with its format (<packageId>,UUID)

name Displays name of the package with its format (.zip/.jar)

startDate Displays date and time when the deployment started

totalRecords Displays total number of records available in the package

extensions Displays the component records available in the package

transactionType Displays the transaction mode (single or no transaction)

status Displays the status of package deployment (success or failed

or in-progress).

chunkSize Displays the chunk size of the deployment

Multi-package deployment response for async = true includes the below information:

Parameters Description

status Displays the status of multi-package deployment (true or false)

overview Displays the below details

deployId: displays a unique ID with its format (<multi-
packageId>,UUID)
startDate: displays date and time when the package deployment
starts
totalRecords: displays the total number of records in the multi-
package

totalPackages: displays the total number of packages in the multi-

package

9
DSF Packager Release Notes 202302

Parameters Description

status: displays the status of multi-package deployment (success

or failed or in-progress).

To deploy a data package using API V4 for single or multi-package, import the dsf-packager-
public-v4.0.0-swagger.json file from dsf-iris.war\WEB-INF\lib\dsf-core-packager-api-DEV.0.0-
SNAPSHOT.jar\api-docs.

2.8.1.2 Deploy response to show FLU, Company specific & Action records
Deploy API V2, V3 & V4 the provides additional information in the deploy response which
includes the information of number of FLU records, company specific records and action
records.

2.8.2 Defects
N/A

2.9 DSF 202301.0.0

2.9.1 Enhancements
N/A

2.9.2 Defects
N/A

2.10 DSF 202302.0.0

2.10.1 Enhancements
N/A

2.10.2 Defects
N/A

3. Changes incorporated in DSF Packager

3.1 Changes in DSF Packager 202205.0.1

Internal
• DSF Version Upgrade to 202205.0.1
• DSF Version Upgrade to 202205.0.0

Client

10
DSF Packager Release Notes 202302

No client defects

3.2 Changes in DSF Packager 202206.0.1

Internal
• DSF Version Upgrade to 202206.0.1
• DSF Version Upgrade to 202206.0.0

Client
No client defects

3.3 Changes in DSF Packager 202207.0.1

Internal
• DSF Version Upgrade to 202207.0.1
• DSF Version Upgrade to 202207.0.0
• DSF Folder structure change overall

Client
No client defects

3.4 Changes in DSF Packager 202208.0.1

Internal
• DSF Version Upgrade to 202208.0.1
• DSF Version Upgrade to 202208.0.0
• DS-1478: Addition of Transaction Time column
• DS-1531: catalog service change
• DS-1393: API changes for max char
• Updating log4j2 properties to populate iris.log
• DS-978: All Processors in workbench Projects should extend DSFProcessor

Client
No client defects

3.5 Changes in DSF Packager 202209.0.1

Internal
• DSF Version Upgrade to 202209.0.1
• Fix upgrade version failure
• DSF Version Upgrade to 202209.0.0
• UXP duplicate jars update

Client
No client defects

11
DSF Packager Release Notes 202302

3.6 Changes in DSF Packager 202210.0.1

Internal
• DSF Version Upgrade to 202210.0.1
• Version upgrade script change in 202210
• DS-1883: Version tag removal by tycho version plugin fix in 202210
• DSF Version Upgrade to 202210.0.0
• Service XML Binary
• DS-1663: Inspect API - synchronized value is wrong when edit/deploy the package

Client
No client defects

3.7 Changes in DSF Packager 202211.0.0

Internal
• DSF Version Upgrade to 202211.0.0
• DS-1883: DSF Packager build failure during 202209.0.1 version upgrade
• Changes for new dsf-iris-directconnect.war with a bean connection
• DS-1502: Multipackage deployment order should be alphabetical order of the package
names
• Update resource ref name for jmsConnectionFactory as irf has updated.

Client
No client defects

3.8 Changes in DSF Packager 202212.0.1

Internal
• DSF Version Upgrade to 202212.0.1
• DSF Version Upgrade to 202212.0.0

Client
No client defects

3.9 Changes in DSF Packager 202301.0.0

Internal
• Release version changed to 202301.0.0
Client
No client defects

12
DSF Packager Release Notes 202302

3.10 Changes in DSF Packager 202302.0.0

Internal
• Release version changed to 202302.0.0
Client
No client defects

4. Migration
Create new projects for working with this release.

13