1. IBM OpenPages Developer WYNTK
Read Me First
Updated

2. Notices and disclaimers
© 2018 IBM Corporation
Notices and disclaimers
© 2018  International Business Machines Corporation. No part of this document may be reproduced or transmitted in any form without written permission from IBM.
U.S. Government Users Restricted Rights — use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. This document is distributed “as is” without any warranty, either express or implied. In no event, shall IBM be liable for any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of opportunity. IBM products and services are warranted per the terms and conditions of the agreements under which they are provided.
IBM products are manufactured from new parts or new and used parts. In some cases, a product may not be new and may have been previously installed. Regardless, our warranty terms apply.”
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice
Performance  data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. 
References in this document to IBM products. Performance  data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. 
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. 
Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.
It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer follows any law.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products about this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM expressly disclaims all warranties, expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a purpose.
The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right.
IBM, the IBM logo, ibm.com and [names of other referenced IBM products and services used in the presentation] are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at:

3. Read me first…
This document contains important and valuable educational material.
It is intended to provide additional clarity on topics covered in other educational assets.
It stands on its own and does not replace other educational material.

4. Topics Included: Computed Fields Object Model Characteristics
Site Synchronization
AFCON
AURA & Rule Based Security Model
BASIM

5. Computed Fields

6. WYNTK about data types for computed fields - Including Data Types, Return Values and When to Use Each Value Type

7. Object Model Characteristics

8. Object Model Characteristics
Content for Object Model Characteristics is taken from the IBM Knowledge Center: Home>OpenPages GRC Platform 8.0.0>…>Object Model
The standard (out-of-the-box) object model consists of certain characteristics.
The following list describes key characteristics of object models:
The business entity and sub-process object types are recursive.
The Issue, Signature, File, and Link object types can be associated to any primary object type.
Object types can contain single valued and multi-valued enumerated string data types.
Note Depending on your configuration, the object model that you see may be different.

9. Object Model Characteristics
Table 1 lists the primary object types that are shared across all solutions. The list is followed by Figure 1 showing the object model and relationship among primary objects. All objects have a direct parent-child relationship.
Table 1. Primary Object Types
Object Type
Label
SOXBusEntity (recursive)
Business Entity
SOXProcess
Process
SOXSubprocess (recursive)
Sub-Process
SOXRisk
Risk
SOXControl
Control
SOXTest
Test Plan
SOXTestResult
Test Result
RiskAssessment
Risk Assessment

10. Object Model Characteristics
Figure 1. Primary Object Relationships

11. Object Model Characteristics
Table 2 lists the secondary object types that are shared across all solutions. The list is followed by Figure 2 showing the secondary objects without links to the primary objects because the joins are formed in the reporting tool.
Table 2. Secondary Object Types
Object Type
Label
SOXIssue
Issue
SOXTask
Action Item
SOXSignature
Signature
SOXExternalDocument
Link
ProjectActionItem
SOXDocument
File
Milestone

12. Object Model Characteristics
Figure 2. Secondary Objects
This model represents the basic relationship of objects within IBM® OpenPages® GRC Platform. For the exact relationships for your own system either
obtain the object model diagram that was created during the system installation process or examine the object relationships from the Administrator > Object Types menu.
Parent Topic: -> Object Model

13. Site Synchronization (Site Synch) WYNTK

14. Site Synchronization (Site Synch) Concept
Site Synchronization (SiteSync) is an automated method of updating GRCM data by looking at the change history (audit history) of the source data.
It is used mostly in the Library – Entity paradigm, where master data is maintained under Library entity and data specific to each business unit is copied from the source entity to the business unit entity .

15. AFCON: Automated Forms Configuration WYNTK

16. AFCON: Automated Form Configuration
AFCON stands for Automated Forms Configuration, and was designed to be used as an efficient way of completing initial forms (schema and profile) configuration. AFCON reads a Microsoft® Excel® format schema template and generates OP-XML files that can be loaded via ObjectManager (which comes with the OpenPages application).
After these files are loaded, the customer schema is in place. AFCON is a standalone Java program.

17. AFCON: Automated Form Configuration
AFCON uses as one of its inputs an XML file which specifies the current configuration of the system. This XML file is generated using ObjectManager to dump the current configuration.
AFCON provides the ability to specify global configurations such as dependent picklists and field dependencies, as well as items which are not global, such as the views themselves and field attributes within a view.

