1. IBM Case Manager An Architectural Overview
Mike Marin
Distinguished Engineer
IBM

2. Disclaimer
The information contained in this presentation is provided for informational purposes only.
While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided “As Is”, without warranty of any kind, express or implied.
In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice.
IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other documentation.
Nothing contained in this presentation is intended to, or shall have the effect of:
Creating any warranty or representation from IBM (or its affiliates or its or their supplies and/or licensors); or
Altering the terms and conditions of the applicable license agreement governing the use of IBM software.

3. Agenda Case Management Introduction Components High Level Architecture
Development Environment
Solution Object Model
Case Tasks
Solution Definition Artifacts
Project Areas
Design Object Store
Execution Environment
Case Instance
Case and task Lifecycles
Case Split
Deployment Topology
Target Object Store
P8 Task Implementation
External Data Support
Case Analytics
CM8 Integration
IBM BPM integration

4. IBM Case Manager Brings people, process and information together … in context of a case
Delivers optimized case outcomes
Supports dynamic, runtime work management
Delivers trusted information to the case – structured or unstructured
Manages and governs entire case lifecycle
Provides the line-of-business and IT with tools to rapidly deliver case-based solutions
process
people
Case Management
Content
By placing the case model in the content repository, information and other artifacts associated with cases are not only selected and viewed but also managed in the context of the case over its lifecycle. These include collaborations, processes steps, and the other associated case elements.
Process
Cases may follow static processes that are prescribed for certain business situations. They may also follow more dynamic paths based on changes to information associated with a case. Straight through, transactional processes can be called as can more collaborative processes.
Analytics
Analytics help case workers to make the right decisions in case of fraudulent claims for insurance, social benefit coverage, eligibility for welfare programs and more. Analytics help detect patterns within or across cases or simply optimize the overall case handling to optimize case outcomes.
Rules
Many decisions in a case depend on set values, e.g. interest rates for loans based on credit rating, approval authority for transaction amounts, etc. By separating rules from process the case handling becomes much more agile as rules can change in lockstep with market changes.
Collaboration
Finding the right subject matter expert is often critical to make an ad-hoc decision required to bring a case to an optimal closure. Collaboration in form of instant messaging, presence awareness, and team rooms enables an organization and its case workers to work together to drive outcomes.
Social Software
Dynamic To Do Lists that are role based help case workers establish conversations and actions that must take place to close cases and link to information about the people that can help. Users can brainstorm on appropriate solutions and actions and create wikis linked to particular case types to assist colleagues in their case work.
information 4

5. IBM’s approach to case management5
IBM’s approach to case management
Integrated Solution
Use Cases
Patterns
Complex exception handling
Complaint or dispute management
New customer or new account opening
Lending applications
Credit approval
Contract management
Claims processing
Benefits enrollment
Rate case management
Investigations or audits
Work activities are event- driven
Collaborative, ad-hoc processes
Processes are often not predetermined
Work is knowledge intensive
Content is essential for decision making
Outcomes are goal-oriented
Relies on people to make decisions
Content management
Business process management
Collaboration tools
Social software
Business rules
Analytics
Solution development and deployment
Templates
A solution pattern where:
Activities are event-driven
There are collaborative, ad-hoc processes
Processes are often not predetermined
Work is knowledge intensive
Content is essential for decision making
Outcomes are goal-oriented
The judgment of people impact how the goal is achieved
…where a case is the primary focus of the system
For challenges such as:
Complex exception handling
Complaint or dispute management
Contract management
Lending applications
Claims processing
Benefits enrollment
Rate case management
Investigations or audits
…that are both horizontal and vertical in nature
That requires unique capabilities from
Content management
Business process management
Collaboration tools
Social software
Business rules
And analytics
Solution development and deployment
… brought together in the context of a case
KEY: Both horizontal and vertical in nature
KEY: A case is the primary focus of the system
KEY: Solution is optimized for the context of a case 5 5 5

