1. IBM FileNet Case Manager 5.3.3 Case Builder Solution Development Steps for the Audit System

Chapter Organization

Note that most chapters in this book are divided into Parts featuring the core topics being covered, further organized by sections within.

This chapter contains the following four Parts:

Part 1 – Bill of Materials. This Part lists the prerequisite system and IBM Software components required to develop the IBM Case Builder solution used in this book as a base for the system integrations which are described in later chapters.

Part 2 – IBM Case Manager Solution Metadata. This Part covers the definition of the global elements of a Solution, Properties, Security Roles, Document Classes, and Business Objects.

Part 3 – Adding IBM Case Manager Case Types. In this Part, the Audit Master Solution Case Type creation procedure is described. Case types are used to specify the Case Solution tasks. This specification includes the required document classes attached to the task workflow, the task workflow steps, and the In-baskets and roles that are used for each of the Workflow steps.

Part 4 – Testing and Administration of the Audit Solution. This Part describes the development and administration of the Audit Solution after the initial deployment. This includes the deployment to a production system from a development environment.

Introduction

IBM Case Manager is now available as part of IBM Business Automation Workflow as described in the following.

Note

IBM Case Manager is still available as a standalone IBM FileNet product for upgrades.

For viewing an IBM Business Process Manager (BPM) process from Case Manager Builder after creating a case task based on an existing workflow process, the process is visible in IBM Process Designer. After you create a task from an existing process, you can click the Open Web Process Designer icon to edit the process in Process Designer.

To change an existing process or add a new process, you must open the process from the IBM Process Center, update or create the process, create a snapshot, and then make that snapshot the default. To view any new processes in the Add Task dialog box, click Refresh on the Select Process page.

The following video tutorial shows an example of this procedure:

www.youtube.com/watch?v=VtobZqwBh9g

(IBM BPM BAW – Moving to Web based Process Designer from Desktop Process Designer)

Access to the IBM Business Process Manager Work Dashboard is also available from the Case Manager Client.

The IBM Process Portal Work Dashboard is accessed from the Case Manager Client by adding the IBM Business Automation Workflow plugin to the IBM Content Navigator desktop.

The Work Dashboard tasks can then be viewed in a Content Navigator desktop which has the same functionality as the Business Process Management Process Portal.

When the IBM Business Automation Workflow plugin and IBM BPM V8.6.0 CF2018.03 are installed, the Workflow ➤ Launch Process action is added to the Action menu and the pop-up menu in the Browse view (configurable in the IBM Case Manager desktop).

This action can be used to launch an IBM BPM process from a document.

The Launch Process action can also be added to the menu in the Documents view for the IBM Case Manager Information widget.

The values for a property that is defined as type Business Object are now listed in the IBM case package solution PDF file along with the other case properties.

The Audit system is based on an article in the journal, Quality Forum, Volume 19 No. 3, September 1993. The Journal of the Institute of Quality Assurance. Pages 116–126. The Quality Audit Process, by Alan S. Bluck.

This article covers the department audits based on the ISO9000/BS5750 Quality Standard. Downloadable from

www.researchgate.net/publication/334094923_Case_Manager_Installation_04-05-2019

Part 1 – Bill of Materials

The installation steps required for IBM Case Manager 5.3.3 are covered step by step in the following free ResearchGate documents, downloaded using the DOI URL as follows:

https://doi.org/10.13140/RG.2.2.21708.16001

entitled “Case Manager 5.3.3 Installation on RHEL 8.0 with Content Navigator 3.0.6”

Click the Download file PDF command button in Figure 1-1.

Figure 1-1
Download the IBM Case Manager Installation document

This gives the downloaded document, entitled CaseManagerInstallationonRHEL8.0_V3.docx.

Note

As part of this installation, the requirement for the prerequisite IBM FileNet Content Engine Object Store Workplace Base Extensions for use with the IBM Case Manager installation is covered.

The step-by-step procedure for the installation of IBM Business Automation Workflow is available as a free download from the ResearchGate website, downloaded using the DOI URL as follows:

https://doi.org/10.13140/RG.2.2.27345.89440

entitled “IBM BAW 18.0 Installation phase1 preprint with install of IBM Workflow Center 8.6.1.19002”

Click the Download file PDF command button in Figure 1-2.

Figure 1-2
Download the IBM Business Automation Workflow Installation document

This gives the downloaded document, entitled

IBMBAW18.0Installation_phase1_preprint (1).docx

The IBM Case Manager Audit system components used are listed as follows with the IBM part numbers shown in brackets. These part numbers can then be searched and downloaded from IBM’s Software Access Catalog.

IBM Case Foundation V5.3.0 Linux Multilingual (CNPF8ML)

IBM Case Foundation V5.3.0 Windows Multilingual (CNPG0ML)

IBM FileNet Content Manager V5.5.0 for IBM Case Foundation V5.3.0 Multiplatform Multilingual eAssembly (CJ2VNML)

FileNet Content Manager V5.5.0 Quick Start Guide Multiplatform Multilingual (CNP8XML)

IBM FileNet Content Platform Engine V5.5.0 Linux Multilingual (CNP8ZML)

IBM FileNet Content Platform Engine V5.5.0 Windows Multilingual (CNP90ML)

IBM FileNet Content Platform Engine Client V5.5.0 Linux English (CNP93EN)

IBM FileNet Content Platform Engine Client V5.5.0 Windows English (CNP94EN)

IBM FileNet Content Search Services V5.5.0 Windows Multilingual (CNP9BML)

IBM FileNet Content Search Services V5.5.0 Linux64 Multilingual (CNP9CML)

IBM DB2 Enterprise Server Edition Restricted Use Quick Start and Activation V11.1 for Linux, UNIX and Windows Multilingual (CNB25ML)

Quick Start Guide for IBM WebSphere Application Server V9.0 (CNA8LML)

IBM WebSphere Application Server V9.0 (CND1AML)

IBM WebSphere Application Server V9.0 Supplements – Application Client (CND1CML)

IBM WebSphere Application Server V9.0 Supplements – IBM HTTP Server (CND1DML)

IBM WebSphere Application Server V9.0 Supplements – Web Server Plugins (CND1EML)

IBM WebSphere Application Server V9.0 Supplements – WebSphere Customization Toolkit (CND1FML)

IBM WebSphere Application Server Liberty (IBM Installation Manager install) (CND1GML)

IBM Installation Manager V1.8.5 for Linux x86_64 (CND0ZML)

IBM SDK, Java (TM) Technology Edition, Version 8 for Windows (CND15ML)

IBM SDK, Java (TM) Technology Edition, Version 8 for Linux (CND18ML)

Note

WebSphere 8.5.5 Fix pack 15 automatically installs and defaults the JDK to 1.8.

Starting the IBM Case Manager System

