Patents by Inventor Krassimir Kondarev
Krassimir Kondarev 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: 11238386Abstract: Techniques are described for workflow management, including automatically deriving characteristics of a user task node in a workflow based on an analysis of other workflow elements such as conditional sequence connectors. In some implementations, elements of a workflow presented in the modeler user interface of a workflow management platform are analyzed, and element(s) of the workflow are automatically and dynamically modified based on the analysis. For example, a workflow may include a first user task that is connected to subsequent node(s) in the workflow, such as other user task(s) downstream from the first user task. The first user task may be connected to each subsequent node by a conditional sequence connector. The condition information for each connector can be extracted from the workflow information and used to automatically modify the first user task to include decision branches for each element of condition information extracted from a respective connector.Type: GrantFiled: December 20, 2018Date of Patent: February 1, 2022Assignee: SAP SEInventors: Volker Lehmann, Andre Hofeditz, Tobias Breyer, Krassimir Kondarev
-
Patent number: 10904238Abstract: Techniques are described for managing access tokens in a computing environment. A proxy service can be configured to issue a first token to a workflow engine, the first token having a substantially unlimited lifetime to not time out during the workflow duration. The first token may be provided to the workflow in place of a shorter-lifetime token that may have otherwise been requested from a backend service. The first token may be used by the workflow engine to provide authorization for operations of the workflow. On completion of the workflow, the workflow engine may send an indication to the proxy service to request interactions with the backend service. The proxy service may request a second (e.g., limited-lifetime) token from the backend service, and use the second token to interact with the backend service on behalf of the workflow, thus acting as an intermediary between the workflow and the backend service.Type: GrantFiled: July 13, 2018Date of Patent: January 26, 2021Assignee: SAP SEInventor: Krassimir Kondarev
-
Publication number: 20200202273Abstract: Techniques are described for workflow management, including automatically deriving characteristics of a user task node in a workflow based on an analysis of other workflow elements such as conditional sequence connectors. In some implementations, elements of a workflow presented in the modeler user interface of a workflow management platform are analyzed, and element(s) of the workflow are automatically and dynamically modified based on the analysis. For example, a workflow may include a first user task that is connected to subsequent node(s) in the workflow, such as other user task(s) downstream from the first user task. The first user task may be connected to each subsequent node by a conditional sequence connector. The condition information for each connector can be extracted from the workflow information and used to automatically modify the first user task to include decision branches for each element of condition information extracted from a respective connector.Type: ApplicationFiled: December 20, 2018Publication date: June 25, 2020Inventors: Volker Lehmann, Andre Hofeditz, Tobias Breyer, Krassimir Kondarev
-
Publication number: 20200021573Abstract: Techniques are described for managing access tokens in a computing environment. A proxy service can be configured to issue a first token to a workflow engine, the first token having a substantially unlimited lifetime to not time out during the workflow duration. The first token may be provided to the workflow in place of a shorter-lifetime token that may have otherwise been requested from a backend service. The first token may be used by the workflow engine to provide authorization for operations of the workflow. On completion of the workflow, the workflow engine may send an indication to the proxy service to request interactions with the backend service. The proxy service may request a second (e.g., limited-lifetime) token from the backend service, and use the second token to interact with the backend service on behalf of the workflow, thus acting as an intermediary between the workflow and the backend service.Type: ApplicationFiled: July 13, 2018Publication date: January 16, 2020Inventor: Krassimir Kondarev
-
Patent number: 9721230Abstract: 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: GrantFiled: August 4, 2015Date of Patent: August 1, 2017Assignee: SAP SEInventors: Ronald Trump, Harald Schubert, Tobias Breyer, Peter Gernold, Stefan Henke, Krassimir Kondarev, Torsten Wecke
-
Publication number: 20170039520Abstract: 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: ApplicationFiled: August 4, 2015Publication date: February 9, 2017Inventors: Ronald Trump, Harald Schubert, Tobias Breyer, Peter Gernold, Stefan Henke, Krassimir Kondarev, Torsten Wecke
-
Publication number: 20170039385Abstract: 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: ApplicationFiled: August 4, 2015Publication date: February 9, 2017Inventors: Stefan Henke, Tobias Breyer, Harald Schubert, Krassimir Kondarev, Peter Gernold, Ronald Trump, Torsten Wecke
-
Publication number: 20170039046Abstract: 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: ApplicationFiled: August 4, 2015Publication date: February 9, 2017Inventors: Stefan Henke, Tobias Breyer, Harald Schubert, Krassimir Kondarev, Peter Gernold, Ronald Trump, Torsten Wecke
-
Publication number: 20170039492Abstract: 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: ApplicationFiled: August 4, 2015Publication date: February 9, 2017Inventors: Stefan Henke, Tobias Breyer, Harald Schubert, Krassimir Kondarev, Peter Gernold, Ronald Trump, Torsten Wecke
-
Publication number: 20170039521Abstract: 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: ApplicationFiled: August 4, 2015Publication date: February 9, 2017Inventors: Stefan Henke, Tobias Breyer, Harald Schubert, Krassimir Kondarev, Peter Gernold, Ronald Trump, Torsten Wecke