6. IBM Case Manager components
Simplifying the delivery of case-based solutions
Case Design
Case Runtime
Case Analytics
Structured Unstructured
Models Templates Solutions
Context o View History
Real time Persisted
Case Infrastructure
Case Object Models
Case APIs
Solution Constructs
Task Object Model
Case Analytics Data Store
IBM is building an advanced case management platform that unites content, process and people
Customers can start from investments in any of these capabilities and expand into advanced case management
IBM is delivering optimized case outcomes through analytics, rules, collaboration and social computing
Advanced case management supports work management of structured and unstructured activities
Advanced case management delivers trusted information to the case – both content and structured data
Advanced case management can uniquely manage the entire case lifecycle including retention and governance requirements
IBM has the broadest portfolio of case management capabilities and the most extensive ecosystem of case management solutions
Collaboration
& Social SW
Monitoring & Analytics
Content
Workflow
Rules
Events
Integration
people s process s information 6 6 6

7. Major components of the case manager environment
Case Manager Builder
Case Solution builder tool oriented to needs of line of business analysts
Case Manager Client
A run time environment for launching, processing, and interacting with cases
Case Manager Analytics
Real time cases monitoring with threshold monitoring and alert generation
Case Manager Administration Client
Tool for configuring the Case Manage environment and for moving solutions between development and production domains
Case Manager API
Communication layer between components of the Case Manager applications.
Bottom line: IBM Case Manager provides rich, web-based user interfaces for Case Solution Authors, Case Workers, and Business Owners 7

8. High level architecture
Case Manager
Administration Client
Browser
Case Client
Case Builder
FileNet Deployment
Manager
WebSphere Application Server
Case Analyzer
Cognos BI Reports
Cognos Real
Time Monitor
Event Publisher
Case Builder Application
Lotus OneUI
DOJO
iLog jViews
Step Editor
Wizard
Solution Editor
Business Space
IBM iLog jRules
Case Widgets
IBM Forms
(optional)
Case Manager REST API
PE REST
Case REST
P8 CMIS
P8 PE API
P8 CE API
Workplace XT
Process Designer
P8 eForms
IBM Content Analytics
P8 Engine
Content & Process Engine
Case Add-ons
Lotus Sametime
Proxy Server
Community Server
IBM BPM (optional)
BPM Standard
BPM Advanced
Web Services
LDAP
Object Store

9. Models Templates Solutions9
Rapid solution design
Case Design
Models Templates Solutions
Easy to use, “Interview Mode” (wizard-driven) Case designer allows a business user to very quickly build a solution
Comprehensive across case assets Case designer can provide view of case
Leverage templates for a fast start Represent industry best practices
Significantly shortens time-to-value for case-style applications
Case Builder Support
PE Server updates
Support for templating model & Support round-trip authoring
Process Definition Enhancements & Dynamic step parameter attributes
BPM uses case properties
Expose case properties to queues for searching, filtering, and sorting
Bottom line: Deliver end users the solution in a fraction of time of other approaches 9 9

10. Solution object model A solution is conceptually composed of cases
Persistence model is based on the case instance

11. Tasks
Avoid defining a complete process, by just defining the known process fragments
Finding the right balance between formal and ah hoc processes
Solving the “Blind Surgeon Metaphor”(1) by introducing human decisions
Explicitly model the “what” need to be done, and the “why” it needs to be done.
Processes are only good to describe the “how” it need to be done
(1) W.M.P. van der Aalst, M. Weske, and D. Grünbauer. Case Handling: A New Paradigm for Business Process Support.
Data and Knowledge Engineering, 53(2): , 2005.

12. Repeatability Tasks can be repeated at will
The power of a task
Repeatability Tasks can be repeated at will
Grouping Inclusive and Exclusive
Optional User directed launching or skipping
Ad hoc User dealing with unknown
Event driven Tasks launched via events
Drive dynamic activities
A variety of events can trigger case tasks
Case Worker Actions
New Content
Case Updates
Uses structured processes fragments
Bottom line: Task object model enables a great deal of flexibility to empower the knowledge worker productivity

13. Examples of tasks

14. Solution definition artifacts
Each solution is a subfolder that contains:
Solution Definition File (SDF)
XML based file
Contains solution definition for; case types, document types, folder structure, properties, choice lists, Tasks, page references, views, etc
SDF does not contain target information
Configuration file
Contains definitions for role(s), inbasket(s), etc
<case name> XPDL (XML Process Definition Language files)
One XPDL file for each case type
Each Task has one process definition
Solution Workflow Collection (XPDL)
Containing reusable P8 BPM processes
User Interface page definitions 14

