feature requests for case manager by spar nord bank a/s ibm insight 2014 spar nord bank a/s1

1Spar Nord Bank A/S

Feature requests for

Case Manager

By Spar Nord Bank A/SIBM Insight 2014

Spar Nord Bank A/S 2

Complex dataFeature request

• Work with complex data inside Process Designero Allow the designer to read and write complex data to the case

• E.g. use the data in routing, web services etc.

• Work with complex data inside Case Buildero Allow the designer to see the complex data inside a given step

• This would allow the designer to create a layout for the complex data

• Reuse of presentation (/layout) of complex data

• Work with complex data inside Case Managero Allow the end user to view and edit data through a standard widget as

with the Case Properties widget


Case BuilderFeature requests #1

• Possibility to define ordering of tasks in “case details” (and “work item”)

• Extended pre-conditionso “Wait for other task”

• E.g. pre-condition that ensures that the task waits until another task is completedo Thus not simply using e.g. a boolean (case property)

o Multiple pre-conditions• E.g. wait for a document of type A AND a document of type B to be put on the case before

starting (and not only one document)• E.g. wait for a document of type A OR a document of type B to be put on the case before

starting (and not only one document)• E.g. wait for document AND property met

o Use system time as condition• Currently it can only wait for a given date, not a dynamic date defined e.g. in a running task

o “Complex pre-conditions”• E.g. allow the user to manually start a task OR wait for a property OR document (of a given

type) added

• Eventso Give the workflow designer the possibility to signal from one workflow that another can continue

• This can be achieved using a boolean value and a wait-for condition, but is not a single (system) step


Case BuilderFeature requests #2

• Extended filtering of in-basketso Allow filtering on in-baskets to be active as default for a roleo Make filters case-insensitiveo Allow users to add multiple filters of the same kind

• E.g. allow the user to add SSN = 123 AND SSN = 321 or SSN = 123 OR SSN = 321

• “Post-conditions”o Give the workflow designer the possibility to disable tasks

• E.g. if property is a given value is doesn’t make sense to start a given task any moreo Easy way of disabling tasks from workflow using a component step

• Give the workflow designer the possibility to allow only certain roles to start a caseo E.g. when working with cases that automatically transfers money

• Possibility to create document hierarchieso E.g. having Document -> Private customer -> Loan application

• This is possible only through FileNet directly and not through the Case Builder• The “add document” widget can display the hierarchy but not the Case Builder

• Possibility to hide a task until a given “event” occurs o E.g. document added, property met


Process DesignerFeature requests #1

• Versioning of workflowso Have a standard way of showing which version of the flow is currently used (not through a case

property)o Updating workflows will affect unstarted tasks on running cases. Having a version number can help

bug tracing etc.

• Possibility to define choice lists in local workflow properties rather than only as case property

• Possibility to move (/redefine) a route from one node to anothero Tedious to add nodes, especially when routes have conditions

• Allow assigning an empty array to a variable. o When declaring a String array, it always contains the empty string as its first element. In some

situations, we want to present an empty array to our users. Our workaround is having a custom java component that returns an empty array and assign that as value.

o An array contains the empty string before a split. The first path of the split fills the array with valid data (without the empty string). The second path does nothing. The override merge option can result in data loss if the second path is completed after the first. Hence the merge option “Append” is used. The “Append” option adds the empty string to the valid data. This behavior is not wanted. As a workaround, we initialize arrays as empty using a custom java component before a split.

• Add “Boolean and” and “Boolean or” as merge type for Boolean variables.



• Undo button• Back button

o Go back to the map you came from (e.g. when working with sub maps)

• Access to MQ directly from the designer through a component stepo Both produce and consume

• Import of existing component queueo E.g. component queue defined in another solution

• Add a comment to the commit when pressing “save” or “save and close”o E.g. as know from source control (e.g. SVN, git, etc.) when doing a

commit



• Web service integration that threats XML as datao Allow the designer to take a complex response (/multi layered XML)

from a web service and assign it directly to a Case or Task property

• Better handling of web service invoke stepso Working with XML is close to impossible

• The designer formats the code as a one line string, which is hard to read, as lines are not allowedo We use annotations for “pretty print” of XML, and paste it

directly into the “Invoke” stepo E.g. the possibility to test the invoke step directly in the designer


Process DesignerBug fixes

• Sometimes the process designer loses the connection and when trying to save all changes are lost

• Expression builder and assignmento sizeOf

• Works on a workflow property (e.g. myArray) but not on case property (e.g. F_CaseFolder.TEST_myArray)

o Access an index on a case property directly fails• E.g. F_CaseFolder.TEST_myArray[index] = “test”

o Allow conditions on routes to access case properties• Our current workaround is to copy the case property to a workflow

variable and perform the check against the workflow variable, but it should be possible to access the case properties directly


DeploymentFeature requests

• Partial deploymento Allow deploying a single case type from a solution that contains

multiple case typeso Could be placed during deployment similar to partner links

• Select one/more/all case types for deployment


In generalFeature requests #1

• Administration tool for caseso Process administrator is great for workflows, not so great for cases

• Possibility to see workflow properties in the tracker for e.g. system stepso Workflow properties are only displayed on manual steps, not on e.g. system

steps, delay etc.

• Possibility to delay a manual step at any given time (“remove” from in-basket)o The idea is that the user can define when a given step should be executed

• Useful if the step involves customer input (/etc.) and thus can only be executed when the customer is available

o E.g. during a meeting with the customer• Should not be modeled as delay, since the customer could provide the info

at any given time (thus it should be possible to find the step once “delayed”)

• Should be a generic solution and not defined/handled through filters on the in-basket


In generalFeature requests #2

• Audit trail on case basiso Having a single place to show what has happened on a case

• E.g. when did what user complete a step• E.g. what did the user do (/input)• E.g. what route was selected

• Define what properties are displayed on a document for each case typeo E.g. document with many properties

• Only show the properties relevant for the case type• E.g. when properties are mutually exclusive

feature requests for case manager by spar nord bank a/s ibm insight 2014 spar nord bank a/s1

Documents