18. AFCON: Automated Form Configuration
AFCON provides the ability to specify items such as object fields, field and display types and standard UI views such as the FLV, Grid, Detail, Activity and List views. It also provides the ability to specify definitions for filters, computed fields, standard UI classic and dashboard home pages, field dependencies and dependent picklists, security rules and reporting fragment and classifier fields.
AFCON also provides the ability to specify Cognos dimensional model items such as object type dimensions, recursive object levels, as well as date dimensions and date dimension associations

19. AFCON: Automated Form Configuration
AFCON does not provide the ability to specify new objects together with their icons and relationships, Cognos reports, users, role templates or role template assignments or profile assignments. It cannot be used to specify GRC instance data.
Searching values in AFCON: The condition that will be searched in the desired field, For enumerated strings this can be an alt-entered seprarated list of enumerated values. For user fields this can be either a user id or the special test “##{logged in user}##”. For text fielsd, this can be a text string with or without a wild-card operator (‘%’). For numerical values or dates, this could be a number, or two pipe-separated numbers (e.g. 1|100).

20. Role Based Security Model and AURA

21. AURA – Automated User Role Assignments
AURA stands for Automated User Role Assignments, and was designed to be used as an efficient way of completing bulk user and user-role assignment loads.
AURA reads the standard template and generates OP-XML files that can be loaded via the Object Manager (which comes with the OpenPages application). After these files are loaded into the system, users are loaded and assigned to their security domains and designated roles and context points.
AURA DOES NOT create Role Templates or entities. AURA is a standalone Java program.
The AURA Template is an Excel spreadsheet which captures the specifics of your security implementation. You can maintain a view a high-level view of your organizational structure, role template definitions and users all in one reference document.
As mentioned earlier, AURA does not create or modify entities.

22. Role-based security model
A role-based security model provides a way for administrators to control user and group access to objects that are under a defined security point within the object hierarchy according to the role the user or group is expected to perform within the organization. Typical security points are business entities, processes, or sub-processes (can also be set at lower security point levels if wanted). The image shown on the right shows how various users and groups can have different permissions set for accessing business entities (a defined security point in the object hierarchy) and objects that are under a specific hierarchy. Based on the type of security context points defined in your security model, such as Business Entity, Process, Control Objective or Risk Assessment, you can use a role template to define a set of permissions for a set of object types.

23. Role-based security model (continued)
Based on the type of security context points defined in your security model, such as Business Entity, Process, Control Objective or Risk Assessment, you can use a role template to define a set of permissions for a set of object types.
For each role template that you define, you can set the following:
• Access control (Read, Write, Delete, Associate) for each object type included in that role.
• Application permissions for the role. For information about the various application permissions
Important: These application permissions do not include administrative group and user security management permissions, such as resetting passwords, assigning roles, adding users, and so forth.
By assigning a role (an instance of a role template) to a user or group at specific security context point In the object hierarchy, you can control access to objects. Roles represent the usual or expected function that a user or group plays within an organization. Some examples of roles are: Finance Reviewer, Tester, External Auditor, System Administrator, Control Owner, Risk Assessor.
When you assign a role to a group or user, the security settings of that Role Template are acquired by that group or user and permissions are automatically granted, per the role template definition, to all objects below the specified security point. For example, if a role were assigned to a user for a business unit (security context point), access control for specific object types under that security point would be set in the object hierarchy. Object types that were excluded from the role would be hidden from view, object types that were included would be visible and could be accessed by users and groups assigned to that role.
So that you can have a clear and accurate understanding of which users and groups have access to what and with which permissions, and what access control modifications were made in the system, you can run a variety of reports to view this data.

24. Role-based security model (continued)
For example, if a role were assigned to a user for a business unit (security context point), access control for specific object types under that security point would be set in the object hierarchy. Object types that were excluded from the role would be hidden from view, object types that were included would be visible and could be accessed by users and groups assigned to that role. So that you can have a clear and accurate understanding of which users and groups have access to what and with which permissions, and what access control modifications were made in the system, you can run a variety of reports to view this data.

25. BASIM

26. IBM BASIM Project Management Components
The IBM Business Analytics Solutions Implementation Method (BASIM) is a step-by-step guide to conducting a complete development lifecycle for IBM Business Analytics solutions. It contains structured steps, development activities, roles and responsibilities, guidelines, proven practices, tips & trouble shooting documents.

27. IBM BASIM

28. IBM BASIM

29. IBM BASIM

30. IBM BASIM

31. IBM BASIM

32. IBM BASIM