15. Example of solution artifacts
Solution folder
Created by P8 Process Designer
Solution Definition
Configuration
Role
In-Basket
Property
Four types of Tasks:
Created by Case Builder’s Step Editor
Reuse a workflow created by P8 BPM
Invoke a WID created component
Invoke an IBM BPM process
May call another workflow
Choice List
Document Type
Case Type
<case> XPDL
Workflow
Reuse Workflow
Global XPDL
Base
Workflow
Folders
May call another workflow
Task
Workflow
Task
Task
BPEL
process
Created by WID
Task
Pages
Page
Created by WID
Created by
IBM BPM
Process Designer
IBM BPM
process
Created by Business Space

16. Development Environment (Sandbox)
Project areas
Development environment can be segmented into project areas each one containing a target object store as a sandbox
Development Environment (Sandbox)
Target Object Store 1
Design Object Store
Project Area 1
Project Area 2
. . .
Project Area n
Isolated region
Case
Manager
Builder
Target Object Store 2
Isolated region
. . .
Target Object Store n
Isolated region
Business Space Server
(shared)

17. Design object store folder structure
Root Folder
Connection definition include project area definitions
IBM Case Manager -
Connection Definitions +
Data Sets contain basic Target Object Store configuration and add-ons
Data Sets +
Folder structure for Templates is similar to Solutions folder structure +
Solution Templates -
Solutions
Each solution is tag with the corresponding project area
<Solution name> -
Solution Definition
Configuration
Solution Workflow Collection
<case name> XPDL
Pages +
Pages contains Business Space references
<Solution name> +

18. Case worker user experience
1818
Case worker user experience
Case Runtime
Context o View Activities
Role-based and personalized End user gets exactly the information they need to progress the case
Flexible and extensible Can be configured to meet unique business requirements
Provides deep context for case work No more disjointed jumping between application
Brings people, process and information together to drive case progression and better outcomes
Case Client Support
Allow for dynamic role membership assignment
Support to case history Widget (Content Analytics for Case Analyzer)
Provide user information for Sametime Integration
Bottom line: A case worker has all the information they need to improve case outcomes 18 18

