1. IBM OpenPages Governance Risk & Compliance
WYNTK – IBM Open Pages Fundamentals
Updated

2. 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:
© 2018 IBM Corporation

3. WYNTK…
This document contains important and valuable educational material.
In some cases it provides additional clarity on topics covered in other educational assets.
It stands on its own and does not replace other educational material.

4. OpenPages Governance Risk & Compliance Platform
Vendor Risk
Reputational Risk
IT Risk
Audit
Predictive Analytics
Regulatory Change
Operational Risk
Advanced Visualizations
Policy
Management
Model Risk
Capital
Modeling
Business Continuity
Conduct Risk
Design Thinking
Cognitive
Key capabilities
Loss Event Management
Issues Management
Scenario Planning
Reporting
Workflow
Comprehensive API
Perform Administrative
Tasks (On-premises only)
Risk and Control Self Assessments (RCSA)
Policy Management
Key Risk Indicators

5. IBM OpenPages GRC Platform
Operational Risk
Management (ORM)
Internal Audit
Management (IAM)
Financial Controls
Management (FCM)
Policy & Compliance
Management (PCM)
IT Governance (ITG)
Regulatory Compliance Management (RCM)
Model Risk Governance (MRG)
Vendor Risk Management (VRM)
Patented Flexible Performance Architecture
User Level Configurability
No “Custom” Code
Core GRC capabilities are supported by a central, common repository. We sell these as modules, and they are supported by a common repository. 5 5 5

6. OpenPages GRC Platform
Counter Fraud
& Financial Crimes
Operational Risk
Financial Risk
IT Risk & Security
Integrated Operational Risk, IT Risk, Audit and Regulatory Compliance Management
IBM® OpenPages® Governance, Risk and Compliance (GRC) solutions provide deep insight into enterprise-wide risk and compliance activities, enabling companies to increase business performance and adapt to new regulatory challenges with a proactive, approach to risk and regulatory change. Many leading companies have chosen IBM OpenPages solutions to provide a scalable, integrated GRC architecture that helps them to eliminate siloed risk management practices, increase efficiency and enable intelligent investment prioritization.
Solutions
Operational Risk Management
Regulatory Compliance Management
Policy & Compliance Management
Internal Audit Management
IT Governance
Vendor Risk Management
Financial Controls Management
Model Risk Governance
Capabilities
Risk and Control Self Assessments
Policy Management
Key Risk Indicators
Loss Event Management
Issues Management
Scenario Planning
Reporting
Workflow
Comprehensive API
Questionnaires
Benefits
Reduced risk exposure
Holistic view of enterprise-wide risk
Superior business intelligence for risk aware decision making
Data integration and aggregation
Improved time to value

7. Tutorial Financial Controls Management (FCM) Object Model
(4 slides)

8. OpenPages Object Modules
Facilitator Notes:
This is an organizing framework of the OpenPages modules / object models that will be discussed in this module.
This is an organizing framework of the OpenPages modules / object models that will be discussed in this module. .

9. Financial Controls Management (FCM)
Reduces the time and
resource costs associated
with ongoing compliance for
financial reporting
regulations.
FCM combines powerful document and process management with rich interactive reporting capabilities in a flexible, adaptable easy-to-use environment, enabling CEOs, CFOs, managers, independent auditors and audit committees to perform all the necessary activities for complying with financial reporting regulations in a simple and efficient manner.
FCM combines powerful document and process management with rich interactive reporting capabilities in a flexible, adaptable easy-to-use environment, enabling CEOs, CFOs, managers, independent auditors and audit committees to perform all the necessary activities for complying with financial reporting regulations in a simple and efficient manner.

10. FCM Object Model
Note: There are no new or different “additional object types” or “children objects” for FCM.

11. Object Types SPECIFIC to FCM
Accounts correspond to the line items on a financial report.
A sub-account represents a smaller, more targeted line item that is part of a larger parent account.
The Assertion object is used to link Control objects to Account (or Sub-account) objects.

12. Parent Relationships
(3 slides)

13. Primary Parent Association https://www. ibm
When a child object is added from the Detail View page of a parent object, it is considered to be a primary child and is automatically associated to that parent object upon creation. Object types that are allowed to have multiple parent objects through association can have only one primary parent association. For example, if Control-01 was added from the Detail View page of Risk-01 and was also associated to Risk-02, Control-01 would have two parents: Risk-01 and Risk-02. However, only Risk-01 would be considered the primary parent of Control-01. A primary parent object is identified in some parts of OpenPages in the application by the Primary Association icon, which is displayed next to that parent object on a child object’s Detail View page.