The ecmukdemo6 VMware system described in the IBM Case Manager installation earlier can be started after booting as follows, logging in as the root user.

Start the LDAP Servers

Find the desktop icon for the Instance Administration tool.

Figure 1-3
Click the Linux desktop Instance Administration tool for LDAP

Click to open the LDAP, IBM Security Directory Server Instance Administration Tool:

Figure 1-4
Select the **Start/Stop** command to start the LDAP servers

Click the Start/Stop command.

Figure 1-5
The **Start server** command is clicked to start the LDAP server

Click the Start server command button.

Figure 1-6
The **Start administration server** command is clicked

Click the Start administration server command button.

Figure 1-7
The **Close** command is disabled until the servers have started

After around six minutes, the Start complete pop-up window is displayed, then you can click the Close command button.

Start the IBM FileNet Case Manager Database

Type the commands as follows:

su - db2inst1

db2start

exit

From the command window in Linux:

Figure 1-8
The IBM FileNet and IBM Case Manager databases are started

Start the IBM FileNet Content Engine Web Service

From the command window in Linux, type the commands as follows:

cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

./startServer.sh server1

Figure 1-9
The IBM FileNet Content Engine web application is started

Start the IBM Case Manager Web Application

From the command window in Linux, type the commands as follows:

cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin

./startServer.sh server1

Figure 1-10
The IBM Case Manager web application server is started

Load the IBM Case Manager Builder Web Application

Using the URL as follows, we can launch the installed IBM Case Builder development tool:

http://ecmukdemo6:9081/CaseBuilder/designer/DesignerHome.jsp

The version of the IBM Case Manager and the available development IBM FileNet Object stores can be viewed using the About menu option in the IBM Case Builder web application as shown in Figure 1-11.

Figure 1-11
The ? ➤ **About** menu is selected to display the version details

The referenced IBM version is displayed in the About pop-up window as shown Figure 1-12.

Figure 1-12
The highlighted details show the Version and Object Store names

Part 2 – IBM Case Manager Solution Metadata

Adding a New Solution

A new solution for IBM Case Manager is created using the + icon on the top right of the logged in Case Builder screen.

Figure 1-13
The Add solution **(+)** icon is selected to create a new Case Solution

We will call this new solution Audit Master.

This is based on the article “The Quality Audit Process,” Quality Forum, The Journal of the Institute of Quality Assurance, Volume 19, Number 3, dated September 1993.

Figure 1-14
The Solution Name is entered and OK is clicked

The Solution can be based on a similar Solution template in the drop-down shown earlier. (Any deployed IBM Case Manager Solution can be saved as a template so that different Solution versions can be built and modified as required).

See www.ibm.com/docs/no/case-manager/5.3.3?topic=application-creating-distributing-case-manager-solution-templates.

Figure 1-15
The Add Property command is selected to add Global Solution properties

The solution is created by entering the required solution criteria using the tabs as shown earlier, working from left to right.

The first tab adds the globally referenced solution properties, which are used to create the required IBM FileNet Content Manager custom object attributes, which are generated from the Solution Template structure for each case created.

Adding Properties and Business Objects

Properties can be added or reused. In this solution, the New option is selected as shown in Figure 1-16.

Figure 1-16
The New menu item is selected to create a new Case Solution property

The Audit Case properties are added to form a list.

Figure 1-17
The list of Audit global properties

The Add Property command button is clicked to add the Audit system department properties for the ISO9000/BS5750 auditing of an organization’s department.

Figure 1-18
The property type is selected from a drop-down list

For each property added, as shown earlier for the DepartmentManager property, the type of the property can be selected from the usual IBM FileNet Content Manager property types, including the new Business Object property type.

A choice list of drop-down options can also be selected by first creating them, using the Manage Choice Lists command.

Figure 1-19
The Manage Choice Lists command

A Choice List consists of a displayed name and a separately held internal value. This allows a visible name, for example, New York, to be displayed, but the state code of NY can be stored.

The allowed length and, for numbers, valid range can also be entered for the property here. Also, a default value can be entered to facilitate the ease of entry.

The property can be selected to be a single value, or it can be defined to allow multiple values to be entered.

Adding Roles

The second tab allows the Solution Roles to be added. The security system uses the concept of a Role to define a group of users with the same access level to the Case Manager project. These roles are attached to the Case In-baskets used and also define functions available to a user with a specific Role. (A user can be allocated more than one Role, which extends and enhances the possible security matrix which can be defined.)

The Audit system Auditor Role is added with the option Personal selected.

The options to move work into the user’s Personal In-basket and the ability to reassign work to other users are selected using the tick boxes against each option.

Click the Roles tab.

Figure 1-20
The **Roles** tab is selected next to create the Case Security

The Auditor role is added with the access options shown in Figure 1-21.

Figure 1-21
The **Auditor** role is added with the options selected as shown

Note

It is good practice to click the Save command button at regular intervals to ensure you do not lose any edits during the Case Solution build.

The Pages tab is then selected to show the Assigned pages for the Role.

At this point, custom pages could be added (see later in this chapter for the details of the entry for the Pages tab).

Figure 1-22
The **Pages** tab is left with the displayed defaults

The Pages tab is next selected as shown in Figure 1-22.

This tab allows the Role to be linked with standard and custom created web widget pages.

(The prebuilt Work and Cases pages are shown.)

The Auditor’s Manager Role is added next to define a supervisor role for the Auditor Role users.

Figure 1-23
The Auditor’s Manager role is added with the assigned work in-basket

The two roles are displayed in Figure 1-24.

Figure 1-24
The list of Roles defined is shown

The next step is to define the In-baskets of the generated Audit cases.

Figure 1-25
The **In-baskets** tab (highlighted) is clicked to define In-baskets

The In-baskets tab is now selected.

Adding Properties to the In-Baskets for Each Role

The properties we defined earlier can now be selected to be added as attributes of the Case, visible in the In-baskets, as required.

Figure 1-26
The Global properties are selected as required for **All Assigned Work**

The required properties are selected by holding down the CTRL key and clicking using the left mouse button. Then select the OK command button.

Figure 1-27
The new In-basket properties are displayed after selection (highlighted)

In addition, the columns which can be sorted can be selected by setting a tick in the Sortable column boxes against the required property to be sortable.

Note

The In-basket Filters tab allows a property to be selected to be used to filter a subset of the Cases in the In-basket.

Repeat the preceding configuration for the other In-baskets.

Adding Document Class

The attached IBM FileNet Content Engine document class can be created using the IBM Case Manager Builder as shown in Figure 1-28.

Figure 1-28
The Documents tab is selected to add IBM FileNet document classes

The Audit Report document class is created as shown in Figure 1-29.

Figure 1-29
The new **Audit Report** document class details are added

Click OK to generate the new Document Class and then select the properties required.

