Patents by Inventor Torsten Wecke

Torsten Wecke has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).

  • Patent number: 9721230
    Abstract: In a first method, a developer mode is determined when a workflow template patch is received, and execution of new workflow instances is either blocked or permitted, or continued execution of workflow instances is forbidden. In a second method, parallelization of workflow execution is provided in an in-memory database management system. In a third method, after received user privilege information, database records associated with a workflow are determined and stored for use at workflow instance runtime. In a fourth method, artifacts used by a workflow are identified using a workflow template. When a command to execute a workflow instance is received, information is stored for generating instances of artifacts for use during execution of the workflow instance. In a fifth method, for a workflow template to be inactivated, the associated workflow template is suspended after currently executing workflow instances have completed and job executors have acknowledged a suspending state.
    Type: Grant
    Filed: August 4, 2015
    Date of Patent: August 1, 2017
    Assignee: SAP SE
    Inventors: Ronald Trump, Harald Schubert, Tobias Breyer, Peter Gernold, Stefan Henke, Krassimir Kondarev, Torsten Wecke
  • Publication number: 20170039046
    Abstract: In a first method, a developer mode is determined when a workflow template patch is received, and execution of new workflow instances is either blocked or permitted, or continued execution of workflow instances is forbidden. In a second method, parallelization of workflow execution is provided in an in-memory database management system. In a third method, after received user privilege information, database records associated with a workflow are determined and stored for use at workflow instance runtime. In a fourth method, artifacts used by a workflow are identified using a workflow template. When a command to execute a workflow instance is received, information is stored for generating instances of artifacts for use during execution of the workflow instance. In a fifth method, for a workflow template to be inactivated, the associated workflow template is suspended after currently executing workflow instances have completed and job executors have acknowledged a suspending state.
    Type: Application
    Filed: August 4, 2015
    Publication date: February 9, 2017
    Inventors: Stefan Henke, Tobias Breyer, Harald Schubert, Krassimir Kondarev, Peter Gernold, Ronald Trump, Torsten Wecke
  • Publication number: 20170039492
    Abstract: In a first method, a developer mode is determined when a workflow template patch is received, and execution of new workflow instances is either blocked or permitted, or continued execution of workflow instances is forbidden. In a second method, parallelization of workflow execution is provided in an in-memory database management system. In a third method, after received user privilege information, database records associated with a workflow are determined and stored for use at workflow instance runtime. In a fourth method, artifacts used by a workflow are identified using a workflow template. When a command to execute a workflow instance is received, information is stored for generating instances of artifacts for use during execution of the workflow instance. In a fifth method, for a workflow template to be inactivated, the associated workflow template is suspended after currently executing workflow instances have completed and job executors have acknowledged a suspending state.
    Type: Application
    Filed: August 4, 2015
    Publication date: February 9, 2017
    Inventors: Stefan Henke, Tobias Breyer, Harald Schubert, Krassimir Kondarev, Peter Gernold, Ronald Trump, Torsten Wecke
  • Publication number: 20170039520
    Abstract: In a first method, a developer mode is determined when a workflow template patch is received, and execution of new workflow instances is either blocked or permitted, or continued execution of workflow instances is forbidden. In a second method, parallelization of workflow execution is provided in an in-memory database management system. In a third method, after received user privilege information, database records associated with a workflow are determined and stored for use at workflow instance runtime. In a fourth method, artifacts used by a workflow are identified using a workflow template. When a command to execute a workflow instance is received, information is stored for generating instances of artifacts for use during execution of the workflow instance. In a fifth method, for a workflow template to be inactivated, the associated workflow template is suspended after currently executing workflow instances have completed and job executors have acknowledged a suspending state.
    Type: Application
    Filed: August 4, 2015
    Publication date: February 9, 2017
    Inventors: Ronald Trump, Harald Schubert, Tobias Breyer, Peter Gernold, Stefan Henke, Krassimir Kondarev, Torsten Wecke
  • Publication number: 20170039385
    Abstract: In a first method, a developer mode is determined when a workflow template patch is received, and execution of new workflow instances is either blocked or permitted, or continued execution of workflow instances is forbidden. In a second method, parallelization of workflow execution is provided in an in-memory database management system. In a third method, after received user privilege information, database records associated with a workflow are determined and stored for use at workflow instance runtime. In a fourth method, artifacts used by a workflow are identified using a workflow template. When a command to execute a workflow instance is received, information is stored for generating instances of artifacts for use during execution of the workflow instance. In a fifth method, for a workflow template to be inactivated, the associated workflow template is suspended after currently executing workflow instances have completed and job executors have acknowledged a suspending state.
    Type: Application
    Filed: August 4, 2015
    Publication date: February 9, 2017
    Inventors: Stefan Henke, Tobias Breyer, Harald Schubert, Krassimir Kondarev, Peter Gernold, Ronald Trump, Torsten Wecke
  • Publication number: 20170039521
    Abstract: In a first method, a developer mode is determined when a workflow template patch is received, and execution of new workflow instances is either blocked or permitted, or continued execution of workflow instances is forbidden. In a second method, parallelization of workflow execution is provided in an in-memory database management system. In a third method, after received user privilege information, database records associated with a workflow are determined and stored for use at workflow instance runtime. In a fourth method, artifacts used by a workflow are identified using a workflow template. When a command to execute a workflow instance is received, information is stored for generating instances of artifacts for use during execution of the workflow instance. In a fifth method, for a workflow template to be inactivated, the associated workflow template is suspended after currently executing workflow instances have completed and job executors have acknowledged a suspending state.
    Type: Application
    Filed: August 4, 2015
    Publication date: February 9, 2017
    Inventors: Stefan Henke, Tobias Breyer, Harald Schubert, Krassimir Kondarev, Peter Gernold, Ronald Trump, Torsten Wecke