14. Primary Parent Association https://www. ibm
When primary associations are enabled:
You can change an object’s primary association from one parent object to another by reassigning the primary parent.
Any re-assignment of the primary association from one parent object to another parent object is reflected on the Change History pane of an object.
A child object with multiple parents that is disassociated from its primary parent object is automatically re-assigned a new primary parent.
Cascading operations on objects (such as sign-off, delete, locking or unlocking), are based upon primary associations.
Objects with multiple parents that are not included in a cascade delete operation (such as issues and action items) are automatically re-assigned a new primary parent.
Copy operations on objects will duplicate existing associations (including primary associations) whenever possible. A new primary parent association is also assigned to the first association.
Changing the primary parent association An object can have only one primary parent. If an object has multiple parent objects, you can change the primary association from one parent object to another one.

15. Absence of Parent Business Entities https://www. ibm
You may want to create a new top-level Business Entity because it currently does not have any parent business entities. This can be accomplished by navigating to the Business Entity folder list view or the Business Entity filtered view list, then selecting Business Entities under the Organization top level menu. Once there you can click on the "add new" button to create the Business Entity.

16. Extending OpenPages
(4 slides)

17. Extending OpenPages

18. Extending OpenPages

19. Extending OpenPages

20. Extending OpenPages

21. Tutorial: IBM OpenPages Features and Functions Dynamic Field Behavior
(7 slides)

22. Dynamic Field Behavior
Administrators are able to configure field behavior so that its behavior (visible, editable or required) is dynamically based upon some value selected by a user in another field or set of fields. This is a system-wide configuration, not by profile.
Considerations:
Dependent fields cannot include system fields or be defined on custom forms.
Controller fields must be enumerated string lists (single or multi-selectable).
Computed fields can only have a behavior of visible.
Dynamic fields can also be Actor fields
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

23. Computed Fields
Computed Fields can be used to dynamically calculate a value based on other fields every time an object is viewed.
When values are persisted:
The value is calculated only when fields on an object are saved; dynamically computing the value for each view is unnecessary.
Persisting a calculated value based on many other objects allows you to use that value in CommandCenter reports more efficiently.

24. Field Dependency Behavior
When defining field dependency behavior, the following actions can be defined:
Select this value…
If you want….
Required
To require the user to enter a value in the dependent field only if the configured value of the controlling field I selected. IF the user tries to save the page without entering a required value, a message is displayed saying the filed is required
Editable
The user is able to modify this dependent field only if the controlling field is selected. Otherwise, the dependent fields will be read only.
Visible
The dependent filed is to be displayed to the user only if the controlling field is selected. Otherwise the dependent fields will be hidden from view.
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

25. Dynamic Field Behavior - Example
When Risk Category = Internal
AND
Risk Subcategory = Internal – High
Explanation field becomes visible and required
Dynamic picklists need to first be created:
The Risk Subcategory field is a dependent picklist to the Risk Category field. Based on what is selected in the controlling field, Risk Category, only specific field values are displayed.
Facilitator Notes:
n/a
Slide Text:
Red Asterisk * at the end of a field label indicates the field is required.
OpenPages Virtual Boot Camp OpenPages Features and Functions

26. Dynamic Field Behavior - Example 2
When Inherent Impact = High OR
Inherent Likelihood = High
Additional Description explanation field becomes required
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

27. Demo 3 Dynamic Field Behavior
Using SoxRisk Object we have the following Field Dependencies
We will select Reason for Acceptance and choose edit to see how a field dependencies are built.

28. Dynamic Field Behavior Screen Shot

29. Tutorial: IBM OpenPages Features and Functions Triggers
(9 slides)