19. Unique case infrastructure and capability set
1919
Unique case infrastructure and capability set
Case Infrastructure
Case Object Models
Case APIs
Solution Constructs
Task Object Model
Case Analytics Data Store
Case Object Model
Full case details, its parties & case interrelationships
Ensures that case lifecycles are managed and relationships persist over time
Task Object Model
Allows the case to respond to external events
Provides unique model for managing ah-hoc activities
Provides a detailed audit trail of activities
Power of Case Client is exposed in APIs
REST APIs in case infrastructure for custom Web 2.0 development and interfaces
Solution Constructs
Enables a rapid, iterative design/test sandbox
Solutions can be templates that are reused
Case Analytics Data Store
Predefined structures for case-related information for analytics
Real-time and historical/summarized
Structured and unstructured information
Case Object Model
Represents the full details of a case and its parties
Provides a centralized representation of the case, enabling a 360deg view. Allows case tasks to coordinate and share information.
Case objects have lifecycles and persist over time
Traditional BPM process are often fleeting, leaving only a summary audit trail. Persisted case objects can store case data and documents that can be retained, records-managed, and disposed appropriately.
Supports relationships between cases
[Note: currently supported in the Case Model but not in the UI or REST APIs. Improvements being made in 5.1]
Track relationships between cases, including parents of split cases (in 5.1)
Leverages the full richness of folders
Everything you can do with a P8 folder, you can do with a case. Store documents in it, update its properties through workflows or APIs, leverage active content, etc. This is also how we provide the next two bullets.
Stores case documents by reference for efficiency
Seems like an “in the weeds” detail, but I can’t count how many times I’ve been asked this
Implication is that you can share documents between cases or between cases and other P8 folders
Provides detailed case, folder, and document-level security
Stems from the fact that a case is a folder. Means you can have security on the case itself, it’s sub-folders, and any of its documents
Task Object Model
Unique model for managing unstructured work
Specifically, the model is one of loosely coupled work around a case, driven by external or internal case events. This is what allows a case to be more flexible than a single end-to-end process. No matter how completely you model a single process, you can’t capture all possible real-world scenarios. The Task model allows you to just model the chunks of work that may need to get performed on a case. Then, separately, you model the events and conditions that trigger that work. These events and conditions include: 1) a case worker determined some piece of work needs to be performed, 2) a document was added to the case, 3) a document of a specific type was added to the case, 4) a case property (or properties) were updated and the case now meets some criteria, 5) another related piece of work was started, 6) an alternative piece of work was started so this one should no longer be available
Provides an ability for ah-hoc activities
Beyond allowing case workers the ability to kick-off work at runtime, Case Manager also allows case workers to define new work.
Using a basic “user created task” template (such as “document review” or “author response”), a case worker can fill in the details of the work at runtime (e.g. which people or groups are responsible for the work, and which documents should be sent to those people)
New “user created task” templates can be authored at design time
Allows the case to respond to external events
The unique model mentioned above is what allows the case to respond flexibly to events
Provides a detailed audit trail of activities
The process associated with each task has a full workflow history. Tasks record their start and finish in the case history.
Tasks automatically synchronize their data back with the case properties after each step [note: this is only for CaseBuilder-defined tasks. Other types of tasks, when available, may only synchronize back with case properties upon task completion]
Case APIs
REST APIs over the case infrastructure for custom Web 2.0 development and interfaces
All the power of the Case Client is exposed in APIs
Main point I usually make on these APIs is that we use them ourselves in the out-of-the-box Client. And that all the functionality we perform in the client is done through these APIs (i.e. there are no hidden APIs)
Solution Constructs
Built-in construct for containing solution assets
[Note: not all assets are yet contained in the solution definition. We’re making progress in 5.1, but this will take several releases]
Value is that this minimizes the various places you have to manage/track solution assets
Enables a rapid, iterative design/test sandbox
This is the primary value that our solutions offer. Rapid design/test against any target environment
Solutions can be templates that are reused
Server independent, allowing for portability
When designing a solution, you don’t need to worry about all the complex details of your P8 server environment. All that is managed separately through different admin/deployment tools. This makes it easier to focus on the solution design issues separately from the solution deployment issues
Case Analytics Data Store
Predefined structures for storing all case-related information for analytics
By default, tracks both case and task level state, processing time, and counts
Real-time and historical/summarized
Used by both Case Monitor for real-time and Case Analyzer for historical
Structured and unstructured information
This is referring mainly to our content analytics capability. Which, conceptually, sits alongside the real- time and historical data store
Analyzes business-level case data (e.g. dollar amounts), enabling real impact assessments
This is probably the most critical piece. You can pass any case property through to the Case Analytics Data Store for use in your reports, dashboards, or content analytics. This allows you to answer questions like “what is the total dollar value of all of my currently open cases of type X”
Bottom line: IBM Case Manager provides a comprehensive and extensible case infrastructure to quickly build a case-based solution 19 19

20. Case instance Cases are persisted as content in a folder structure
Case data lives on long beyond any individual task or action in a case
All content management functionality can be applied to the case and its content
Task
Comments are case folder annotations
Tasks
Case instance comes from a Case Type
Case folder
Properties
Annotations
Case comment
Containment
History
Other folder
CE Audit
Log
Folder structure was defined in the Case Type
Case History
Containment
Document
Documents comes from a document class

21. Case lifecycle
Complete
Case Created
Case creation
triggers
event handler
No running tasks,
and all “Required
Task” completed
After all tasks
are created
New
Initializing
Working
Error
condition
Failed
Case is created in a new state, but that triggers the case creation event handler that moves the state to initializing
The case creation event handler creates all the tasks and copy folder structure from case template

22. Process fragment is automatically launched
Task lifecycle
Waiting
Complete
Failed
Working
Ready
Case Created
Ad-Hoc Task
Created
Manual or
Automatic
transition
Pre-condition
triggered
Transition
Under
process
control
Process fragment is automatically launched
Waiting to Ready transition immediately when there is no precondition
Ready to Working transition immediately for automatic tasks
Ready to Working transition manually by the Case Worker executing the task
Ad-Hoc tasks are automatic and have no preconditions, so they transition immediately from waiting to ready to working

23. Case split relationship
Split cases are related via a case relationship link
History in both cases reflect the split
User interface allow navigation between related cases via the history
Task
Case folder
Properties
Case folder
Properties
Case relationship link
Case comment
Document
Document
Task
Case comment
Bidirectional link object with description, and type = split

