Workflow

About: Workflow is a research topic. Over the lifetime, 31996 publications have been published within this topic receiving 498339 citations.

Workflow manager for a distributed system

Abstract: A workflow manager handles the communication between a workflow-enabled provider and a workflow-enabled client. The workflow manager maintains a directory of clients, translates a transaction from a provider into multiple transactions suitable for the client, and handles security. In one embodiment, the workflow manager connects with the workflow-enabled client by registration and with the workflow-enabled provider by advertising and activation. Subsequent communications between the workflow manager and the workflow-enabled provider and the workflow-enabled client are with a request/response protocol. The workflow manager also comprises data storage for storing data for transmission to the workflow-enabled client or the workflow-enabled provider, and workflow storage for storing information related to registered clients. The present invention also includes a number of novel methods including a method for a method for registering a client and a method for activating a provider.

Enterprise system implementation and employee: understanding the role of advice networks

Abstract: The implementation of enterprise systems, such as enterprise resource planning (ERP) systems, alters business processes and associated workflows, and introduces new software applications that employees must use. Employees frequently find such technology-enabled organizational change to be a major challenge. Although many challenges related to such changes have been discussed in prior work, little research has focused on post-implementation job outcomes of employees affected by such change. We draw from social network theory-- specifically, advice networks--to understand a key post-implementation job outcome (i.e., job performance). We conducted a study among 87 employees, with data gathered before and after the implementation of an ERP system module in a business unit of a large organization. We found support for our hypotheses that workflow advice and software advice are associated with job performance. Further, as predicted, we found that the interactions of workflow and software get-advice, workflow and software give-advice, and software get- and give-advice were associated with job performance. This nuanced treatment of advice networks advances our understanding of post-implementation success of enterprise systems.

The view-based approach to dynamic inter-organizational workflow cooperation

Abstract: This paper presents a novel approach to inter-organizational workflow cooperation. Our goal is to provide support for organizations which are involved in a shared but not pre-modeled cooperative workflow across organizational boundaries. Our approach allows for partial visibility of workflows and their resources, thus providing powerful ways for inter-organizational workflow configuration. Varying degrees of visibility of workflows enable organizations to retain required levels of privacy and security of internal workflows. Our presented view concept provides a high degree of flexibility for participating organizations, since internal structures of collaborative workflows may be adapted without changes in the inter-organizational workflows. Furthermore, we provide workflow participants with the freedom to change their work-flows without changing their roles in the cooperation. This increases flexibility and is an important step to increase efficiency as well as reduction in costs for inter-organizational workflows. The presented approach is inspired by the Service-oriented Architecture (SOA). Accordingly, our approach consists of three steps: workflow advertisement, workflow interconnection, and workflow cooperation.

Clinical Workflows - The Killer Application for Process-oriented Information Systems?

Abstract: There is an increasing interest in changing information systems to support business processes in a more direct way. Workflow technology is a very interesting candidate to achieve this goal. Hence the important question arises, how far do we get using this technology? Is its functionality powerful enough to support a wide range of applications or is it only suitable for rather simple ones? And, if the latter is the case, are the missing functions of the “just to do” type or are more fundamental issues addressed? The paper uses the clinical domain to motivate and to elaborate the functionality needed to adequately support an advanced application environment. It shows that workflow technology is still lacking important features to serve this domain. The paper surveys the state of the art and it presents solutions for some issues based on the concepts elaborated in the ADEPT project.