30. Triggers
The GRC Platform provides a trigger framework that allows the implementation and deployment of custom business logic and rules, and the capability to plug them into a live IBM OpenPages deployment.
Out of the box triggers are available in the ORM module.
A trigger consists of the following two parts, a rule and an action:
A Rule is a condition that applies to the operation being executed and the parameters involved in the operation. Common examples of rules:
The operation being executed
Type of object
Condition on a property of the object(s) in context
An Action is executed if the current operation satisfies the rule defined for the trigger. These actions can perform any business logic. Common examples of actions:
Throw a validation error
Create a new object
Delete an existing object
Reset or modify properties of the object
Modify properties of a related object
Execute a report or program
Facilitator Notes:
n/a
Slide Text:
The Platform provides a trigger framework that allows the implementation and deployment of custom business logic and rules
A rule is a condition that applies and there are defined parameters.
An action is executed if the current operation satisfied the rule defined for the trigger.
This section describes the triggers which are available for this Module. OpenPages Modules 6 R1.1 Trigger Details provides additional details on the triggers described here.
ORM 6 R1.1 includes triggers on the following object types by default:
Loss Impact
Loss Recovery
KRI Value
KPI Value
Risk
OpenPages Virtual Boot Camp Introduction to OpenPages Operational Risk Management (ORM)

31. Triggers (cont’d.)
This framework is built in Java and generic enough to allow the implementation of any business logic based on existing functionality available through the platform’s Software Development Kit (SDK).
The current form of a trigger is a piece of code that can be injected before or after the execution of an operation is performed on the Platform. This piece of code can perform anything that can be written in Java.
The underlined point is key. “Technically” there isn’t much that we can’t do with a trigger, but there are major caveats to this:
Cost
System Performance
Length of Implementation
Complexity of Solution
Supportability
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

32. Triggers (cont’d.) Most common triggers follow these characteristics:
Are only available for SDK operations.
Must be written in Java. Only triggers written in Java are currently supported in the IBM OpenPages product.
Can invoke any program or module that can be invoked from Java.
Can be used with all functionality that is supported by the OpenPages Platform SDK.
Have access to the current user’s IBM OpenPages Platform SDK session.
Are executed within the existing transaction boundary of the original operation.
Can be configured to execute before or after the original operation execution.
All dependencies need to be implemented or provide as part of the custom trigger package delivery. These dependencies can include custom jar file and configuration files, etc.
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

33. Triggers (cont’d.)
Triggers can execute in any of the following scenarios
Creating an Object
Updating an Object
Associating Objects
Disassociating Objects
Deleting Objects
Copying Objects
Searching for Objects
As mentioned, the action of the trigger can essentially be anything, but typically one of the following actions are taken:
Field value on an object is changed
An is sent
An object is locked or unlocked
A signature is applied
A picklist is updated
Associated objects are moved, deleted, copied, or changed
Field based security is implemented
Custom logic is executed
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

34. Triggers (cont’d.)
The most important point to remember is not to misuse triggers. Triggers execute as part of the core functionality of the GRC Platform and caution should be exercised when implementing.
Performance is one of the key factors in a successful client implementation. Since triggers operate serially in the system, a slow trigger will slow down the user’s perception of the application speed. For this reason, triggers should be used sparingly and logic should be focused and as simple as possible.
Triggers can operate before an Operation (PRE) or after an Operation (POST).
Use triggers before (PRE) the execution of the method when:
All actions that will calculate and set a new value on the object must be persisted.
All validation requirements that will throw an error in the UI.
Any requirements that perform business logic and will either display an error on the UI or must be persisted before or as part of the original operation, should be executed in the PRE phase of the operation.
The advantage of using PRE triggers is that data can be processed before it is persisted.
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

35. Triggers (cont’d.)
Use triggers after (POST) the execution of the method when all actions that require the information from the current object to be present in the database after the operation for the business logic to work correctly.
Cognos-based computation that depend on the new values of the properties of the object should not be used in triggers. These new values are not available to Cognos at the time of execution of the triggers.
Often times during the design phase, a well designed trigger can eliminate the need for a Cognos based computed field.
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

36. Risk Computation Trigger
This trigger calculates and persists the Inherent and Residual Risk Rating, and Inherent and Residual Risk Exposure field values on the Risk object.
Facilitator Notes:
n/a
Slide Text:
The Risk Computations trigger calculates and persists the Inherent and Residual Risk Rating, and Inherent and Residual Risk Exposure field values on the Risk object. The triggers are enabled when a Risk is created or updated.
OpenPages Virtual Boot Camp Introduction to OpenPages Internal Audit Management (IAM)

