[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-203369-105":59,"doc-detail-203369-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","workflow-data-patterns-beta","Workflow Data Patterns - BETA","","Workflow systems enable execution of complex, recurring business processes, yet commercial workflow management tools differ in how well they model and implement the diverse requirements found during workflow requirements analysis. Building on prior work on workflow control patterns, this paper presents a series of workflow data patterns that describe how data is represented and used. The patterns remain independent of specific technologies and modeling languages, enabling a comprehensive view of the workflow data perspective and supporting detailed comparisons across commercial workflow systems and business process modeling languages.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":40,"@type":76,"position":81},"https://docshare.wps.com/document/research-report/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/workflow-data-patterns-beta/203369/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/workflow-data-patterns-beta/203369.png","ImageObject",300,407,{"name":92,"@type":93},"Quinn","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-08","2026-09-04",true,{"@type":102,"interactionType":103,"userInteractionCount":81},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What problem do workflow data patterns address in workflow systems?","Question",{"text":112,"@type":113},"They capture the ways data is represented and utilized in workflows, helping explain how requirements related to data are modeled across different workflow engines.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"How do the workflow data patterns improve comparison across tools and languages?",{"text":117,"@type":113},"By being independent of specific workflow technologies and modeling languages, they provide a consistent basis to compare data-related capabilities across products and languages.",{"name":119,"@type":110,"acceptedAnswer":120},"What prior work does this paper build upon?",{"text":121,"@type":113},"It extends earlier research on workflow control patterns by applying a patterns-based approach specifically to the data perspective and identifying 39 recurring data patterns.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},203369,1788560358,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":39,"category_name":40,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":81,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":139,"language":140,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":67,"update_tm":129,"read_time":144},962075114765,"https://ap-avatar.wpscdn.com/davatar_a8503ba1806abce46bf441b54a3ca4cd","WORKFLOW DATA PATTERNS  \nNick Russell 1 , Arthur H.M. ter Hofstede 1 , David Edmond 1  \n1 Centre for Information Technology Innovation, Queensland University of Technology  \nGPO Box 2434, Brisbane QLD 4001, Australia  \n{n.russell,a.terhofstede, [d.edmond}@qut.edu.au](d.edmond}@qut.edu.au)  \nWil M.P. van der Aalst 1 ;2  \n2 Department of Technology Management, Eindhoven University of Technology  \nGPO Box 513, NL-5600 MB Eindhoven, The Netherlands [w.m.p.v.d.aalst@tm.tue.nl](w.m.p.v.d.aalst@tm.tue.nl)  \nAbstract  \nWork􀀍ow systems seek to provide an implementation vehicle for complex, recurring business processes. Notwithstanding this common objective, there are a variety of distinct features o􀀋ered by commercial work􀀍ow management systems. These di􀀋erences result in signi􀀌cant variations in the ability of distinct tools to represent and implement the plethora of requirements that may arise in contemporary business processes. Many of these requirements recur quite frequently during the requirements analysis activity for work􀀍ow systems and abstractions of these requirements serve as a useful means of identifying the key components of work􀀍ow languages.  \nPrevious work has identi􀀌ed a number of work􀀍ow control patterns which characterise the range of control 􀀍ow constructs that might be encountered when modelling and analysing work􀀍ow. In this paper, we describe a series of work􀀍ow data patterns that aim to capture the various ways in which data is represented and utilised in work􀀍ows. By delineating these patterns in a form that is independent of speci􀀌c work􀀍ow technologies and modelling languages, we are able to provide a comprehensive treatment of the work􀀍ow data perspective and we subsequently use these patterns as the basis for a detailed comparison of a number of commercially available work􀀍ow management systems and business process modelling languages.  \nKeywords: Patterns, Data, Work􀀍ow, Business Process Modelling  \n1 Introduction  \nThere are a series of concepts that apply to the representation and utilisation of data within work􀀍ow systems. These concepts not only de􀀌ne the manner in which data in its various forms can be employed within a business process and the range of informational concepts that a work􀀍ow engine is able to capture but also characterise the interaction of data elements with other work􀀍ow and environmental constructs.  \nDetailed examination of a number of work􀀍ow tools and business process modelling paradigms suggests that the way in which data is structured and utilized within these tools has a number of common characteristics. Indeed these characteristics  \nbear striking similarities to the Work􀀍ow Patterns [AHKB03] and Design Patterns [GHJV95] initiatives in terms of their generic applicability across the class of work􀀍ow engines, except in this case, they refer speci􀀌cally to the data perspective of work􀀍ow systems and the manner in which it interrelates with other work􀀍ow perspectives.  \nThe use of a patterns-based approach for illustrating data-related concepts in work􀀍ow systems o􀀋ers the potential to describe these concepts in a language-independent way. This ensures that the patterns identi􀀌ed have broad applicability across a wide variety of work􀀍ow implementations. It provides the basis for comparison of data-related capabilities between distinct products and o􀀋ers a means of identifying potential areas of new functionality in work􀀍ow systems. In this paper we focus on work􀀍ow technology but the results identi􀀌ed apply to any process-aware information system (PAIS) .  \n1.1 Background and related work  \nInterest in work􀀍ow systems has grown dramatically over the past decade and is evidenced by the uptake in membership of industry bodies such as the Work􀀍ow Management Coalition [Wor04] which now lists 270 vendors, associate and academic members. This has fuelled the development of a multitude of work􀀍ow engines each with unique features and capabilities, yet despite attempts by industry bodi","cbCailZ5QxHev84i","https://ap.wps.com/l/cbCailZ5QxHev84i","pdf",432139,75,"English","# Abstract\n# Keywords\n# 1 Introduction\n## 1.1 Background and related work\n## 1.2 Structure of this paper","[{\"question\":\"What problem do workflow data patterns address in workflow systems?\",\"answer\":\"They capture the ways data is represented and utilized in workflows, helping explain how requirements related to data are modeled across different workflow engines.\"},{\"question\":\"How do the workflow data patterns improve comparison across tools and languages?\",\"answer\":\"By being independent of specific workflow technologies and modeling languages, they provide a consistent basis to compare data-related capabilities across products and languages.\"},{\"question\":\"What prior work does this paper build upon?\",\"answer\":\"It extends earlier research on workflow control patterns by applying a patterns-based approach specifically to the data perspective and identifying 39 recurring data patterns.\"}]","Workflow Data Patterns - BETA | PDF",189]