Figure 1-30
The existing global properties created earlier are added

Click OK.

Figure 1-31
On selecting the properties, each one is displayed with options to be added

If required, for each property the attributes of Default value, Required, or Hidden can be selected, and then the OK command button can be clicked for each of the properties.

Figure 1-32
The updated property attributes are completed after each OK is clicked

Adding Business Objects

The Business Objects are a fairly recent IBM FileNet Content Engine property type which provides a compound property consisting of a collection of different properties which are tied together as one entity, that is, a structured data type that contains a collection of properties.

Figure 1-33
The **Business Objects** tab is selected and a **New** Object is created

The Business Objects tab is selected as shown in Figure 1-33, and then select the New menu option from the Add Business Object drop-down.

Figure 1-34
The new **Audit** Business Object is added

Enter the Business Object Name and enter a Description and click OK as highlighted in Figure 1-34.

Figure 1-35
The **New** menu item is selected for properties for the **Audit** Business Object

Click New to add a new property to the Audit Business Object.

Figure 1-36
**The Auditor Name** property details are entered

The next property is a DateTime type. Notice that each property is held more uniquely for the Case Solution by using the Case Solution prefix (set to AUD for the Audit Master solution) for the internal Unique identifier value. This enables separate properties to be stored in the IBM FileNet Content Store for different Case solutions where the visible name may be coincidentally set the same, but the Solution property attributes are required to be set differently.

Figure 1-37
The **Audit Date** property is added and flagged as **Required**

The Audit Date property is added to the Audit Business Object.

Figure 1-38
The **Auditor** property is added to the **Audit** Business Object

The Comments multi-value property is added to the Audit Business Object.

The complete list of properties added to the Audit Business Object is shown in Figure 1-40.

Figure 1-40
The completed list of properties added to the **Audit** Business Object

Figure 1-41
The **Audit** Business Object is linked to the **Department ID** property

Finally, the Department ID property is selected to represent a unique instance of the Audit Business Object.

Next, the Auditor Business Object is defined as shown in Figure 1-42.

Figure 1-42
The **Auditor** Business Object details are entered

The properties are added from the Global property list (defaulting the attributes).

Figure 1-43
The **Auditor** Business Object properties are selected and entered from the Global list

The Department Business Object is created next, with the Name and Description defined as shown in Figure 1-44.

Figure 1-44
The Department Name and Description are entered

The Department Business Object properties are selected from the Existing Global property list as shown in Figure 1-45.

Figure 1-45
The Department Business Object Global properties are selected

New properties are then also added as follows:

Department Emails (String, multiple values)
Department Procedure IDs (String, multiple values)
Department Procedure Names (String, multiple values)

(Note the red flag fields denote that the Required box is ticked for the property.)

Figure 1-46
The Department ID is also selected for the Department Business Object unique ID

The details of the properties for the Department Business Object are shown in Figure 1-47.

Figure 1-47
The Department Business Object property details

The Procedure Business Object is created next, with the Name and Description defined as shown in Figure 1-48.

Figure 1-48
The Procedure Name and Description are entered

The Procedure Business Object properties are selected as NEW properties as shown in the following and in Figure 1-49 (using the Add Property drop-down command button):

Procedure ID (Required) The Procedure ID
Procedure Publication Date (Required) The Procedure publication date
Procedure Version (Required) The issue/version number of the current version of the Procedure
Procedure Main Authors (Multiple values) (Required) The main authors of the procedure
Procedure Main Reference The procedure reference
Procedure Signatories (Multiple values) (Required) The authorization signatories
Procedure Reviewers (Multiple values) (Required) The main reviewers
Procedure Location The master copy location
Distribution List (Multiple values) The Owner email Distribution list
Procedure Name (Required) The Procedure Name

Figure 1-49
The New properties added to the **Procedure** Business Object

The Checklist Item Business Object is added next to the list of Business Objects.

Figure 1-50
The New properties added to the Checklist Item Business Object

The Checklist Item Business Object properties are selected as NEW properties as shown in the following and in Figure 1-51 (using the Add Property drop-down command button):

Checklist Item Ref (Required) The Checklist Item Reference
Checklist Item Audit Date Time (Required) The Checklist Item Audit Date Time
Checklist Item Department (Required) The Checklist Item Audit Date
Checklist Item Description (Required) The Checklist Item Description
(Maximum 1024 Characters Long)

Figure 1-51
The New properties added to the **Checklist Item** Business Object

In the preceding property list, we have changed the default String length for the Checklist Item Description from 64 characters to 1024 characters.

Note

In an IBM FileNet Content Store, Content Store Object String properties (for Object Classes such as Document and Folder) are limited to a maximum of 4000 characters for DB2 and SQL Server–based database systems and 1333 characters for an Oracle-based database system (as of IBM FileNet Version 5.5.x).

The details of the properties for the Checklist Item Business Object are shown in Figure 1-52.

Figure 1-52
The details of the properties for the **Checklist Item** Business Object

