1. Analytical Application Infrastructure User Guide
  2. Rule Run Framework

10 Rule Run Framework

Financial Institutions require constant monitoring and measurement of risk in order to conform to prevalent regulatory and supervisory standards. Such measurement often entails significant computations and validations with an organization’s data. Data must be transformed to support such measurements and calculations. The data transformation is achieved through a set of defined rules. Rules Run Framework within the Infrastructure System facilitates you to define a set of rules, reporting objects, and processes that are required to transform data in a warehouse. You can execute Rules and Process and manage the pre-defined rules within the system.

The Rules Run Framework is used for the following main purposes:

  • To design a set of rules and processes and to structure the execution flow of processes that are required to transform data in a data warehouse or data store.
  • To design reporting objects based on previously transformed data that is stored as aggregated data in multidimensional databases.
    • To design reporting objects based on the atomic information stored in the data warehouse or data store.

See How Run Rule Framework is used in LLFP Application and How Run Rule Framework is used in LRM Application sections to know how the RRF Module is used in other applications.

Before you begin, do the following:

  • Select the required Application: An Application is mapped to an Information Domain, which refers to a logical grouping of specific information and defines the underlying data warehouse or data store in which the physical data model has been implemented. When you log in to the Infrastructure system, you can access only those Applications to which your user ID is mapped. Contact System Administrator for permissions to access a specific Application.
  • Select the associated Segment: Segments are defined through the Administration Module. A Segment facilitates you to classify all the related metadata in the selected Information Domain. You are authorized to access only those metadata objects to which the segment and user roles have been mapped.

Object Security in RRF Framework

  • There are some seeded user groups and seeded user roles are mapped to those user groups. If you are using the seeded user groups, the restriction on accessing objects based on user groups is explained in the OFSAA Seeded Security section.
  • For creating/editing/copying/removing an object in the RRF Framework, you should be mapped to the folder in case of a public or shared folder, or you should be the owner of the folder in case of the private folder. Additionally, the WRITE role should be mapped to your user group. For more information, see Object Security in OFSAAI.
  • To access the link and the Summary window, your user group should be mapped to the ACCESS role. You can view all objects created in Public folders, Shared folders to which you are mapped, and Private folders for which you are the owner.
  • In the Component Selector window, you can view the RRF objects like Rule and Process that are created in Public or Shared folders to which you are mapped and Private folders for which you are the owner.
  • The Folder selector window behavior is explained in the User Scope section.

Hierarchy Member Security

  • For each information domain, a default security mapper can be set. Based on this mapper definition, the Hierarchy Browser window will be displayed.
  • In the Hierarchy Browser window, the members that are mapped to your user group are enabled and can be used. However, you can view the members that are not mapped, but you cannot use it since they are disabled.
  • If a Child hierarchy is mapped and the Parent is not mapped to your user group, the Parent will be displayed as a disabled node.
  • For all AMHM hierarchies, the corresponding Business Hierarchy is created implicitly. Thus, you can view and use AMHM hierarchies in the RRF Framework, provided they are mapped to your user group.
  • Hierarchy member security is applied only for Source hierarchies. No security is used for Target hierarchies, Rule Condition, Run Condition, and Process Condition.