License matrix
The IBM® TRIRIGA® License Matrix is delivered in the software. It is available at . The License Manager includes a List View and a Matrix View. This Matrix View is also known as the License Matrix.
The TRIRIGA License Matrix is for general guidance and reference and contains IBM proprietary information. The information within the License Matrix does not constitute legal documentation. Customers should refer to their Terms of Use (TOU), Service Description (SD), and/or other governing agreement(s) with IBM for applicable terms.
The TRIRIGA License Matrix is for reference only. This material may change at any time at IBM's sole discretion, based on market opportunities or other factors, and are not intended to be a commitment to future content, including product or feature availability, in any way. Please be advised that the information within the License Matrix contains IBM proprietary information which, if obtained by a third party may eliminate a competitive advantage in the industry.
In consideration of IBM's disclosure, you may not reproduce or make this information available to any person outside of your employees and agents. The final determination that the proposed products and services meet your technical requirements must be yours.
Contents
I. Introduction
IBM TRIRIGA licensing works by granting access to a defined list of TRIRIGA tools, modules, business objects (BOs), or UX models (i.e., the rows in the matrix) for a set of different licenses (i.e., the columns in the matrix). The granted access (i.e., the intersecting cell for a given row/column) is either full (i.e., create, read, update, delete), read-only, or none.
II. Builder tools
The first section of the license matrix lists a set of tools that are license-controlled. For example, the Workflow Builder is listed in this section and is only accessible by a handful of licenses that grant a user access.
III. UX models
The second section of the license matrix controls access to UX Models defined in the UX Model Designer. The access defined in this section overrides any access defined at the module or business object level and is used to provide more granular control over UX applications (or apps) that use those UX Models.
IV. Modules and business objects
The third section of the license matrix controls access at the module and business object level. The most specific level of access is granted at the business object level. If a business object is listed in the matrix, then access to that business object is governed by the values in the matrix: full access (indicated by a check mark “✓” or “X”), read-only (indicated by the letter “R”), or if left blank, no access. These values (even if left blank/no access) override and take priority over any module-level access (defined below).
For business objects that are not listed, access may be controlled at the module level. If a module name is included as a row in the matrix, then all objects within that module are license-controlled. Access for business objects in the module not explicitly listed is granted based on the module's access value: full, read-only, or none. If there are no individual business objects listed under a module, then all business objects in that module have the same level of access. Access defined for a module also applies to custom BOs created in that module.
If a module is not listed in the matrix, then access to the business objects in that module isn't controlled by a license. If a custom object is created in a module not listed in the matrix, then access to that object will not be restricted by a license. However, if a module that contains the custom object is added to the matrix in a future release, then access to the custom object will be governed by the license access defined for the module.
V. How it works
Here's an idea of how this works. In this example, the triRequest module and
several licenses are shown. The “✓” in the first line is the module-level access. This means that
the Cloud Self Service license provides full CRUD (create, read, update, delete) access to
any business objects in that module that aren't listed specifically in the matrix. There are 21 BOs
in the triRequest module, but only 12 of those are explicitly listed. So this
module-level access for Cloud Self Service provides full access to the 9 BOs not listed. However,
the Portfolio Data Manager license does not have access to those 9 BOs because its
module-level access is blank, or no access. If a new BO is created in the
triRequest module, the Cloud Self Service license will grant access, but the
Portfolio Data Manager license will not.
For the BOs listed in the triRequest module, access is defined by the entries
for each license. Neither of the above licenses grants access to
triCarbonCalculation, so that BO won’t be accessible by either license.
triBidClarification has full access by the Cloud Self Service license, but no
access by the Portfolio Data Manager license. Meanwhile, triDispositionRequest has
no access by either license, but has read-only access by Cloud Approvals and Reporting.
TRIRIGA administrators can see what access is provided by the licenses they have installed in the License Manager in the Matrix View, or in the Administrator Console in the Licenses page. An administrator can also choose a user on the left panel to see the license access granted for that specific user.
a. Example of the License Manager in the Matrix View
b. Example of the Administrator Console in the Licenses page
