Digital Assets

Digital assets group together configuration items (entities, attributes, libraries, digital journeys, etc.) that belong to a common context, such as a data model, a digital journey, or an app data form.

Create Digital Assets

1. To start creating a digital asset, you can either:
   • Click Create new Digital Asset in the FintechOS Studio home page.
   • Go to Main Menu > Configuration Management > Digital Assets click Insert.
2. In the General tab, fill in the following fields:
   

Field	Description
Type	Data Configuration - Used for defining metadata relationships and packaging business records which comply with a broad range of use cases, such as promoting banking or insurance products from one environment to another. Data Model - Used for creating and configuring generic data models that can be used by one or more Digital Assets. Digital App (App Data Form) - Used for building solutions published in employee portals for mid- and back-office applications. Digital Journey - Used for building customer facing journeys for a broad range of scenarios. Resources - Used for bundling generic resources such as endpoints, libraries, or style sheets. These can be referenced in more than one Digital Solution by one or more digital assets.
Code	Identification code for the digital asset.
Name	Insert a suggestive name.
Description	Insert a text that describes the digital asset.
Version	Tracks the digital asset versions based on when you Lock and Unlock Digital Assets. To enable/disable automatic versioning, in the Configuration Manager, at the kv/<environment name>/<Studio instance>/app-settings path, set the feature-da-version-type key to: none - The version number can be edited manually. You can enter integer values or numeric values in the x.y.z format. autoincrement - The field is readonly and incremented automatically on asset unlock. When switching the key from none to autoincrement, the asset versions will be incremented automatically from the previous manually set values. On versions using the x.y.z format, the patch number (z) will be incremented. If the feature-da-version-type key doesn't exist, the setting defaults to autoincrement.
Status	This field is read-only. The status is automatically Unlocked.

NOTE  
For each digital asset type, check the configuration item types compatibility in the Configuration items section.
3. Click the Dependencies tab. From the drop-down list, select the Minimum Platform Version with which the digital asset is compatible with. Once selected, the digital asset cannot be imported in a prior version of the FintechOS platform.
4. Click Save and reload.
   The digital asset is created. The second dependency available could be a dependency on another digital asset. For details, see Edit Digital Assets.

Edit Digital Assets

When you open a digital asset, several configuration sections are available

General

When editing a digital asset, the fields in the General tab that you used to create the asset (see Create Digital Assets) are visible in read-only mode, with the exception of the Description field which you can still edit.

Set the Context Digital Asset

If you click Set as context digital asset, the name of the digital asset will be displayed next to the FintechOS Studio logo.

All the configuration items created while the context is active are assigned automatically to the digital asset.

To close the context digital asset, click Close Digital Asset.

Unlock Sealed Digital Assets

Some official FintechOS digital assets have controlled distribution and are locked by FintechOS to ensure their integrity. In this case, a Set Customization Key button is displayed in the interface. This button allows you to insert an unlock code provided by FintechOS to unlock the asset if you need to edit it.

Configuration Items

This tab typically includes all the components required for the digital asset to work, such as entities, form driven flows, entity views, scripts, configurations for the automation processors, and any other configurations made while the digital asset was set as context.

You can also use configuration items to distribute ownership over different areas of a business context. For instance, you can manage an entity form in a digital asset that is different from the one that owns the entity, or you can manage a form step in a digital asset that is different from the one that owns the entity form. This is useful when delivering modular business solutions for back office scenarios.

The Configuration Items tab also shows when an item was linked to the digital asset, and by whom. This is useful for keeping track of the modifications brought to the configuration items. They are shown in the last two columns of the Configuration Items grid: Modified On and User Name.

The section tab has three buttons above the grid. The Branch Digital Asset button merges two digital assets by transferring all the configuration items from one asset to the other. By clicking the button from the current asset, the configuration items will be moved to another asset and deleted from the currently displayed asset. For details, see Branch Digital Assets.

Manually Add Configuration Items to the Digital Asset

To add configuration items to the digital asset, click Add.

The Add Digital Asset Configuration Item page is displayed. The Type field allows you to select the type of configuration item.

The configuration item types compatibility depends on the Digital Asset type:

Configuration item types	Digital asset types
	Data Model	Digital Journey	Digital App	Data Configuration	Resources