The summary of the properties for each of the Business Object and Solution properties is shown in Table 1-1, based on the Appendix A System Design (https://www.researchgate.net/publication/334095565_Case_Manager_Solution_Development).

Table 1-1

The list of Audit Master Solution properties

Global Solution Properties
Property Name	Property Type	Description
Department Number	String 64	The Department Number of the department to be audited
Department Name	String 64	The Department Name of the department to be audited
Department Manager	String 64	The Department Manager of the department to be audited
Audit Business Object
Auditor	String 64	The Auditor name
Audit Date	Date	The Audit Date
Audit Status	String 64	The Audit Status
Checklist Issue Date	Date	The Issue date of the checklist
Audit Report Date	Date	The report date
Follow-up Dates	Multi Date	The follow-up audit dates
Completion Date	Multi Date	The completion dates
Number of Nonconformances	Number	The number of nonconformances found
Audit References	Multi String 64	The list of audit trail references to other departments
Comments	Multi String 1024	The audit log comments (summarizing the main points found during the audit)
Audit Report GUID	String	The auditor report
Audit Frequency	Number	The Audit Frequency
Audit ID	Number	The Audit Reference Number ID
Department ID	Number	The Department ID
Auditor Business Object
Auditor ID	String 64	The Auditor’s Unique ID
Auditor Name	String 64	The Auditor’s Name
Auditor Department	String 64	The Auditor’s Department Number
Auditor Status	String 64	The Auditor’s status
Auditor Manager	String 64	The Auditor’s manager
Auditor Skills	Multi String 128	The list of the Auditor’s skills
Department Business Object
Department ID	Number	The Department ID
Department Telephone	String 64	The Department Telephone Number
Department Emails	Multi String 64	The Department email addresses
Department Procedure IDs	Multi String 64	The Department Procedure IDs
Department Procedure Names	Multi String 128	The Department Procedure Names
Department Manager	String 64	The Department Manager
Procedure Business Object
Procedure ID	String 64	The Procedure ID
Procedure Name	String 64	The Procedure Name
Procedure Publication Date	Date	The Procedure publication date
Procedure Version	String 64	The issue/version number of the current version of the Procedure
Procedure Main Authors	Multi String 64	The main authors of the procedure
Procedure Main Reference	String 64	The procedure references
Procedure Signatories	Multi String 64	The authorization signatories
Procedure Reviewers	Multi String 64	The main reviewers
Procedure Location	String 64	The master copy location
Distribution List	Multi String 64	The Owner Distribution list
Checklist Item Business Object
Checklist Item Ref	String 64	The Checklist Item Reference
Checklist Item Audit Date	Date	The Checklist Item Audit Date
Checklist Item Department	Number	The Checklist Item Department number
Checklist Item Description	String 1024	The Checklist Item Description

Adding Business Object Types As Case Properties

The Business Object types we created earlier have to be added back into the Global properties section as Case properties of the Solution as follows in this section.

See “Adding and modifying business objects”:

www.ibm.com/docs/en/case-manager/5.3.3?topic=solution-adding-modifying-business-objects

In the properties tab of Case Builder, select the Business Object type.

Figure 1-53
The **AuditObj** property of type Business Object is added to the Solution

The AuditObj property is automatically assigned as a multi-value object and is selected as an Audit Business Object type from the drop-down list of Business Objects which we created earlier.

Next, we will add the other Business Object types, similarly, as Case properties as shown in the list in Figure 1-54.

Figure 1-54
The list of the Case Solution Business Object properties is highlighted

Part 3 – Adding IBM Case Manager Case Types

There can be any number of Case Types added to an IBM Case Manager Solution. These are used to define the specific Workflows and their associated steps and for each step the In-baskets where the individual Cases can be viewed and opened.

Adding Case Types

In this next step, we can now create the Audit Master Solution Case Types.

Case types are used to specify the Case Solution tasks. This specification includes the required document classes attached to the task workflow, the task workflow steps, and the In-baskets and roles that are used for each of the Workflow steps.

For each Case Type, the following attribute elements can be created/edited:

The name and description for each case type, including the unique task identifier.
The document class which, when stored in the IBM FileNet Object Store, can initiate the task workflow.
The option for a user to start additional custom tasks for the case.
The page types to use. The default layout for the page can be selected for the Add Case, Split Case, and Case Details function pages.
Additional properties can also be assigned to the case type.
Case Folders can be added for a specific Case Type to store the associated documents.

See www.ibm.com/docs/en/case-manager/5.3.3?topic=types-case for the full description of the usage of the IBM Case Manager Case Types.

The Case Type tab is the last tab which is navigated, in order, from the top to the bottom of a Tree menu, to add the required Case Type properties, Views, Case Folders (if required), Stages, Rules, and Tasks.

Auditing Department Task

The Audit Department Task is added as follows.

Figure 1-55
The highlighted attributes for the **Audit Department** case type are added

The Case Type Properties Tree menu item is selected to add the required properties for the Task.

Figure 1-56
The **DepartmentName** and **DepartmentNumber** properties are added

Figure 1-57
The existing **Completion Date** property is added

Figure 1-58
The Business Object type properties are selected for the Audit Case Type

Add the required Business Objects to the Audit Department Case Type. In this case, they are all set with the Required option. The OK All command button can then be selected to update all the open property attribute values.

Figure 1-59
The Required Option is selected for all the Business Object properties

The Save command can be used to save all the Solution build updates at this point.

Figure 1-60
The completed list of Audit Department Case Type properties

The Views tab is selected, and the related Case summary properties are added from the list as shown in Figure 1-61.

Figure 1-61
A selected Case Property (the internal Case Identifier in this example) is added

Figure 1-62
The list of selected Summary Case properties to be viewed

The Audit Business Object properties are added next, to the Case Summary view.

Figure 1-63
The highlighted Audit Business Objects are selected for the summary view

Next, we select the Properties Layout tab to define the layout of the displayed property values.

Figure 1-64
The new View Auditor Department is created

On clicking the OK command in Figure 1-64, the Audit Department entry line for the new View is shown, and the icon highlighted in Figure 1-65 appears on using the mouse-over on this new entry line.

Figure 1-65
The highlighted “Open Properties View Designer” icon is clicked to open

The View editor can be used to drag and drop the required properties to create a new View Auditor Department layout page.

Figure 1-66
The required properties for the View are dragged and dropped to the page

First, the Layout Container in the list on the left in Figure 1-66 is dragged to the central panel of the Properties View Designer.

Then the properties are dragged from the Case Properties list on the left to the Layout Container area as shown in Figure 1-66.

Figure 1-67
The completed properties layout, including Business Objects

Finally, the Case Search tab is selected, and the required Search Properties are added to the Case Search view as shown in Figure 1-68.

Figure 1-68
The Case Properties to be searched are added to the Case Search view

Adding Business Objects to Be Searched

The Business Objects to be searched are also added to the Case Search view.

Figure 1-69
The Case Business Objects to be searched are added to the Case Search view

The default root Case Folder (already created by the system) of Audit Department is left for the Case Folders item as shown in Figure 1-70. (A set of subfolders could be created to provide a different location for different document class types.)

Figure 1-70
The default **Audit Department** Case Folder is left “as is.”

The Stages section is used to add stages. An Audit Check List Creation and an Audit Checklist Review stage are added, as shown in Figure 1-71.

Figure 1-71
The Stages are added to the Audit Department Case workflow steps

Additional Stages are added as shown in Figure 1-72.

Figure 1-72
The list of the stages for the Auditing Case workflow

The Business rules are not set on this Solution, so we can leave the Rules step empty.

A Case Type can have Business rules which determine the actions to take if particular conditions are met. After creation, the business rules in a task can be used to affect the route of the Task Workflow process or update the case properties.

Rules can be created which include the user-defined case properties and case system properties.

For a full description and usage, see the following link:

www.ibm.com/docs/en/case-manager/5.3.3?topic=solution-business-rules

The Case Workflow Tasks can be added with the attributes shown as follows using the Case Type Tasks section.

There are four possible options for the Workflow Task types as follows:

Task with New FileNet P8 Process

(Creates a task that uses a FileNet P8 Workflow Process to define one or more steps that a case worker completes)

To-do Task

(Creates a to-do task that can be used to record information and can be completed without any workflow steps)

Container Task

(Creates a container workflow task that contains subtasks that start after the Container workflow task changes to a working state)

Task with Existing FileNet P8 Process

(Creates a Workflow task that reuses an existing FileNet P8 Workflow Process)

The first type of Task is selected (Task with New FileNet P8 Process).

Figure 1-73
A new Case Type Workflow Task is selected

Figure 1-74
The Audit Process workflow task attributes are entered

The Task Properties tab is entered next. (The Preconditions tab allows for preconditions that must be met before the task can start. Tasks can start automatically after all preconditions are met or manually by a user after all the preconditions are met. The Case property values are usually used to determine the preconditions.

See the full details here:

www.ibm.com/docs/en/case-manager/5.3.3?topic=tasks-task-preconditions

Figure 1-75
**Select All** is clicked to reference all the Audit Solution properties

Add a Design Comment. (This appears on the Solution reports.)

Figure 1-76
The Design Comments are added to the Audit Master Audit Process Task

The Pages tab of the main solution is selected to copy the default Case Details page to add the custom property’s view we created.

Copy and edit the Case Details page and add the custom property’s view created.

Figure 1-77
The default **Case Details** page is copied to customize the view

It is good practice to use the copy facility of the IBM Case Builder for customizing pages since this provides a ready-made backup of the original default Case Details page which can be reverted back to, if there are any issues with the customization. In addition, a working customized Case Details page can itself be copied to provide different functions for different Roles within a Solution.

Figure 1-78
The highlighted Copy icon is selected to copy the Case Details page

Figure 1-79
The copied **Case Details** page name can be altered from the highlighted default

The Case Details page can now be updated with the name Case Details with Business Objects as shown in Figure 1-80.

Figure 1-80
The **Name** and **Description** fields are updated for the Custom **Case Details** page

The Page Designer icon is clicked to edit the new Case Details page.

Case Pages are set up with predefined templates containing web widgets which have built-in functionality to support the display of Case details in the In-baskets for a specifically selected Case. It is possible to modify the layout of these template pages in the IBM Case Builder Page Designer as shown in Figure 1-81.

Figure 1-81
The **Open Page Designer** icon is selected using the mouse-over on the new **Case Details** page line

The Edit Settings icon is selected on the Properties section of the Page Designer.

Figure 1-82
The **Properties** panel is edited using the **Edit Settings** icon

The Case Type we created can now be associated with the Case Details page properties by clicking the Add icon highlighted in Figure 1-83.

Figure 1-83
The **Add (+)** icon is clicked to add the **Audit Department** Case Type

Figure 1-84
The **Audit Department** Case Type we created earlier is selected from the list

The selected Case Type will then give access to one or more Views created under the Case Type.

Figure 1-85
The Auditor Department view, created earlier, is selected

The Add button is now grayed out. If there were additional Views created for a second Case Type, then this could be added and then associated with a relevant properties frame view.

Figure 1-86
The OK command button is clicked to save the settings

The Audit Department Case Type can now be updated to associate the Case Details with Business Objects page, which we copied from the default Case Details page earlier, with the Auditor’s Manager role.

The Case Details with Business Objects page allows a Business Object (which consists of a number of global properties) to be treated as a single multi-property entity. The page widget has additional display features such as a + icon to add a complete business object in a pop-up window.

Figure 1-87
The **Auditor’s Manager** role is associated with the custom **Case Details** page layout

Figure 1-88
The **Auditor** role is also associated with the custom **Case Details** page layout

We can now save, deploy, and then test the Audit Master Solution.

Figure 1-89
The “Commit all the components of the Solution” icon (↓) is clicked

If there are some locked components of the Solution which still require saving, you might get the message as shown in Figure 1-90.

Figure 1-90
The “Commit all the components of the Solution” icon (↓) message is shown if items are locked for a Solution

Next, we have to deploy the Audit Master Solution to the Target Object Store in order to test the Case system.

Figure 1-91
The “Deploy the changed solution artifacts into a test environment” icon is clicked

The deployment takes around two minutes and is confirmed with a green tick if all is successful or a red “x” if there are errors requiring remediation.

Figure 1-92
The Audit Master solution is successfully deployed for testing

In the preceding example, the Solution is deployed with no deployment errors.

We can now click the icon as shown in Figure 1-93 for a first test of the deployed Audit Master Solution.

Figure 1-93
The “Start the IBM Case Manager Client to test the solution” icon is clicked

Part 4 – Testing and Administration of the Audit Solution

Figure 1-94
We need to be a member of a Solution **Role** associated with **Audit Master**

Add the Solution role for user Alan.

Figure 1-95
The Manage Roles menu is selected under the Audit Master Solution

The Add Users and Groups command button is clicked on the first role which is selected, by default, as the Auditor’s Manager role.

Figure 1-96
The **Add Users and Groups** command button is clicked to add users

Figure 1-97
The User Names beginning with A are searched, and Alan is selected

After a list of Auditor’s Manager role users is added, the Auditor role users can be added. (A user can be added to more than one role in an IBM Case Manager Solution.)

The Auditor role users are added next.

Figure 1-99
A Group can be added to a Solution role

Now we can see the Add Case button. Also, Roles can now be managed to add more users, using the Manage Roles command.

Figure 1-100
The Manage Roles command can now be used to add new users

Figure 1-101
The **Add Case** command button is clicked to add a new Audit Department

The Audit Department Case Type is selected from the drop-down (an IBM Case Manager Solution can have multiple Case Types).

Figure 1-102
The new **Audit Department** case is selected to start a new case

Figure 1-103
The required Business Objects are edited using the + icons (highlighted)

The + icons are selected in turn, and the Case entry form is scrolled down as shown in Figure 1-103.

Figure 1-104
The Audit Date/Time field is a required entry field

The Date picker shows the current date, but we need to select an Audit Date in the future to allow the Checklist questions to be reviewed by the Department Manager.

Figure 1-105
June is selected using the Date picker drop-down for the month

Figure 1-106
The required fields are entered as shown (red *) for required fields

The Audit Business Object is entered and updated using the OK command.

Figure 1-107
The Comments (multi-value) are entered and the Audit information fields

Figure 1-108
The Auditor Business Object fields are entered

One or more Checklist Business Objects are entered to confirm the Department procedures are followed correctly.

Figure 1-109
A Checklist item is entered

Next, the Department details are entered using the Department Business Object.

Figure 1-110
The list of the Department procedure documents to be audited is entered

The list of department emails for user contacts for the audit is entered.

Figure 1-111
The multi-value list of emails for the audit is entered

Figure 1-112
The OK command is clicked to signify that all the Department fields are completed

The completed Case details are reviewed, and after checking, the Add command button is clicked to launch the “live” Audit Master Case into the IBM Case Manager system.

Figure 1-113
The Case details are reviewed, and the Case is launched by clicking the Add command button

The Case is visible in the Cases tab of the Case Manager Client, after selecting the Search command button.

Figure 1-114
The Search command button is used to refresh the Cases In-basket view

The case we created is automatically provided with a unique Case ID.

Figure 1-115
The refreshed Cases In-basket displays the new Audit Case we created

The Case is also visible in the acce (IBM Content Platform Engine Administration) web application tool in the Target Object Store.

Figure 1-116
The Case structure created in the IBM FileNet Content Object Store OS2

The Case Folder structure is held in the IBM FileNet Case Manager Target Object Store, OS2. The structure of the nested folders is shown in Figure 1-117.

The top-level folder, under the Target Object Store Root Folder, is called IBM Case Manager. Under this folder, each solution is stored under the Solution Deployments folder. (The Audit Master solution folder can be seen to be linked to this folder.)

Each solution Case Type for Audit Master is then held under the Case Types folder. The next subfolder is the AUD_AuditDepartment case type for the Audit Master solution. The live Audit Master Solution cases are then stored under the Cases folder, which is one of the subfolders under the AUD_AuditDepartment Case Type parent folder.

This top-level Cases folder for the AUD_AuditDepartment Case Type is split by date subfolders organized by nested folder levels of year (2022), month (5), day (31), the four-digit parent folder number, a randomly generated number to identify the parent folder (0036), and under this a unique Case ID sequence value starting from 0000000100001.

The Case ID and sequence value and customization are described in detail on the URL page:

www.ibm.com/docs/en/case-manager/5.3.3?topic=system-customizing-case-unique-identifier-prefix

Figure 1-117
The Case Advanced Search criteria entry window

The Advanced Search command button on the main IBM Case Manager Cases tab is clicked to display the search criteria entry window shown in Figure 1-117.

Figure 1-118
The Advanced Search results are shown

The returned row can be clicked on the DepartmentNumber property column to show the Summary tab details in the right panel, as displayed in Figure 1-119.

Figure 1-119
The Summary tab details are shown for the Case

On clicking the History tab, the recorded events for the Case and Task audit history are displayed as shown in Figure 1-120, with the latest events shown at the top of the list.

Figure 1-120
The Case History tab shows the events generated for the Case and task

The layout of the Case details panel can be changed from a summary Details view to the Magazine view of each property using the icon highlighted in Figure 1-121.

Figure 1-121
The **Magazine view** of the Case properties

On clicking the AUD_AuditDepartment_000000100001 Case link in Figure 1-121, the Case Details with the Business Object property entry view, Case Details with Business Objects (the page view we created earlier), is displayed.

Figure 1-122
The Business Object property entry page view, **Case Details with Business Objects**

The + icon against each multi-value Business Object property allows new entries to be inserted, as shown for the ChecklistObj property lines in Figure 1-123.

Figure 1-123
Checklist items are added to the Case using the + icon (highlighted)

In Figure 1-123, the Audit Process Start command can be clicked to move the case onto the next stage of the process (from the Audit Check List Creation to the Audit Checklist Review stage). This shows the pop-up window shown in Figure 1-124.

Figure 1-124
The Yes command is used to start the Audit Process

The Audit Process Task status is shown with a status of Completed with the date of completion.

Figure 1-125
The Audit Process Task status is shown with a status of **Completed**

Figure 1-126
The History tab shows the latest Audit Process event

Each of the Audit Case Stages shown in Figure 1-127 can be clicked to show the Stage details entered (defined during the IBM Case Builder development, as shown in Figures 1-71 and 1-72).

Figure 1-127
The Stages defined for the Audit Master solution process

On clicking the Audit Checklist Review stage link (highlighted in Figure 1-127), we get the pop-up window shown in Figure 1-128.

Figure 1-128
The **Audit Checklist Review** stage details are displayed

It is possible to configure the state of the case stage at runtime by changing the case stage state by

a)
Adding the following actions to a menu or toolbar in the Case List widget or Case Toolbar widget:
- Complete Stage
- Restart Stage
- Toggle Stage

b)
Adding the stage steps to the System Lane of the workflow for a task to run the following case operations:
- completeCurrentCaseStage
- placeCurrentCaseStageOnHold
- releaseCurrentOnHoldCaseStage
- restartPreviousCaseStage

