scispace - formally typeset
Search or ask a question
Topic

Workflow

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


Papers
More filters
Patent
20 Apr 2006
TL;DR: Workflow Templates as discussed by the authors provide the means to create, define and store the name and definition of and 'trigger points' for each workflow item, and trigger points for when a document is used are also determined when creating the template.
Abstract: The present invention facilitates the creation and implementation of Workflow Templates and also the designation of linkage between these templates and specific projects dealing with different media type handling. Workflow Templates are used to automatically generate user interface views which will be used by agents, knowledge workers, supervisors and customers. Such Workflow Templates provide the means to create, define and store the name and definition of and 'trigger points' for each workflow item. The trigger points for when a document is used are also determined when creating the template. Further, in creating a Workflow Templates the administrator can instruct the system to save scripts associated with the template that can be saved as XML, EDI, JSP, CGI, VXML, etc. so as to be able to automatically generate documents or logic flows consistent with the target media type for the anticipated interactions with customers.

109 citations

Patent
24 Jan 2008
TL;DR: In this article, a business process can be launched by one of the data systems to update the target data and any related data in the repository or any other related repository, such that the data can be modified, added to, rejected, or otherwise processed before being added to the appropriate repositories.
Abstract: A data repository includes information for multiple data systems, which can each control data in this and a number of other domains. A business process can be launched by one of the data systems to update the target data and any related data in the repository or any other related repository. Any request to update data is intercepted and the business process can launch workflows and apply policies as needed to process the request. Workflows can be associated with the fields being updated or process being executed, such that any update to the target data is also accurately reflected in any other related system. Further, launching a workflow allows processes to be run before the data is updated, such that the data can be modified, added to, rejected, or otherwise processed before being added to the appropriate repositories.

109 citations

Patent
25 Mar 2010
TL;DR: In this article, a computer-based system and method of providing document isolation during routing of a document through a workflow is disclosed, which comprises maintaining a separate "working" copy of the original base document while the document is routed through the workflow.
Abstract: A computer based system and method of providing document isolation during routing of a document through a workflow is disclosed. The method comprises maintaining a separate “working” copy of the original base document while the document is routed through a workflow. Access controls, which define who may access the original document as well as any versions of the working copy document, are defined and stored in relation to the documents. The access controls further define the types of actions users may take with respect to the document. Users are selectively directed to the appropriate document, either the base document or working copy, and selectively granted permission to perform publishing operations on the working copy document, as determined by the access controls.

109 citations

Book ChapterDOI
03 May 2006
TL;DR: This work develops a simple provenance model capable of supporting a wide range of scientific use cases even for complex models of computation such as process networks, and is capable of reconstructing complete data and invocation dependency graphs for a workflow run.
Abstract: Integrated provenance support promises to be a chief advantage of scientific workflow systems over script-based alternatives. While it is often recognized that information gathered during scientific workflow execution can be used automatically to increase fault tolerance (via checkpointing) and to optimize performance (by reusing intermediate data products in future runs), it is perhaps more significant that provenance information may also be used by scientists to reproduce results from earlier runs, to explain unexpected results, and to prepare results for publication. Current workflow systems offer little or no direct support for these “scientist-oriented” queries of provenance information. Indeed the use of advanced execution models in scientific workflows (e.g. process networks, which exhibit pipeline parallelism over streaming data) and failure to record certain fundamental events such as state resets of processes, can render existing provenance schemas useless for scientific applications of provenance. We develop a simple provenance model that is capable of supporting a wide range of scientific use cases even for complex models of computation such as process networks. Our approach reduces these use cases to database queries over event logs, and is capable of reconstructing complete data and invocation dependency graphs for a workflow run.

109 citations

Book ChapterDOI
03 Nov 2003
TL;DR: This work proposes an infrastructure level support for a provenance recording capability for service-oriented architectures such as the Grid and Web Services and provides a mechanism by which provenance is used to determine whether previous computed results are still up to date.
Abstract: Large-scale, dynamic and open environments such as the Grid and Web Services build upon existing computing infrastructures to supply dependable and consistent large-scale computational systems. This kind of architecture has been adopted by the business and scientific communities allowing them to exploit extensive and diverse computing resources to perform complex data processing tasks. In such systems, results are often derived by composing multiple, geographically distributed, heterogeneous services as specified by intricate workflow management. This leads to the undesirable situation where the results are known, but the means by which they were achieved is not. With both scientific experiments and business transactions, the notion of lineage and dataset derivation is of paramount importance since without it, information is potentially worthless. We address the issue of data provenance, the description of the origin of a piece of data, in these environments showing the requirements, uses and implementation difficulties. We propose an infrastructure level support for a provenance recording capability for service-oriented architectures such as the Grid and Web Services. We also offer services to view and retrieve provenance and we provide a mechanism by which provenance is used to determine whether previous computed results are still up to date.

109 citations


Network Information
Related Topics (5)
Software
130.5K papers, 2M citations
89% related
Information system
107.5K papers, 1.8M citations
84% related
The Internet
213.2K papers, 3.8M citations
82% related
Deep learning
79.8K papers, 2.1M citations
82% related
Cluster analysis
146.5K papers, 2.9M citations
81% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
20241
20234,414
20229,010
20211,461
20201,579
20191,702