This chapter covers the step-by-step procedure to use the IBM FileNet Case Manager 5.3.3 Case Builder Solution Development steps and the similar IBM system, IBM Business Automation Workflow, to create an Audit system.
See:
www.ibm.com/docs/en/case-manager/5.3.3?topic=overview-whats-new-in-case-manager-v533
An overview of the IBM Case Manager system can be found in the following link:
www.ibm.com/docs/en/case-manager/5.3.3?topic=documentation-case-management-overview
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.
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”
This gives the downloaded document, entitled CaseManagerInstallationonRHEL8.0_V3.docx.
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”
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)
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.
Click to open the LDAP, IBM Security Directory Server Instance Administration Tool:
Click the Start/Stop command.
Click the Start server command button.
Click the Start administration server command button.
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
From the command window in Linux:
Start the IBM FileNet Content Engine Web Service
Start the IBM Case Manager Web Application
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.
The referenced IBM version is displayed in the About pop-up window as shown Figure 1-12.
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.
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.
See Appendix A ©1992, Alan S. Bluck (https://www.researchgate.net/publication/334095565_Case_Manager_Solution_Development).
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).
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
The Audit Case properties are added to form a list.
The Add Property command button is clicked to add the Audit system department properties for the ISO9000/BS5750 auditing of an organization’s department.
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.
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.
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).
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.
The next step is to define the In-baskets of the generated Audit cases.
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.
The required properties are selected by holding down the CTRL key and clicking using the left mouse button. Then select the OK command button.
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.
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.
Click OK to generate the new Document Class and then select the properties required.
Click OK.
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.
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.
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.
Enter the Business Object Name and enter a Description and click OK as highlighted in Figure 1-34.
Click New to add a new property to the Audit Business Object.
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.
The Audit Date 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.
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.
The properties are added from the Global property list (defaulting the attributes).
The Department Business Object is created next, with the Name and Description defined as shown in Figure 1-44.
The Department Business Object properties are selected from the Existing Global property list as shown in Figure 1-45.
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.)
The details of the properties for the Department Business Object are shown in Figure 1-47.
The Procedure Business Object is created next, with the Name and Description defined as shown in Figure 1-48.
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
The Checklist Item Business Object is added next to the list of Business Objects.
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)
In the preceding property list, we have changed the default String length for the Checklist Item Description from 64 characters to 1024 characters.
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.
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.
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.
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.
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.
The Case Type Properties Tree menu item is selected to add the required properties for the Task.
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.
The Save command can be used to save all the Solution build updates at this point.
The Views tab is selected, and the related Case summary properties are added from the list as shown in Figure 1-61.
The Audit Business Object properties are added next, to the Case Summary view.
Next, we select the Properties Layout tab to define the layout of the displayed property values.
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.
The View editor can be used to drag and drop the required properties to create a new View Auditor Department layout 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.
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.
Adding Business Objects to Be Searched
The Business Objects to be searched are also 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.)
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.
Task with New FileNet P8 Process
To-do Task
Container Task
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).
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
Add a Design Comment. (This appears on the Solution reports.)
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.
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.
The Page Designer icon is clicked to edit the new Case Details page.
The Edit Settings icon is selected on the Properties section of the Page Designer.
The selected Case Type will then give access to one or more Views created under the Case Type.
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.
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.
We can now save, deploy, and then test the Audit Master Solution.
Next, we have to deploy the Audit Master Solution to the Target Object Store in order to test the Case system.
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.
In the preceding example, the Solution is deployed with no deployment errors.
Part 4 – Testing and Administration of the Audit Solution
Add the Solution role for user Alan.
The Add Users and Groups command button is clicked on the first role which is selected, by default, as the Auditor’s Manager role.
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.
Now we can see the Add Case button. Also, Roles can now be managed to add more users, using the Manage Roles command.
The Audit Department Case Type is selected from the drop-down (an IBM Case Manager Solution can have multiple Case Types).
The + icons are selected in turn, and the Case entry form is scrolled down as shown in Figure 1-103.
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.
The Audit Business Object is entered and updated using the OK command.
One or more Checklist Business Objects are entered to confirm the Department procedures are followed correctly.
Next, the Department details are entered using the Department Business Object.
The list of department emails for user contacts for the audit is entered.
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.
The Case is visible in the Cases tab of the Case Manager Client, after selecting the Search command button.
The case we created is automatically provided with a unique Case ID.
The Case is also visible in the acce (IBM Content Platform Engine Administration) web application tool in the Target Object Store.
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
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.
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.
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.
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.
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.
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.
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
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.
The History tab of the Case now shows the uploaded Document we added.
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.
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.
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.
The Next command is clicked after verifying the Export details are correct.
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.)
The web browser download option is used to retrieve the exported Solution .zip file.
The exported Audit_Master_solution.zip file can now be copied to another test or production system to be imported.
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.
The Finish command entered to start the Import process for Audit Master.
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.
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.
Finally, the Production System Security Users and Groups are added to the Audit Master 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.
Set the logging level for the applications to Debug.
Click Save and then click Close.
Log out of the IBM Content Navigator administration desktop.
Restart the application server instance where IBM Content Navigator is deployed.
Checked FileNet Version
http://ecmukdemo6:9080/FileNet/Engine
Checked FileNet Health
http://ecmukdemo6:9080/P8CE/Health
Check FileNet Object Store Upgrade Status
http://ecmukdemo6:9080/FileNet/AutomaticUpgradeStatus
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).
Fix/Workaround for Error on Case Search
Issue Found in Case Manager Client Search in the Solution
Initial Workaround
But see other issues!!
Fix (Recommended)
After searching the Internet with Google using
REF:
So we just need to add a Workplace Base Extensions Add-On to the OS2 Target Object store.
- a)
From the Test Folder
- b)
And then from the property definition list
And then restart the WebSphere application server.
Testing for the Audit Master Solution
The Search command is tested against the added Case in Figure 1-192.
Double-click the Case Title.
Search is now working correctly!
Chapter 1 Exercises
The following questions cover the functions using the IBM Case Builder which we covered in this chapter.
- 1.The Red Flag icon against the IBM Case Property Attributes column defines
- a)
A multiple-value property
- b)
A Hidden attribute property
- c)
A Required attribute property
- d)
A New property is added
- 2.An IBM Case String property type for the Oracle Database system is limited to
- a)
64 characters
- b)
1333 characters
- c)
4000 characters
- d)
024 characters
- 3.The In-basket Filters tab is used:
- a)
To filter a subset of the Cases
- b)
To alter the sort order of the Cases
- c)
To define the Object Type of the Case properties
- d)
To define the list of Hidden Case properties
- 4.Business Object Types as Case properties are
- a)
Multi-value String properties
- b)
Multi-property Business Objects
- c)
Multi-value Choice lists
- d)
Multiple Case Types
- 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
- 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.