Managing Data Packages

The below steps guide you to add a data record.

1. On the Content tab, click the + (Add data record) button.

   

   A dialog pop-up window for adding data records opens.

   

   • The Component field defaults to t24data. In future, other types of data will be available (not only core Temenos Transact).
   • The Type field accepts a valid application name with a content assist.
   • The Company field displays the list of all available companies.
   • The ID field is used to enter the record ID for the chosen application. You can also use wildcard * (asterisk) in this field to import records in bulk mode. The formats supported by the wildcard and their corresponding actions are:
     • * = Imports all records for the selected application
     • Characters followed by * = Imports all records that begin with those characters. For example, AA* loads records beginning with AA.
     • * followed by characters = Imports all records that end with those characters. For example, *AA loads records ending with AA.

     A * in the middle of a string is not considered as a wildcard. In case of duplicate records (folder/phase/action), you can select how to interact with them:

     • Move duplicate data records to new folder/phase
       • If checked, existing records are moved to new folder/phase.
       • If unchecked, duplicates are not allowed.
     • Move duplicate data records to new action
       • If checked, existing records are moved to new action.
       • If unchecked, duplicates are not allowed.

     You can refresh the application IDs and Record IDs using the corresponding refresh icons.

     

2. Click Import to add the data record to the content table.

   After that, you can add a new data record or close the pop-up window.

The below steps guide you to edit a data record.

1. On the Content tab, click the chosen edit button. Here edit means from a package point of view, typically, to change the record ID, not to open the record itself in edit mode. A pop-up window with an edit option opens.
2. Modify the record ID or set/remove the company code.

   

The below steps guide you to delete a data record.

1. On the Content tab, click the chosen delete icon (Recycle Bin).

   

   A pop-up window opens requests a confirmation to delete the record.

2. Select Yes. The records gets deleted from the content table.

The below steps guide you to add a record in IDE.

1. On the Content tab, click + (Add Data Record) to add a new data record. A pop-up window opens.

   

2. Click Import.

   You can also edit or delete an existing data record on the Content tab.

The data packager uses retry strategies to manage dependencies between data records, but sometimes it's best to define the sequence in which data records must be deployed.

This is possible through data records sequencing:

• By Temenos Transact application
• By Temenos Transact data record

The retry strategy will ensure that the package will be deployed successfully if there are only dependencies issues, but having a custom sequence would allow to make deployment faster.

You can use the Sequence tab to specify the data record deployment sequence to define the order in which deployment of data records should happen. This is to ensure that deployment is efficient and correct.

The below steps guide you to define deployment sequence for data records.

1. On the main Data Packager page, click the Sequence tab and then click + to add a sequence element.

   

2. Provide the application type to define an application sequence during deployment.
3. Provide both application type and record ID to define the order of deployment of a specific data record of an application.

   

4. Click Add. The sequencing element is added into the Sequence table.
   • You can delete a sequencing element by clicking the Delete button.
   • You can also re-order the records using the Move Up or Move Down buttons.

     

Typically, the following default sequence is recommended. You can adapt it while creating your custom package.

1. PGM.FILE
2. FILE.CONTROL
3. STANDARD.SELECTION
4. LOCAL.TABLE
5. LOCAL.REF.TABLE
6. EB.TABLE.DATA.TYPE
7. EB.TABLE.DEFINITION
8. EB.API
9. EB.TABLE.PROCEDURE
10. AA.CLASS.TYPE
11. AA.CLASS.DEFINITION
12. BATCH
13. LANGUAGE
14. EB.RULES
15. EB.RULE.GATEWAY

It is recommended to validate a package at build time to reduce errors at deployment time.

You can trigger validation through the validation button in package editor. The validation button is enabled after the package is saved.

Package validation always uses OFS bulk mode without committing to Temenos Transact (only validation) with retry strategy to manage dependencies issues within the same package.

A collapsible error pane at the top of the page will be shown when there are errors after an action. Typically, this happens after a package validation.

The below steps guide you to validate a package in IDE mode.

1. In IDE mode, import the package zip file. Navigate to package-name/src and open the t-package.json file in Web Designer.
2. Click the Validate button. In case of an error, a validation error message is displayed.