\n",
" \n",
" 0 | \n",
" qa_w_prompt | \n",
" What is FastMap? | \n",
" FastMap is a productivity tool that helps automate the process of importing and batch processing object data into IBM OpenPages with Watson. It uses a data load template (a Microsoft Excel workbook in .xlsx format) to capture data for import, validates the data during import, and then populates the repository with the new or updated records. FastMap supports the import of Process and Risk objects but does not support the import of File and Signature objects or the system Comment field. It can also be used to import and export questionnaire template objects and their associated child objects, as well as the standard fields for questionnaire assessment instances. The tool includes options for cleaning up FastMap import templates stored on the server and controlling the formatting of exported data. Overall, FastMap helps increase efficiency and reduce manual effort required for data entry and management in OpenPages with Watson. | \n",
" 0.66 | \n",
"
\n",
" \n",
" 1 | \n",
" qa_w_prompt | \n",
" What is a Role Template? | \n",
" In IBM OpenPages with Watson solutions, a Role Template is a predefined set of permissions and access levels that determines the privileges granted to a user. It includes application permissions, Object ACLs (RWDA), and access to features and functions. There are several Role Templates delivered with the solutions, such as \"All Permissions\" and \"All Data - Limited Admin,\" and some solutions may include additional Role Templates with a subset of permissions. By default, these Role Templates provide administrative rights or limited admin rights for all object types available for the solution. Administrators can also create custom Role Templates to define specific application permissions and security context points. | \n",
" 0.66 | \n",
"
\n",
" \n",
" 2 | \n",
" qa_w_prompt | \n",
" What is the purpose of Object Reset? | \n",
" Object Reset is a feature in IBM OpenPages with Watson that allows administrators to automate the process of deleting, moving, renaming, copying, disassociating, or reassigning primary parents of objects based on specific criteria defined in a ruleset. This feature helps to streamline data management processes, reduce manual effort, and ensure consistency and accuracy of data across the application. It can also be used to prepare data for reporting purposes or to clean up obsolete or redundant data. | \n",
" 4.58 | \n",
"
\n",
" \n",
" 3 | \n",
" qa_w_prompt | \n",
" What is the purpose of Reporting Periods? | \n",
" Reporting periods in IBM OpenPages with Watson are \"snapshots\" of the current state of the repository, typically created at the end of a quarter or year during documentation phases. They allow users to view and report on data from past periods without being affected by changes made to the repository. This feature helps organizations maintain historical records and facilitates auditing and compliance activities. Additionally, object resets, which are rule-based operations contained in a ruleset, can be used to automatically modify objects within the repository during reporting periods. Overall, reporting periods provide a way to manage and organize data over time in IBM OpenPages with Watson. | \n",
" 0.69 | \n",
"
\n",
" \n",
" 4 | \n",
" qa_w_prompt | \n",
" List the system variables used in Expressions. | \n",
" 1. $APPLICATION_URL$ - A URL for OpenPages.\n",
"2. $COGNOS_URL$ - A URL for IBM Cognos Analytics.\n",
"3. $ApplicationText/application text key$ - Application text content.\n",
"4. $TASK_VIEW_URL$ - A URL to an object task view.\n",
"5. $System Fields:Task View URL$ - Deprecated. Use [$TASK_VIEW_URL$].\n",
"6. $Setting/OpenPages/...$ - A registry setting value.\n",
"7. $END_USER$ - The user name of the signed on user.\n",
"8. $TODAY$ - Today's date.\n",
"9. $DaysFromNow/field group:field name$ - A day count from today to a given date. | \n",
" 0.69 | \n",
"
\n",
" \n",
" 5 | \n",
" qa_w_prompt | \n",
" Provide the steps to configure Watson Assistant in OpenPages? | \n",
" 1. In OpenPages, go to Administration > Integrations > Watson Assistant.\n",
"2. Click on \"Add Watson Assistant\" and enter your Watson Assistant credentials.\n",
"3. Select the desired Watson Assistant service and click \"Save\".\n",
"4. Configure the integration settings, such as endpoint URL, authentication type, and API key.\n",
"5. Test the connection by clicking \"Test Connection\".\n",
"6. Save the configuration and start using Watson Assistant in your OpenPages applications.\n",
"\n",
"Note: Refer to the IBM OpenPages with Watson Version 9.0.0: Administrator's Guide (page 960) and IBM OpenPages with Watson Version 9.0.0: User Guide (page 110) for detailed instructions. | \n",
" 0.79 | \n",
"
\n",
" \n",
" 6 | \n",
" qa_w_prompt | \n",
" List the user administration permissions that can be delegated. | \n",
" There are six security management permissions that can be delegated to a security domain or user group administrator:\n",
"\n",
"1. Manage - allows the delegated administrator to create, modify, and associate users and groups.\n",
"2. Lock - allows the delegated administrator to lock a user account, preventing logon to the IBM OpenPages with Watson application from that account.\n",
"3. Unlock - allows the delegated administrator to unlock a previously locked user account.\n",
"4. Reset Password - allows the delegated administrator to reset passwords for users.\n",
"5. Assign Role - allows the delegated administrator to assign one or more roles to users and groups and to revoke a role from a user or group. Applies to security domains only.\n",
"6. Browse - allows the delegated administrator to view users and groups within that group. This permission is selected by default.\n",
"\n",
"Note: These permissions can be granted to a security domain or user group administrator to help distribute administrative tasks among multiple administrators. However, it is recommended to limit the number of administrators with these permissions to minimize potential errors or misuse. Additionally, it is important to ensure that the appropriate permissions are granted based on the specific responsibilities of each administrator. | \n",
" 0.74 | \n",
"
\n",
" \n",
" 7 | \n",
" qa_w_prompt | \n",
" What is the difference between PRE and POST position in Triggers? | \n",
" In Triggers, the position can be either PRE or POST. The PRE position indicates that the event occurs prior to the operation being performed by the system, while the POST position indicates that the event occurs after the operation has been performed but before the transaction is committed. Essentially, PRE triggers allow for modifications to be made to the data before it is persisted, while POST triggers allow for further processing of business logic after the operation has completed. Both positions are required for certain operations, such as deletes, associations, and disassociations for PRE, and creates and updates for POST. For more information, refer to the OpenPages 8.3 trigger development guide. | \n",
" 6.15 | \n",
"
\n",
" \n",
" 8 | \n",
" qa_w_prompt | \n",
" What are the features of Operational Risk Management in OpenPages? | \n",
" OpenPages Operational Risk Management includes the following key features:\n",
"\n",
"1. Loss Events: This activity involves tracking, assessing, and managing both internal and external events that could result in operational losses. Multiple impact events and recoveries associated with operational losses can also be managed.\n",
"\n",
"2. Risk and Control Self Assessments (RCSA): This activity involves identifying, measuring, and mitigating risks, testing and documenting internal controls.\n",
"\n",
"3. Key Risk Indicators (KRIs) and Key Performance Indicators (KPIs): These metrics can track performance metrics to potentially show the presence or state of a risk condition or trend.\n",
"\n",
"4. Scenario Analysis: This assessment technique is used to identify and measure specific kinds of risks, particularly low-frequency, high-severity events.\n",
"\n",
"5. External Loss Events: This feature provides the ability to import loss data from various sources like IBM FIRST Risk Case Studies, ORX, and ORIC loss databases into OpenPages Operational Risk Management for scenario analysis, benchmarking, and reports generation. Data can also be exported to analytic tools or capital allocation applications.\n",
"\n",
"6. Issue Management and Remediation (IMR): This activity includes issue creation and assignment, action creation and assignment, remediation performance, issue closedown, and reporting.\n",
"\n",
"7. Reporting, Monitoring, and Analytics: OpenPages Operational Risk Management offers reporting, monitoring, and analytics capabilities.\n",
"\n",
"Note: For more details on how to configure the RiskLens connector, refer to the IBM OpenPages with Watson Administrator's Guide. | \n",
" 1.15 | \n",
"
\n",
" \n",
" 9 | \n",
" qa_w_prompt | \n",
" What are the different administrator permissions that can be delegated to a user group administrator? | \n",
" There are six security management permissions that can be delegated to a user group administrator: Manage, Lock, Unlock, Reset Password, Assign Role, and Browse. These permissions allow the delegated administrator to perform various user-provisioning functions, such as creating, modifying, and associating users and groups, locking and unlocking user accounts, resetting passwords, assigning roles, and viewing users and groups within their respective groups. The Browse permission is selected by default. The specific permissions required for each user-provisioning function are outlined in Table 38 provided in the context. | \n",
" 1.11 | \n",
"
\n",
" \n",
" 10 | \n",
" qa_w_prompt | \n",
" What are the different access controls available for non-participants for a standard stage within a workflow? | \n",
" For a standard stage within a workflow, the different access controls available for non-participants are:\n",
"\n",
"1. Strict: Non-participants cannot view or edit objects at this stage.\n",
"2. Read: Non-participants can view objects at this stage, but cannot edit them.\n",
"3. Open: Non-participant's access depends on the standard access controls defined for their role template and security rules.\n",
"\n",
"Note: By default, access for a non-participant is based on the access controls defined by their role template and security rules. However, you can override these standard access controls for the workflow stage by selecting \"Override\" under \"Access Control\" in the workflow properties. This allows you to define custom access controls for non-participants at this stage. | \n",
" 1.24 | \n",
"
\n",
" \n",
"