Figure 1-129
Comments can be added at any time for an Audit Case by clicking the Comments command button (highlighted)

One or more comments can be added to the Audit Case, as shown in Figure 1-130, using the Add command button. The Close command is then used to complete the addition of comments.

Figure 1-130
A new comment is added to the Case

An Excel or MS Word Office document can be added to the Audit case as shown in Figure 1-131.

Figure 1-131
The Documents tab is selected, and the **Add** drop-down is used to Add a Document from the Local System

The Add ➤ Add Document from Local System menu option on the Documents tab allows a document to be browsed to from a pop-up window, as shown on the Linux system window in Figure 1-132.

Figure 1-132
The **Browse** command is used to navigate to an Audit results Word document

Figure 1-133
The Add command is used to store the selected Word document in the IBM FileNet Content Engine Object Store

The stored document can be seen in the Audit Case and downloaded and viewed at any time using the features of the IBM FileNet document management system.

Figure 1-134
The uploaded **IT Quality Audit Results** document is available for viewing

The History tab of the Case now shows the uploaded Document we added.

Figure 1-135
The **History** tab shows the uploaded Audit results Word document event

Exporting and Production Deployment of the Audit Master Solution

Usually, the IBM Case Manager Solution will be developed in a development environment and will then be transferred to one or more test environments and finally imported to a production system. IBM Case Manager supports this development life cycle by providing an export/import of the complete Solution, packaged as a single zip file, as shown in this section.

