Pecunia Corp. We need to solve these issues: Module 1: Introduction 3 High costs for dealing with credit card disputes This is an expensive process even when the disputed money value is low. Long processes, unhappy customers Currently our dispute evaluation takes a long time compared to competitors. Decisions are not reproducible We have decisions being take by people and they need to manually work with repeatable decisions that could be automated. No tracing of the events that happened in each dispute There's no easy way for the business team to see what happens and take decisions based on facts;
Humans are frequently involved to add information and take decisions. The task sequence is quite pre-ordered. • Order fulﬁllment • Claims processing • Loan approvals • Mortgage origination • Travel requests • Purchase requests • Mobile workforce support “Orchestration” / “Choreography” of automated activities, humans by exception. • Trading processes (Capital Market, Banking, Energy ...) • Automatic claims processing • Automatic reordering • Inventory reduction / rebalancing • Order to cash automation Adaptive and dynamic processes: Knowledge Workers guide the activities ﬂow selecting among suggested options or creating on the ﬂy ad hoc activities. • Investigation solution • Next-Gen customer onboarding • Customer retention program • Personalized customer service • Omni-channel engagement marketing Straight Through Human Intensive Case Management Flexibility Automation
• Business processes - Usually modelled as ﬂow charts with starting points and ﬁnite end nodes. • Cases - not structured, dynamic ( with room for dynamic tasks) • Cases - reach a business goal through milestones • Cases - usually consist of loosely coupled process fragments that can be connected
Case; • Case ﬁle and documents marshallers are conﬁgured. • WorkDeﬁnition.wid ﬁles are created in the project and its packages to ensure case-related nodes such as Milestone and Cases are available in the case deﬁnition design palette. Case Projects
ﬁle data and attached documents across the entire case. org.jbpm.casemgmt.impl.marshalling.CaseMarshallerFactory.builder().withDoc().get(); new org.jbpm.document.marshalling.DocumentMarshallingStrategy();
used within cases. The "Per_Case" runtime strategy will make sure that the case data is properly shared within instances. If the sub process is in another project, the kiebase needs to be added to the case project.