24. Basic deployment topology
Development Domain
Case Builder
Case Client
Solution
Business Space Server and database (shared)
Deploy
Project Area 1
Target
Object
Store 1
Project Area n
Store n
. . .
Design
Object
Store
Solution
Data Set
Initialize
Export
Filenet Deployment Manager
Case Manager
Administration Client
Solution
Package
Assets created outside Case Builder
Data Set
Import
User Acceptant Testing (UAT) Domain
Case Client
Business Space Server and database
Design
Object
Store
Deploy
Target
Object
Store 1
Target
Object
Store n
. . .
Solution

25. Target object store folder structure
Solution Deployments
Root Folder
IBM Case Manager
Case Types
<Solution name> -
<case name>
Case Structure +
Cases
<year>
<month>
<day>
<hour>
<case instance>
Contains all the solutions deployed in this object store
Contains for each Case Type, the information needed to create case instances.
Cases are stored in a year, month, day, hour folder structure to avoid large amount of instances in a single folder
Actual case folder

26. P8 task implementation
Task workflow structures live in the same object store as the case data
Very efficient interaction between case data and workflow
Target Object Store
Isolated Region
Solution
Application Space
Case
Task
Role
In-Basket
In-Basket
Workflow
work
Queue
Inbox
Queue
Roster
Event
Log

27. Case Builder and P8 Process Designer
Roundtrip between Case Builder and P8 Process Designer is useful
Full P8 BPM functionality can be implemented this way
Roles, In-Baskets, and Tasks implemented with Case Builder can be modified and enhanced using the P8 Process Designer
. . -
. . -
Business
Analyst
Process
Designer
Design Object Store
Solutions
<Solution name>
Solution Workflow Collection
PE Configuration
Solution Definition
<case name> XPDL -
Browser
P8 Process Designer
Case Builder

28. P8 task runtime
Case data lives in the case folder, but can be accessed from the workflows
F_CaseFolder.<property name> to access case properties
F_CaseTask.<property> to access task information
Case Client
Case REST API
Target Object Store
Task
Case folder
Properties
Document
Isolated Region
Case comment
Workflow
In-Basket
Direct access
to case data
Event
Log
Roster
work
Queue
Attachments
Audit
Log
Case Analyzer
Event Dispatcher
Publisher

29. External data support
Each solution can be configured to invoke a REST external data service
This external data service is used by the Case REST API when case data is retrieved
The external data service can be used to
Influence property values based on data from an external source
Modify property attributes (for example minimum and maximum)
Enforce dependencies between properties
The external data service must implement a POST operation
The payload contains the relevant case data plus a request mode
The returned payload is merged with the case data and returned to the case client

30. . . . External data support Browser Business Space Case Widgets
Widgets do not interact with the external data service
Customer provides REST feed to provide external data
Single external data service per solution
Process work items,
retrieve work,
In-basket, etc.
Interact with
documents,
Search, etc
Create cases,
modify case properties,
case history, comments, etc.
Application Server
PE REST
CMIS
Case REST
External Data Service
REST
External System
External
Data
External System
External
Data
. . .
Case REST API merges data from Case Folder with external data from external data service

31. Interaction diagram for case creation using external data
Client
Case
REST
API
External
Data
Service
ICM
Server
Add case
Get default case
Properties and attributes
Initial New Object
Dependent property change
In Process Changes
Optional
Add
Final New Object
Create case

32. Interaction diagram for using external data
Case
Client
Case
REST
API
External
Data
Service
ICM
Server
Get Case Object
Get case instance
properties and attributes
Initial Existing Object
Dependent property change
In Process Changes
Optional
Complete
Final Existing Object
Update case

33. Powerful analytics for better case outcomes
3333
Powerful analytics for better case outcomes
Case Analytics
Structured Unstructured
Real time Persisted
Comprehensive reporting and analysis Gives case managers visibility across all information types to assess and act quickly
Real-time dashboards Understand issues before they become a problem
Unique content analytics for discovering deeper case insight
Crawl and index case content and metadata. Discover patterns, trends and insights across cases
Case Analyzer (Historical Reporting)
Excel and Cognos enable case and process analysis
Dynamic - Drill down, slice and dice, filter, etc
High performance, large volume analysis
Case Monitor (Real Time Dashboards)
Cognos RTM 10.1 provides real time cases and process monitoring
Threshold monitoring and alert generation
Content Analytics
Crawl and index case contents and metadata
Discover patterns, trends and insights across cases
Example : Most common compliant in user comments in cases
Bottom line: Case managers need insight in order to impact results. 33 33