The IBM Case Administration Content Navigator desktop application is run using the URL as follows:

http://ecmukdemo6:9081/navigator/?desktop=icmadmin

where ecmukdemo6 is the web application server and 9081 is the WebSphere application server port for the IBM Case Manager applications.

Figure 1-136
The IBM Case Manager Administration Desktop is launched

The Design Object store, OS1, in Figure 1-136, is clicked to show the Solutions drop-down as illustrated in Figure 1-137.

Figure 1-137
The Design Object Store, **OS1**, menu options are displayed

The drop-down Solutions is then clicked to show the list of IBM Case Manager Solutions, from which we can export the Audit Master Solution file we require.

Figure 1-138
The list of Solutions in the Design Object store

The Audit Master solution is selected on the Solutions tab shown in Figure 1-138, and the Actions drop-down command button is clicked to select the Export option.

Figure 1-139
The Audit Master Solution is selected for Export

The Solution name and prefix values can (optionally) be changed for export as shown in the next screen in Figure 1-140.

Figure 1-140
The Next command is clicked after any required changes are made

The Next command is clicked after verifying the Export details are correct.

Figure 1-141
The Finish command is clicked to start the Export to the Solution zip file

When the Finish command is clicked, the Audit_Master_solution.zip file is created with the exported Solution parameters. This zip file can be used as a backup of the Solution during design and development, so that any changes which require backing out can easily be removed, since the saved .zip file can be used to import the backed up Solution and reset the Design Object store.

