[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-244098-105":53,"doc-detail-244098-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","beyond-workflow-management-product-driven-case-handling","Beyond Workflow Management - Product-Driven Case Handling","","Workflow technology has evolved into a core building block for enterprise information systems, yet contemporary workflow management remains constrained to well-defined and tightly controlled environments. In practice, limited flexibility causes failures when processes involve non-trivial variations and exceptions. The paper argues for a paradigm shift where workflows are driven by the products they generate rather than by pre-specified control flows, and introduces FLOWer as a software package supporting product-driven case handling.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/beyond-workflow-management-product-driven-case-handling/244098/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/beyond-workflow-management-product-driven-case-handling/244098.png","ImageObject",442,249,{"name":88,"@type":89},"McGucket","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",10,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"Why do workflow management systems often fail in real-world use?","Question",{"text":109,"@type":110},"Because their flexibility is limited and they rely on rigid, pre-specified control flows that struggle with non-trivial exceptions and process variability.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What paradigm shift does the paper propose?",{"text":114,"@type":110},"Workflows should be driven by the products they generate (the case) rather than by pre-specified control-flow routing.",{"name":116,"@type":107,"acceptedAnswer":117},"How does FLOWer support the proposed approach?",{"text":118,"@type":110},"FLOWer is presented as a software package that fully supports product-driven case handling, enabling work support, distribution, and management under this paradigm.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},244098,1791719229,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":101,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":79},1236954412713,"https://us-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Beyond Workflow Management: Product-Driven Case Handling  \nW. M. P. van der Aalst  \nDepartment of Technology Management Eindhoven University of Technology P.O. Box 513, NL-5600 MB, Eindhoven The Netherlands  \n[w.m.p.v.d.aalst@tm.tue.nl](w.m.p.v.d.aalst@tm.tue.nl)  \nP.J.S. Berens  \nPallas Athena  \nP.O. Box 747  \nNL 7300 AS, Apeldoorn The Netherlands  \n[paul.berens@pallas-athena.com](paul.berens@pallas-athena.com)  \nABSTRACT  \nIn the last decade, workflow technology has become one of the building blocks for realizing enterprise information systems. Unfortunately, the application of contemporary workflow management systems is limited to well-defined and wellcontrolled environments. In practice, workflow technology often fails because of limited flexibility. We advocate a paradigm shift to overcome this problem: Workflows should not be driven by pre-specified control-flows but by the products they generate. This paper presents the software package FLOWer which fully supports this paradigm shift.  \nCategories and Subject Descriptors  \nH.4.1 [Information Systems Applications]: Office AutomationWorkflow management.  \nGeneral Terms  \nManagement, Design, Human Factors, Languages, Theory, Verification.  \nKeywords  \nWorkflow management, case handling, workflow management systems, product-driven design, FLOWer.  \n1. INTRODUCTION  \nIn the last three decades, there have been many attempts to build information systems to support (business) processes. What was called ‘office automation’ in the mid-70s is nowadays called‘workflow management’. From a technological point of view, much progress has been made. Moreover, processes moved from second-class citizens to first-class citizens of the enterprise information system. The traditional data-oriented approaches have been replaced by process-oriented paradigms (e.g., BPR, CPI, etc.) [9] . Unfortunately, despite all the jubilant stories of suppliers, the application of workflow management (WFM)  \nPermission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.  \nGROUP'01, Sept. 30-Oct. 3, 2001, Boulder, Colorado, USA.  \nCopyright 2001 ACM 1-58113-294-8/01/0009 ... $5 .00.  \nsystems [12,15,18] is still limited. Where WFM is actually applied, it is clear that the majority of the supported processes are very simple. For more complex processes, WFM systems are either not applicable or require considerable modeling and implementation efforts. For non-trivial processes, the degree of customization is typically high. The process models driving the WFM system are either kept simple by removing all flexibility or are complex and non-transparent to address exceptions adequately.  \nIf the process model is kept simple, only a more or less idealized version of the preferred process is supported. As a result, the real run-time process is often much more variable than the process specified at design-time. The only way to handle changes is to go behind the system’s back. If users are forced to bypass the WFM system quite frequently, the system is more aliability than an asset. If the process model attempts to capture all possible exceptions [20], the resulting model becomes too complex to manage and maintain.  \nMany authors have pointed out the importance of workflow flexibility, e.g., many workshops and special issues of journals have been devoted to the topic [3,5,13,14] . Few of the results reported are really applicable in a practical setting and the impact on contemporary WFM systems is limited. We argue that the core of the problem is the fact that routing is the only mechanism driving the workflow, i.e., work is moved from on worktray to another based on pre-specifie","cbCaicInMr5ffBZp","https://ap.wps.com/l/cbCaicInMr5ffBZp","pdf",268502,"English","# Abstract\n# 1. Introduction\n## Problem with Control-Flow Driven WFM\n## Proposed Paradigm Shift: Case-Driven Workflows\n## FLOWer and Product-Driven Case Handling","[{\"question\":\"Why do workflow management systems often fail in real-world use?\",\"answer\":\"Because their flexibility is limited and they rely on rigid, pre-specified control flows that struggle with non-trivial exceptions and process variability.\"},{\"question\":\"What paradigm shift does the paper propose?\",\"answer\":\"Workflows should be driven by the products they generate (the case) rather than by pre-specified control-flow routing.\"},{\"question\":\"How does FLOWer support the proposed approach?\",\"answer\":\"FLOWer is presented as a software package that fully supports product-driven case handling, enabling work support, distribution, and management under this paradigm.\"}]","Beyond Workflow Management - Product-Driven Case Handling | PDF",1789212102]