37. Loss Event Life Cycle Trigger
The Loss Event Life Cycle triggers are configured to calculate and persist four fields on the Loss Event object when related fields are created or changed on any child Loss Impact and Loss Recovery records.
Facilitator Notes:
Slide Text:
The Loss Event Life Cycle triggers are configured to calculate and persist four fields on the Loss Event object.
When Loss Impact and Loss Recovery amounts are created or changed the trigger calculates and rolls the amounts to the parent Loss Event record.
OpenPages Virtual Boot Camp Introduction to OpenPages Internal Audit Management (IAM)

38. KRI Life Cycle Trigger
The KRI and KPI Life Cycle triggers are configured to calculate and persist field values on the KRI and KRI Value object types.
KRI
KRI Value
Facilitator Notes:
Slide Text:
OpenPages Virtual Boot Camp Introduction to OpenPages Internal Audit Management (IAM)

39. Tutorial: IBM OpenPages Features and Functions JSP and Batch Utilities
(2 slides)

40. JSP Utilities & Helpers
JSP Utilities include any custom web form or tool that we develop.
These utilities can solve many challenges, but they are commonly used in the following scenarios:
To simplify a User interaction in the system
To replace an Activity View
To launch Ad-Hoc operations that span across multiple objects
An example would be to create an issue, create an action plan on that issue, complete predefined fields, and send an to a user all with one click
To launch a new business process
JSP Utilities (or reports) & JSP Helpers are often discussed in the same sentence. The core difference is that a Utility (or report) is launched through the “Reports” menu in the system, while a “Helper” is launched from a link present in an object view.
The Object Identifier is passed into a helper, which allows the tool to “scope” to the level of that object.
By using Utilities & Helpers, an engineer can also develop a solution that can “Bypass Security”, which can temporarily elevate a user’s permissions temporarily within the confines of the tool.
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

41. Batch Utilities
Batch utilities are used to manage long running process that happen on a repeatable schedule
Batch utilities make use of the out of the box Notification Manager along with the Windows Schedule to start processes. In AIX, CRON is used to schedule the operation
As with JSP Utilities, the options available for batch processing are limitless, but typically are reserved for:
Quarterly cleanup operations
Large Scale mailing operations
3rd party service integration
A 3rd party service can grab data from a given system and place the data in a reachable location. OpenPages can then write a utility that runs on a schedule to process this data and cleanup as necessary.
Automated User Management
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

42. Tutorial: IBM OpenPages Features and Functions Workflow
(2 slides)

43. Workflow
IBM OpenPages has integrated application, IBM BPM Workflow Engine, into the Platform to develop, manage, and remediate workflow processes.
IBM OpenPages includes a “Workflow Authors Guide” so clients who choose to do so can develop their own process flows. This also provides a good view into the workflow engine.
Included with the package is the IBM Business Process Manager for OpenPages
This is an Eclipse extension that allows the graphical design of process flows
It is a standalone utility that can be run from any system that can access an OpenPages instance
Authoring workflows is typically an operations reserved for Power Users with some background in programming.
notifications (either automatic out-of-the-box or custom) sent to users assigned tasks in a work flow are optional
Facilitator Notes:
n/a
Slide Text:
OpenPages Virtual Boot Camp OpenPages Features and Functions

44. IBM BPM Workflow Engine
OpenPages uses a Workflow engine integrated for the workflows. Using this engine, users click on the process and the button designed for the workflow.
The IBM BPM engine in OpenPages and this workflow engine work with system tasks (“wheel” symbol) and user coach views (“user” symbol).
When a user in OpenPages activates the workflow, it navigates them through it. When it reaches a coach view node, it presents a screen to the user which they need to validate. The “Reject “or “Approve” buttons would be available options for the user.
Note: “OK” and “Cancel” button options would be available to advance the workflow for custom applications such as the example shown above, instead of “Reject” and “Approve” buttons

45. OpenPages Fundamentals Implementation and Configuration
(2 slides)

46. IBM OpenPages Implementation – Phases
Design Phase
Gather Requirements
Assessment effort
Requirement sessions
Develop and Deliver Blueprint
Develop Scope and Estimate
Implementation Phase SOW
Obtain Sign offs from Client
Blueprint
Project Plan
Implementation Phase Scope
Specifications
Schema
Manage Infrastructure Work stream
Design Phase Installation
Environment utilization guidance
Implementation Phase
Manage Implementation Workstreams
Configure the platform / solution
Develop / deliver customizations
Develop / deliver reports
Support installation / deployment
Support test preparation (data)
Risk / Quality management
Identify technical or functional issues
Confirm quality through testing
Support Testing / Defect Resolution
Provide Training
Formal training products
Knowledge Transfer during project
Complete Documentation
Support “Go-Live”
Transition to Business as Usual Support