Action Group		✔	✔
Action Authorization Type		✔	✔		✔
Advanced Analytics		✔	✔		✔
Anonymous Frontends		✔	✔		✔
Attribute	✔	✔	✔
Business Data Model	✔	✔	✔
Business Entity	✔	✔	✔
Business Entity extension	✔	✔	✔
Business Service Component					✔
Business Workflow	✔	✔	✔
Business Workflow Configuration	✔	✔	✔
Chart		✔	✔
Client Script Library		✔	✔		✔
Code Block		✔	✔		✔
Configuration Data Definition	✔	✔	✔	✔
Custom Form		✔	✔		✔
Dashboard		✔	✔
Data Import Template	✔	✔	✔	✔
Data Set		✔	✔		✔
DB Task		✔	✔		✔
Digital Document		✔	✔		✔
Digital Journey		✔
Email Template	✔	✔	✔	✔	✔
Endpoint		✔	✔		✔
Entity Form Step	✔		✔
EntityForm	✔(default form only)	✔	✔
Entity Unique Constraint	✔	✔	✔
EntityView	✔(default view only)	✔	✔		✔
Form UI Customization		✔	✔
Formula		✔	✔		✔
Formula parameter mapping		✔	✔		✔
Menu Item		✔	✔
Option Set	✔	✔	✔	✔	✔
Portal Profile		✔	✔		✔
Report		✔	✔		✔
Schedule Job		✔	✔		✔
Schedule Service		✔	✔		✔
Sequencer		✔	✔		✔
Server Automation Script		✔	✔		✔
Server Automation Script Library		✔	✔		✔
Style Sheet		✔	✔		✔
System Parameter	✔	✔	✔	✔	✔
User Competence	✔	✔	✔	✔
Web Api Client Library		✔	✔		✔
Widget		✔	✔

where ✔ = compatible

Once the configuration item type is selected, the system will automatically display the grid with the available configuration items.

Manually Remove Configuration Items from the Digital Asset

To remove configuration items from the digital asset, click Remove and confirm. This action also removes child dependencies, such as when removing an entity, it removes the entity default view, attributes, default form, or relations. Once removed, the configuration item becomes unallocated and can be used by other digital assets.

Related Digital Solutions

This section tab displays the Digital Solutions where the digital asset is included.

Data Import Files

This section tab displays the Data Import Templates and the Configuration Data Definitions which allow you to populate the digital asset’s metadata and data. From here, you can set the configuration items’ templates and the records’ data models that you will use for your imports, then you can perform the actual imports.

1. To add a new package, click Insert. Select the Type:
   • Based on Data Import Templates
   • Based on Data Config Definitions
2. Depending on what was selected for the type, two new fields are displayed, Data Import Templates/Data Config Definitions. Select the name of one of the templates/definitions.
3. Click Select file. The local File Explorer opens. Select the desired file and add it to the template/definition.
4. Click Save and reload.

From this section tab, you can download the templates which were previously displayed:

1. Navigate to the Application Data Import Files grid.
2. Select from the grid the template you wish to consult.
3. Click the desired record in the grid. The Edit Application Data Import File page opens.
4. To download a file already imported into the digital asset, click the file and it will download on the local drive.

DB objects

Use the database objects tab to easily add SQL objects such as views, stored procedures, or functions to your digital asset. Database objects added to a digital asset are executed before import when importing the digital solution package to a new environment.

Views, user defined data types and table types can be added as database objects starting with v24.1.1. However, user defined data types and table types objects can only be imported once on another environment, at creation. Packages with updates to user defined data types and table types are not supported and might cause missing reference errors. This is not the case for views, which support updates.

From this section you can attach SQL objects to a digital asset:

1. Use the available search bar to look for a specific SQL object.

2. Check the box for the function, procedure, or view that needs to be attached. Keep in mind that only stored procedures with the name starting with "ebs." are displayed in this list. Objects that start with "FTOS_DEV", "vwResources" , "aspnet_" will not appear in this view.

   

Custom Files

Custom files are used to customize portal profiles, allowing you to change the appearance of theFintechOS Portal instances. Depending on your preferences, these folders can contain:

• style sheets (CSS) to style your application layout (change fonts, colors, margins, etc.)
• different types of images that you want displayed on your application,
• PDF files (Terms and Conditions, Loan Agreement, GDPR),
• Java script files.

 

In this section you can upload the custom and custom-on-demand files needed by your digital solution.

It is advisable to pack your custom files in a digital asset and use the import wizard for an automated publishing of custom files on the application server. Through this wizard, you can specify on which portal/application you want to apply the custom files.

The files should be in .zip archive format and it is advisable to archive them in a folder with the same name as your Digital Asset. In case your custom files contain a resource with the same name as an existing one, the existing resource file will be overwritten.

Custom and Custom-on-demand Folders Structure

• A custom folder contains the video custom components (css, images, and javaScripts: dcs-sdk.js and onfido.min.js) and has the below structure:
  Copy

  ├── {Digital Asset Name}
  │   └── css
  │   └── img
  │   └── js

• A custom-on-demand folder contains the liveness component resources and has the below structure:
  Copy

  ├── {Digital Asset Name}
  │   └── common
  │   └── liveness
  │   └── usermedia
  │   └── video
  │   └── zoom

 