34. IBM Case Manager – case analytics
Case Analyzer (Historical Reporting)
Excel and Cognos enable case and process analysis
Dynamic - Drill down, slice and dice, filter, etc
High performance, large volume analysis
Case Monitor (Real Time Dashboards)
Cognos RTM 10.1 provides real time cases monitoring
Threshold monitoring and alert generation
Case Analyzer (Historical Reporting)
Provides Excel and Cognos reports to enable case and process analysis
Dynamic analysis (drill down, slice and dice, filter, etc) of historical trends
Based on Online Analytical Processing (OLAP) technology to support high performance dynamic queries on large data sets
Case Monitor (Real Time Dashboards)
Data processed by Cognos RTM environment to provide real time monitoring of cases and processes
Threshold monitoring and alert generation
Real time dashboards for current data
Content Analytics
Crawling and indexing of case contents and metadata
Discovers trends and anomalies across cases
How frequently do textual patterns occur across cases
e.g. most common compliant in user comments in cases
Content Analytics
Crawl and index case contents and metadata
Discover patterns, trends and insights across cases
Example : Most common compliant in user comments in cases 34 34 34

35. Case analyzer
Case Analyzer combines content and process information to present a real time picture of the case
Case Analyzer
Reports and Dashboards
Dimension
cache
Cognos Real Time Monitor
Case Monitor Dashboard
(Business Activity Monitor)
Cognos BI
reports
Event
Dispatcher
Publisher
Case Analyzer Database
Object Store Isolated Region
Fact
Tables’
OLAP
Database CE
Audit
Log PE
Event
Log
Build OLAP cubes
Target Object Store