47. IBM OpenPages Implementation: Stages Definition
Scoping – this incorporates all of the activities and products that are completed prior to agreement with the client to move forward on the project. Most of the time this agreement will be prior to Contracts being signed, but sometimes it might be as part of a paid piece of work (for instance, scoping of a Phase 2 of a project)
Definition – Once the decision on scoping and contractual matters (either a Master Agreement or new Schedule) are addressed then detailed requirements gathering must occur. This stage is called definition and should supply the needed business and technical requirements as inputs to the solution design.
Design – this is the stage where the requirements are analyzed (both functional and non functional) and a solution design is completed which is agreed with the client. The design will be influenced by a number of factors, including (but not limited to); initial scope, agreed budget etc. The other outcome from the Design work would be a revised and more detailed scope and estimate. The agreement on a Design and what is and what isn’t achievable given the project constraints (i.e. budget, time, resources) is fundamental to ensuring Scope (time and budget) is understood and agreed.
Build – this is the phase where the work to deliver the configuration and any custom deliverables is conducted. This build process may be a re- iterative one with the next stage . . .and could be completed a number of times (such as when a delivery of ‘build prototypes’ occurs).
Test – this is the stage where the deliverables are tested by the Client to ensure that they meet the requirements as agreed would be completed in the Design phase. This phase could also be conducted re-iteratively, depending on whether a phased prototyping approach is taken. The end of the Test stage is when the client has signed off the Tests as completed and the solution is ready for Deployment.
Deploy – this is the stage where the solution is deployed to the business users. This may be initially to a Pilot group (who are not completing User Acceptance Testing – as this should have been completed in the Testing stage previously), but who are running the solution as either a ‘live’ system (i.e. early adopters) or as a parallel system to their current approach; or rolled straight out to the User Community.
Support – this stage is when the system is officially handed over for ‘Business as Usual’ for both the OpenPages support team and the client’s support team.

48. AURA: Automated User Role Assignments WYNTK
(2 slides)

49. 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.

50. AURA: Automated User Role Assignments
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.

51. ObjectManager WYNTK
(2 slides)

52. ObjectManager
The ObjectManager tool provides a command-line interface (CLI) that you can use instead of the application graphical user interface to load data into the IBM OpenPages GRC Platform repository.
With the ObjectManager tool, you can perform the following tasks:
• Import (load) data, such as objects and configuration data, into the OpenPages GRC Platform repository.
• Export (dump) filtered or unfiltered data from the OpenPages GRC Platform repository. You can use this
functionality, for example, to migrate environments and data from one computer to another one in a
multi-deployment environment.
• Batch-load multiple loader files in a single session.
Only a Super Administrator has full access to ObjectManager operations. .

53. ObjectManager (continued)
An alternative to using the ObjectManager tool is to use Administration > Import Configuration. You can use it to load system data, user-related information, and instance data. The rules that apply to loader files that are imported with the ObjectManager tool apply also to Import Configuration.
The ability to import ObjectManager XML files through Import Configuration is controlled by the
/OpenPages/Applications/GRCM/Environment Migration/Allow ObjectManager XML registry setting.
It is disabled by default.

54. FastMap WYNTK
(1 slides)

55. FastMap
FastMap is a productivity tool that works with the IBM OpenPages GRC Platform export feature, and automates the importing and batch processing of object instance data into OpenPages GRC Platform.
The FastMap tool uses a data load template (a Microsoft Excel workbook in .xls or xlsx format) to capture data for import.
When you import data into OpenPages GRC Platform, FastMap validates the data andthen, if no errors are found, populates the repository with the new or updated records.

56. Site Synchronization (Site Synch) WYNTK
(1 slides)

57. 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 .

58. AFCON: Automated Forms Configuration WYNTK
(4 slides)

59. 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.

60. 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.

61. 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.

62. 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.

63. OpenPages Notifications
(1 slide)

64. OpenPages Notifications