To add custom or custom-on-demand files to click the Add file button to upload the Content For Custom Folder or the Content For Custom On Demand Folder.

 

Dependencies

Dependencies allow you to share resources between digital assets by providing the current digital asset with read-only access to configuration items that belong other digital assets.

To add more dependencies for the digital asset:

1. In the grid labeled Digital Asset Dependencies, click Insert.
2. The Add Digital Asset Dependency opens with the field labeled Referenced Digital Asset. Click the drop-down arrow and select from the list the digital assets.
3. Click Save and close.

Repeat as many times as needed.

To delete a dependency, in the grid, select the digital asset by clicking once, then click Delete.

Configuration Items Migration

Migration is the process of importing a deployment package (including deployment packages from prior releases that don't support configuration management) into an existing digital asset. This allows you to easily upgrade your legacy applications to take advantage of the configuration management capabilities available starting with release 21.2 (digital assets, digital solutions, digital solutions packages, etc.).

To migrate a deployment package, follow the steps:

1. Expand the Choose deployment package for migration field and select the deployment package to migrate to.
   IMPORTANT!  
   You cannot migrate an obsolete digital asset. If you attempt to migrate an obsolete digital asset, a toast message is displayed to inform the user.
2. Click Migrate. If the migration is successful, a grid will be displayed below the deployment package. From the grid, use the Export button to export records and see all deployment packages that were migrated.

Run server scripts in the Advanced tab

In order to re-initialize sequencers, troubleshoot data entry errors, or turn formulas from draft to actives, create an digital asset that contains automation scripts that can either call an endpoint, database tasks, or server side methods.

In the Advanced tab, add the automation script:

• In the Before Import tab if the script should be executed before the import of the digital solution package on the destination environment.

• In the After Import tab if the script should be executed after the import of the digital solution package on the destination environment.

Click Open in Editor to edit your scripts in the Code Editor. The beforeImport and afterImport javascript files are available in the _importOrchestration subfolder.

Delete Digital Assets

To delete a digital asset, you must first unallocate all its configuration items:

1. Go to Main Menu > Configuration Management > Digital Assets.
2. In the digital assets list, double click the digital asset you wish to delete.
3. Open the Configuration Items tab, select all the configuration items and click Remove.
4. Once all the configuration items have been removed, click Save and close to return to the Digital Assets List.
5. From the list, select the digital asset and click Delete.
6. Confirm the deletion by clicking the Yes button when the pop-up question appears with the question Delete one record?

Import Digital Assets

Sometimes, you may need to import a digital asset on your environment. This is often the case when distributing applications that are based on a digital asset.

Prerequisites

• Check the minimum required version of the package and the version of the FintechOS Studio.
• Check the dependencies of other digital assets.
• Make sure the digital asset status is not obsolete.

Lock and Unlock Digital Assets

Locking a digital asset prevents further modifications to its configuration items. The configuration items are still functional, i.e. you can still use the asset's digital journeys to create new records for instance, but you can no longer edit them in FintechOS Studio. This allows you to ensure compliance with your organization's application implementation workflow, for example when you wish to mark a stable version to be used for release.

When you lock a digital asset, its locked state is indicated in red in the FintechOS Studio header (when the digital asset is currently set as the context digital asset):

If you wish to resume development on a locked digital asset (for instance to start working on the next release of your application), you have to unlock it. This reopens the asset's configuration items for editing and increments the digital asset's version number. The changes in the asset's state and version number are indicated in the FintechOS Studio header when the asset is currently set as the context digital asset:

How to Lock a Digital Asset

1. Log in to FintechOS Studio using a user account with the Release Manger security role.
2. Go to Main Menu > Configuration Management > Digital Assets.
3. From the Digital Assets List, open the digital asset you wish to lock.
4. In the General tab, click Lock Digital Asset.

How to Unlock a Digital Asset

1. Log in to FintechOS Studio using a user account with the Release Manger security role.
2. Go to Main Menu > Configuration Management > Digital Assets.
3. From the Digital Assets List, open the digital asset you wish to unlock.
4. In the General tab, click Unlock Digital Asset.

Branch Digital Assets

Branching allows you to merge applications by transferring all the configuration items from one digital asset to another. This empties the source digital asset and tags it as Obsolete. You cannot reactivate a digital asset or use it in any other way once it is obsolete.

To branch a digital asset:

1. In FintechOS Studio, go to Main Menu > Configuration Management > Digital Assets.
2. From the Digital Assets List, open the source digital asset (the digital asset whose configuration items you wish to transfer).
3. Open the Configuration Items tab, and click Branch Digital Asset.
   
4. In the Branch the current Digital Asset window, select the destination digital asset from the dropdown box. Make sure that the target digital asset is not locked or obsolete.
   
5. Click Save.
6. The configuration items is transferred to the destination digital asset and the source asset is emptied and marked as obsolete.