New features in IBM TRIRIGA Application Platform version 3.5.0
IBM® TRIRIGA® Application Platform version 3.5.0 includes a new UX framework for building UX applications. Also included are platform enhancements to the classic tools to support the UX framework and enhancements for the support of currency.
UX framework for Perceptive applications
- UX framework
Used generically as the "user experience" (UX) application framework, or more specifically as the IBM TRIRIGA UX Framework for Perceptive applications, this term refers to the MVC-based approach for UX applications.
The model-view-controller (MVC) approach separates the application into three components or layers: the model, view, and controller. The view layer is built upon the Polymer library of reusable web components.
- UX application
During the app-designing process, this term refers to the application metadata that pulls together related model metadata and view metadata in the MVC-based approach, all of which are built upon the UX framework.
The model metadata defines the data sources, which retrieve the data and trigger the business logic, while the view metadata defines the HTML components, which render the interfaces.
- Perceptive application
This term refers to an advanced type of UX application that is designed, developed, and delivered exclusively by the IBM TRIRIGA software team.
Built upon the Polymer library of reusable web components, Perceptive applications enable organizations to more easily meet business requirements with an intuitive user interface, compatibility with touch interfaces, and improved performance.
- Classic application
This term refers to the familiar form-based type of IBM TRIRIGA application that is built upon the classic IBM TRIRIGA Application Platform.
UX designers
- Model designer
- You use this designer to define your model metadata and assemble your data sources. The data sources pull your data from business objects, queries, or other source types.
- Web view designer
- You use this designer to define your view metadata and assemble your HTML files. The HTML files are built with Google Polymer and standard web components.
- Model and view designer
- You use this designer to tie together your model metadata and view metadata. Any number of views can be tied to a model, and any number of models can be tied to a view.
- Application designer
- You use this designer to define your application metadata or final layer that pulls the model-and-view metadata. Your UX application can then be shown to users.
For information on the UX framework and Perceptive applications, see the IBM TRIRIGA wiki.
Changes to the classic tools to support the UX framework
Administrator console
You can select the new Translated UX File Cache option in the Cache Manager to refresh the Polymer-based components and HTML files that make up the translated UX views. The product regenerates the translated UX views the next time that they are requested from the server.
Similarly, you can select the new Translated Dictionary Cache option in the Cache Manager to refresh the translatable and translated text that is stored as records of the triDictionaryEntry business object in the System module. Clearing the cache regenerates the translated UX views the next time that they are requested.
Globalization manager
You can select the new Dictionary option to export the labels and tooltips from your HTML views as XLIFF files of unique translatable text. So, if a specific label appears in multiple views, only one unique entry appears in the dictionary.
The translatable text is stored as records of the triDictionaryEntry business object in the System module. When you open the UX view, the platform checks the language setting in your profile. If the language is not US English, the platform generates a translated version of the HTML files and components, and pushes the translated UX view to your web browser.
Navigation builder
You can select the new Application option to open a UX app from a navigation item such as a menu item. For example, if you create a new customized Space or Move app, you can add an item to your main menu to directly open your new app.
Object migration
You can select the new Application option to search for and add UX applications to your export package. During export, all UX metadata that is related to the application, such as the model-and-view, model, and data sources, are automatically added to the package. Plus, all UX application view files, which are related to the web view metadata with a Component Type of VIEW, such as HTML and CSS files, is automatically added to the package.
Similarly, you can select the new Web Component option to search for and add UX web components to your export package. During export, only the selected web view metadata with a Component Type that is not equal to VIEW, such as APPLICATION, BUILDING_BLOCK, CORE, and PLATFORM is added to the package.
Security manager
You can open the new Models tree from a security group, and assign permissions to a UX model. In effect, a user inherits the model permissions from all of the security groups to which that user belongs. Also, the permissions for a model will apply to all of the data sources associated with that model.
The security manager operates on the database table APP_OBJECT_PERMISSION which stores module-level and form-level permissions. But as part of the UX framework, the System module introduces a new triModelPermission business object which stores instance-level permissions for each individual UX model.
