Framework models
- Metadata
- Labels
- Custom query subjects
The reporting framework contains a set of pre-defined framework models, which are used for the pre-defined reports that are supplied with OpenPages. In addition to the pre-defined framework models, you can create your own framework models. The ability to use multiple framework models allows you to target a framework model to specific solutions, user roles, or object profiles.
There are two types of framework models that you can create:
- Standard
- Basic
Both types support profile filtering and allow you to define the package name.
Standard framework models
Standard framework models are intended for advanced report writers with extensive knowledge of IBM® Cognos® Analytics. Use this type of model for reports that require the more complex functionality that Cognos offers.
- Nest a relationship subnamespace.
- Use the following namespace hierarchy:
- Use extensive foldering for query subjects and data items.
- Contain query subjects for ancillary objects such as Enumerations and Relationships.
- Use complex field representations, for example, currencies have multiple data items for local and base amount.
- Represent recursive objects as multiple query subjects using recursive object levels.
- Provide secondary compliance objects, such as Files or Issues, as stand-alone objects. Relationships to them must be built in reports.
Basic framework models
Basic models are intended for end users who do not have extensive knowledge of IBM Cognos Analytics. Use this type of model for more simple reports that you want to allow your end users to create as they require.
- Use the following namespace hierarchy:
Query subjects are created in the root namespace. The
[namespace]_RELsub-namespace is not created. - Do not create ancillary query subjects for Enumerations, relationships, and so on.
- Generate recursive objects, for example, Business Entity, SubMandate, and SubProcess, as single query subjects.
- Generate recursive object levels only for Business Entity objects.
- Remove system-level data items, for example, IS_PRIMARY, LATEST_VERSION, and so on.
- Use simplified field representations, for example, single data items for Currencies and Enumerations as Local Amount and Localized Value, respectively.