36. Underlying capabilities
3636
Underlying capabilities
Collaboration
& Social SW
Monitoring & Analytics
Content
Workflow
Rules
Events
Integration
Integrated and bundled capabilities:
Content Management
Process Management
WebSphere ILOG jRules*
Content Analytics (Text analytics)*
Cognos Real Time Monitoring (Real time analytics)*
Lotus SameTime (embedded awareness in case runtime and web chat)*
Bottom line: IBM Case Manager leverages and integrates best of breed capabilities from across IBM
Case Object Model
Represents the full details of a case and its parties
Provides a centralized representation of the case, enabling a 360deg view. Allows case tasks to coordinate and share information.
Case objects have lifecycles and persist over time
Traditional BPM process are often fleeting, leaving only a summary audit trail. Persisted case objects can store case data and documents that can be retained, records-managed, and disposed appropriately.
Supports relationships between cases
[Note: currently supported in the Case Model but not in the UI or REST APIs. Improvements being made in 5.1]
Track relationships between cases, including parents of split cases (in 5.1)
Leverages the full richness of folders
Everything you can do with a P8 folder, you can do with a case. Store documents in it, update its properties through workflows or APIs, leverage active content, etc. This is also how we provide the next two bullets.
Stores case documents by reference for efficiency
Seems like an “in the weeds” detail, but I can’t count how many times I’ve been asked this
Implication is that you can share documents between cases or between cases and other P8 folders
Provides detailed case, folder, and document-level security
Stems from the fact that a case is a folder. Means you can have security on the case itself, it’s sub-folders, and any of its documents
Task Object Model
Unique model for managing unstructured work
Specifically, the model is one of loosely coupled work around a case, driven by external or internal case events. This is what allows a case to be more flexible than a single end-to-end process. No matter how completely you model a single process, you can’t capture all possible real-world scenarios. The Task model allows you to just model the chunks of work that may need to get performed on a case. Then, separately, you model the events and conditions that trigger that work. These events and conditions include: 1) a case worker determined some piece of work needs to be performed, 2) a document was added to the case, 3) a document of a specific type was added to the case, 4) a case property (or properties) were updated and the case now meets some criteria, 5) another related piece of work was started, 6) an alternative piece of work was started so this one should no longer be available
Provides an ability for ah-hoc activities
Beyond allowing case workers the ability to kick-off work at runtime, Case Manager also allows case workers to define new work.
Using a basic “user created task” template (such as “document review” or “author response”), a case worker can fill in the details of the work at runtime (e.g. which people or groups are responsible for the work, and which documents should be sent to those people)
New “user created task” templates can be authored at design time
Allows the case to respond to external events
The unique model mentioned above is what allows the case to respond flexibly to events
Provides a detailed audit trail of activities
The process associated with each task has a full workflow history. Tasks record their start and finish in the case history.
Tasks automatically synchronize their data back with the case properties after each step [note: this is only for CaseBuilder-defined tasks. Other types of tasks, when available, may only synchronize back with case properties upon task completion]
Case APIs
REST APIs over the case infrastructure for custom Web 2.0 development and interfaces
All the power of the Case Client is exposed in APIs
Main point I usually make on these APIs is that we use them ourselves in the out-of-the-box Client. And that all the functionality we perform in the client is done through these APIs (i.e. there are no hidden APIs)
Solution Constructs
Built-in construct for containing solution assets
[Note: not all assets are yet contained in the solution definition. We’re making progress in 5.1, but this will take several releases]
Value is that this minimizes the various places you have to manage/track solution assets
Enables a rapid, iterative design/test sandbox
This is the primary value that our solutions offer. Rapid design/test against any target environment
Solutions can be templates that are reused
Server independent, allowing for portability
When designing a solution, you don’t need to worry about all the complex details of your P8 server environment. All that is managed separately through different admin/deployment tools. This makes it easier to focus on the solution design issues separately from the solution deployment issues
Case Analytics Data Store
Predefined structures for storing all case-related information for analytics
By default, tracks both case and task level state, processing time, and counts
Real-time and historical/summarized
Used by both Case Monitor for real-time and Case Analyzer for historical
Structured and unstructured information
This is referring mainly to our content analytics capability. Which, conceptually, sits alongside the real- time and historical data store
Analyzes business-level case data (e.g. dollar amounts), enabling real impact assessments
This is probably the most critical piece. You can pass any case property through to the Case Analytics Data Store for use in your reports, dashboards, or content analytics. This allows you to answer questions like “what is the total dollar value of all of my currently open cases of type X”
*Denotes usage limited to case solutions 36 36

37. CM8 support Browser Case Client Case Builder Application Server
Case REST
PE REST
P8 CMIS
CM8 CMIS
Target Object Store
CM Repository
CM8 Adaptor
Case folder
Proxy case folder
Proxy
CM8 Docs
CM8 Docs
ICM Adaptor

38. Development Environment
IBM BPM integration
Case Builder can introspect a Process Center repository to locate processes to invoke as case tasks
Development Environment
Design Object Store
Deployment target
Project Area
Target Object Store
Project Area
Solution
PE Region
Solution
Solution
Case Builder
Business Space
Process Center
Process Server
Export Solutions
Production Environments
Are project areas reflected in the prod environment as shown above?
Design Object Store
Deployment target
Solution
Solution
Solution
Target Object Store
PE Region
Business Space
Process Server 38

39. Example P8 Domain IBM BPM Process Server 1 Target Object Store 1
Solution 1
Process Application 1
Process 1
Process 2
Case Type 1
Task A
Task B
Solution 2
Process Application 2
Process 1
Case Type 2
Task C
Process Application 3
Process 1
Process 2
Target Object Store 2
Configure:
TOS/connection definition/target environment
Solution 3
Case Type 1
Task A
IBM BPM Process Server 2
Target Object Store 3
Solution 4
Process Application 4
Process 1
Case Type 1
Task A 39

40. Executing a task in IBM BPM
Task invocation of IBM BPM processes is done via transactional Web Services
Target Object Store
IBM BPM Process Server
BPM Web
API
Case folder
Properties
Document
Start BPM
Process
IBM BPM Web
Services Start
Process
Callback
information
Task
Audit
Log
ICM
Callback
Notify BPM
process completion
ICM Web
Services
callback

41. Federated in-basket
A Business Space In-Basket widget that federates work items from Case Management, Human tasks, BPEL processes, and WLE processes

42. Distinguished Engineer
Mike Marin
Distinguished Engineer
IBM