Abstract: To extend a power cylinder bore in a hydraulic block of a power brake system, a cylinder cover, which is in the form of a cylinder tube and is closed at one end, is fastened by means of a circumferential caulking in a fastening groove of the hydraulic block which encloses the power cylinder bore. An interference fit of a fastening flange of the cylinder cover in the fastening groove reliably seals the cylinder cover against the hydraulic block in a pressure-proof manner.

Abstract: A cup-shaped cover of a pedal travel simulator, hydraulic accumulator, or a damper chamber, using a radially resilient connecting ring, which protrudes into a groove of the cover and into an opposing groove of a receptacle of a hydraulic block of a traction slip controller of a hydraulic vehicle braking system, to fasten inseparably at the hydraulic block.

Abstract: 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.

Abstract: 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.

Abstract: The present disclosure involves systems, software, and computer implemented methods for a personalized task ranking system capable of ranking tasks based on task context and user attributes. One example system includes operations to receive a request via interactions with an interface from a client device. User attributes associated with the request are identified. Context attributes corresponding to each task are identified from the repository of contextual content. Relevance conditions corresponding to each of the tasks are identified. The relevance conditions for each of the tasks are evaluated by comparing each of the context attributes to the user attributes. Based on the evaluating, a relevance score is generated for each of the tasks included in the task list corresponding to the user. The task list is transmitted with the generated relevance score for each of the tasks included in the task list to the client device.

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.

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.

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.

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.

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.

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.

Abstract: Systems and methods for adding services to an application platform via an extension platform coupled to the application platform. The application platform runs in a first operation system process and provides a number of resources. The extension platform is implemented in a second operation system process and communicates with the application platforms via standard inter-process communication protocols. The extension platform provides an environment to dynamically model and host application services. A resource abstraction layer provides the extension platform with access to the resources provided at the application platform. The resources are utilized by the extension platform to design and to execute the application services. The application services hosted in the extension platform are centrally managed and administered from the application platform via exposed interfaces.

Abstract: Systems and methods for adding services to an application platform via an extension platform coupled to the application platform. The application platform runs in a first operation system process and provides a number of resources. The extension platform is implemented in a second operation system process and communicates with the application platforms via standard inter-process communication protocols. The extension platform provides an environment to dynamically model and host application services. A resource abstraction layer provides the extension platform with access to the resources provided at the application platform. The resources are utilized by the extension platform to design and to execute the application services. The application services hosted in the extension platform are centrally managed and administered from the application platform via exposed interfaces.