(In practice, the Design/Target Object Stores may need to be reinitialized to clear out some property templates which are not easy to remove programmatically before loading the backed up Solution.)

Figure 1-142
The **Download and Close** command is executed after the solution is exported

The web browser download option is used to retrieve the exported Solution .zip file.

Figure 1-143
The exported solution .zip file is saved to the Downloads area

The exported Audit_Master_solution.zip file can now be copied to another test or production system to be imported.

Figure 1-144
The exported zip file can be copied to a production system

Importing the Zipped Audit Master Solution to a Production System

The copied Audit_Master_solution.zip file is also imported using the IBM Case Manager administration web application.

Copy the exported Audit_Master_solution.zip file to a new folder /opt/AuditMaster.

Figure 1-145
The exported zip file is copied to the production system

The zipped solution can be loaded into the Design Object store as shown in Figure 1-146.

Figure 1-146
The Import ➤ Import Solution ➤ From Solution Package option is selected

Figure 1-147
The exported Audit Master Solution zip file is browsed to

Figure 1-148
The Audit_Master_solution.zip is selected to open

Figure 1-149
The Next command is used to display the Audit Master solution attributes

Figure 1-150
The Audit Master zipped Solution attributes are displayed

The Finish command entered to start the Import process for Audit Master.

Figure 1-151
The Audit Master Solution is successfully imported to the production system

The Close command button can now be clicked on the Figure 1-151 page.

The Audit Master Solution is now added to the Design Object Store, OS1, but now we need to deploy it to the Target Object Store, OS2.

Figure 1-152
The Audit Master solution is deployed to the Target Object Store

Figure 1-153
The Next command is used to view the deployment attributes

Figure 1-154
The Finish command is clicked to deploy the imported Solution

Figure 1-155
The Audit Master solution is successfully deployed

After a successful deployment to the Production Target Object Store, the Assign Roles command button launches a separate IBM Case Manager Client window to allow the Production Role security to be configured.

Figure 1-156
The IBM Case Manager Client Manage Roles is selected

Finally, the Production System Security Users and Groups are added to the Audit Master Roles.

Figure 1-157
The Production Users and Groups are added to the Audit Master solution roles

Debugging the Case Manager Client

This section covers an earlier issue which was fixed by adding a missing component for the IBM FileNet Content Server Target Object Store, used by IBM Case Manager.

REF: www.ibm.com/support/knowledgecenter/en/SSCTJ4_5.3.3/com.ibm.casemgmt.design.doc/acmta044.htm

To configure logging for IBM Case Manager web applications, you must enable debugging on the IBM Content Navigator server and then restart the IBM Content Navigator server.

Procedure

To configure logging settings in IBM Content Navigator:

Log in to the IBM Content Navigator administration desktop.

Click the Settings tab and then click the Logging subtab.

Figure 1-158
The **Logging** tab of the **Settings** menu in the admin desktop is selected

Set the logging level for the applications to Debug.

Figure 1-159
The **Debug** level option is selected to replace the **Warning** level

Click Save and then click Close.

Figure 1-160
The **Logging** level is now displayed as **Debug**

Log out of the IBM Content Navigator administration desktop.

Restart the application server instance where IBM Content Navigator is deployed.

In the SystemOut.log file, I get

[REQUEST 19] com.ibm.ecm.struts.actions.p8.P8SearchAction.executeAction()

com.filenet.api.exception.EngineRuntimeException: FNRCR0081E: RETRIEVE_PROPERTY_NOT_DEFINED: The property ContainerType is not defined. ObjectStore: "OS2", SQL: "SELECT t.[FolderName], t.[CmAcmHealthIndicator], t.[LastModifier], t.[DateLastModified], t.[CmAcmCaseTypeFolder], t.[CmAcmCaseState], t.[CmAcmCaseIdentifier], t.[DateCreated], t.[Creator], t.[Id], t.[ASB_TestString], t.[ClassDescription], t.[ContainerType], t.[LockToken], t.[LockTimeout] FROM [ASB_Test] t WHERE t.[ASB_TestString] LIKE 'ASB%%' and t.[CmAcmCaseState] > 1 ORDER BY t.[CmAcmCaseIdentifier] OPTIONS ( COUNT_LIMIT 2147483647 )" errorStack={

Analysis with acce showed:

[REQUEST 19] com.ibm.ecm.struts.actions.p8.P8SearchAction.executeAction()

com.filenet.api.exception.EngineRuntimeException: FNRCR0081E: RETRIEVE_PROPERTY_NOT_DEFINED:

The property ContainerType is not defined. ObjectStore: "OS2", SQL:

Exists

"SELECT t.[FolderName], Yes

t.[CmAcmHealthIndicator], Yes

t.[LastModifier], Yes

t.[DateLastModified], Yes

t.[CmAcmCaseTypeFolder], Yes

t.[CmAcmCaseState], Yes

t.[CmAcmCaseIdentifier], Yes

t.[DateCreated], Yes

t.[Creator], Yes

t.[Id], Yes

t.[ASB_TestString], Yes

t.[ClassDescription], Yes

t.[ContainerType], No

t.[LockToken], Yes

t.[LockTimeout] Yes

FROM [ASB_Test] t

WHERE t.[ASB_TestString] LIKE 'ASB%%'

and t.[CmAcmCaseState] > 1

ORDER BY t.[CmAcmCaseIdentifier] OPTIONS ( COUNT_LIMIT 2147483647 )" errorStack={

Checked FileNet Version

http://ecmukdemo6:9080/FileNet/Engine

Figure 1-161
The FileNet version details are checked

Checked FileNet Health

http://ecmukdemo6:9080/P8CE/Health

Figure 1-162
The FileNet Health status is checked and validated by the system

Check FileNet Object Store Upgrade Status

http://ecmukdemo6:9080/FileNet/AutomaticUpgradeStatus

Figure 1-163
The IBM FileNet Object Store Upgrade status is checked

Upgrading Status Meaning

Visit the following URL to see the description of the status values shown:

www.ibm.com/support/knowledgecenter/en/SSGLW6_5.5.0/com.ibm.p8.install.doc/p8pup323.htm

Check FileNet Workflow Upgrade Status

http://ecmukdemo6:9080/peengine/IOR/ping

NB: You will be prompted to log in using the administration user (or other workflow Administrator accounts).

Figure 1-164
Log in to the Workflow Process Engine status page

Figure 1-165
The Workflow Process Engine status page

Figure 1-166
The Workflow Process Engine status page (scrolled down)

Clicking the System link in Figure 1-166, we get the screen in Figure 1-167.

Figure 1-167
The Process Engine status System Information details

Fix/Workaround for Error on Case Search

Issue Found in Case Manager Client Search in the Solution

Initially, I get the error in Figure 1-168 trying to search a Case that appears to be created correctly.

Figure 1-168
The initial version of the deployed solution was searched

The error message in Figure 1-169 was displayed on clicking the Search command shown in Figure 1-168.

Figure 1-169
The error window was shown on using the Search command

Initial Workaround

Figure 1-170
The **ContainerType** Property Template was added to the Object Store

Add a Property Template with a Symbolic Name of ContainerType.

Figure 1-171
A Property Template with a Symbolic Name of **ContainerType** was added

Figure 1-172
The Data type was selected as String

Figure 1-173
The Choice list values were left empty

Figure 1-174
The **Single** option default was set for the value type

Figure 1-175
The reviewed properties for the **ContainerType** Property Template

Figure 1-176
The ContainerType Property Template was successfully created

Figure 1-177
The ContainerType property template was added to the Test Case Object class

Select the “Container Type” Property Template Definition we just created to add to the Test Case Object class.

Figure 1-178
The Container Type property is now visible in the Test Object class definitions

Save and refresh.

Figure 1-179
The Container Type property is now saved and ready for use

Tested and working in the acce tool, search the SQL as follows:

SELECT [This], t.[FolderName], t.[CmAcmHealthIndicator], t.[LastModifier], t.[DateLastModified], t.[CmAcmCaseTypeFolder], t.[CmAcmCaseState], t.[CmAcmCaseIdentifier], t.[DateCreated], t.[Creator], t.[Id], t.[ASB_TestString], t.[ClassDescription], t.[ContainerType], t.[LockToken], t.[LockTimeout] FROM [ASB_Test] t WHERE [ASB_TestString] like '%ASB%'

Figure 1-180
The SQL is run and now works correctly returning the first Case details

Case Search is now working correctly.

Figure 1-181
The IBM Case Manager shows the retrieved Test case

But see other issues!!

Fix (Recommended)

After searching the Internet with Google using

What is the Container Type for the Folder Class in FileNet P8?

Figure 1-182
The IBM Knowledge base article on the Container Type property

REF:

www.ibm.com/support/knowledgecenter/en/SSNW2F_5.5.0/com.ibm.p8.ce.admin.tasks.doc/featureaddons/fa_properties_folder_class_subclasses.htm

Figure 1-183
The Container Type is installed using the Workplace Base Extensions

So we just need to add a Workplace Base Extensions Add-On to the OS2 Target Object store.

First, reverse out our initial workaround by removing the property definition we added:

a)
From the Test Folder

Figure 1-184
The manually added Container Type property is removed from the Test class

Figure 1-185
The Save and Refresh command shows the Container Type has been removed

b)
And then from the property definition list

Figure 1-186
The Container Type property template is also removed

Figure 1-187
Click OK to confirm the deletion of the Container Type template property

Now install the Workplace Base add-on feature.

Figure 1-188
The Install Add-on Features menu option is selected by right-clicking the **OS2** Object Store node

Figure 1-189
The 5.2.1 Workplace Base Extensions add-on feature is selected for installation

Figure 1-190
The Add-on feature status is displayed

And then restart the WebSphere application server.

Testing for the Audit Master Solution

Figure 1-191
The Test Case is added using the IBM Case Manager desktop

Figure 1-192
The example Audit Master case is added

The Search command is tested against the added Case in Figure 1-192.

Figure 1-193
The Cases tab is selected, and the Search command is used

Figure 1-194
The Search command now works correctly and returns the case

Double-click the Case Title.

Search is now working correctly!

Figure 1-195
The Audit case details are now all displayed correctly

Chapter 1 Exercises

The following questions cover the functions using the IBM Case Builder which we covered in this chapter.

MULTIPLE CHOICE QUESTIONS

1.
The Red Flag icon against the IBM Case Property Attributes column defines
1. a)
  A multiple-value property
2. b)
  A Hidden attribute property
3. c)
  A Required attribute property
4. d)
  A New property is added
2.
An IBM Case String property type for the Oracle Database system is limited to
1. a)
  64 characters
2. b)
  1333 characters
3. c)
  4000 characters
4. d)
  024 characters
3.
The In-basket Filters tab is used:
1. a)
  To filter a subset of the Cases
2. b)
  To alter the sort order of the Cases
3. c)
  To define the Object Type of the Case properties
4. d)
  To define the list of Hidden Case properties
4.
Business Object Types as Case properties are
1. a)
  Multi-value String properties
2. b)
  Multi-property Business Objects
3. c)
  Multi-value Choice lists
4. d)
  Multiple Case Types

MULTIPLE CHOICE ANSWERS

1.
c) A Required attribute property
2.
b) 1333 characters
3.
a) To filter a subset of the Cases
4.
b) Multi-property Business Objects

QUESTIONS

1.
Describe how you would implement an IBM Case Manager Solution to support moving it from a development environment to a production system in particular, describing how the development system security is kept separate from the security of the production system.
2.
What databases does IBM Case Manager support and what impact does this have on how String Case properties are stored?
3.
What methods can you use to track issues in the deployment and testing of an IBM Case Manager Solution?

.

In Chapter 2, we will cover the use of the Java language to customize Workflow Component Events and the DBEXECUTE workflow step for calling Database Stored Procedures.

Table of Contents for 1. IBM FileNet Case Manager 5.3.3 Case Builder Solution Development Steps for the Audit System

Create new playlist

Sign In

Sign Up

1. IBM FileNet Case Manager 5.3.3 Case Builder Solution Development Steps for the Audit System

Chapter Organization

Introduction

Part 1 – Bill of Materials

Starting the IBM Case Manager System

Start the LDAP Servers

Start the IBM FileNet Case Manager Database

Start the IBM FileNet Content Engine Web Service

Start the IBM Case Manager Web Application

Load the IBM Case Manager Builder Web Application

Part 2 – IBM Case Manager Solution Metadata

Adding a New Solution

Adding Properties and Business Objects

Adding Roles

Adding Properties to the In-Baskets for Each Role

Adding Document Class

Adding Business Objects

Adding Business Object Types As Case Properties

Part 3 – Adding IBM Case Manager Case Types

Adding Case Types

Auditing Department Task

Adding Business Objects to Be Searched

Part 4 – Testing and Administration of the Audit Solution

Exporting and Production Deployment of the Audit Master Solution

Importing the Zipped Audit Master Solution to a Production System

Debugging the Case Manager Client

Procedure

Checked FileNet Version

Checked FileNet Health

Check FileNet Object Store Upgrade Status

Upgrading Status Meaning

Check FileNet Workflow Upgrade Status

Fix/Workaround for Error on Case Search

Issue Found in Case Manager Client Search in the Solution

Initial Workaround

Fix (Recommended)

Testing for the Audit Master Solution

Chapter 1 Exercises

Table of Contents for
1. IBM FileNet Case Manager 5.3.3 Case Builder Solution Development Steps for the Audit System