Abstract: In one implementation, a workflow system can include a storage engine and a merger engine. The storage engine maintains a restricted workflow part on a first storage resource and maintains a customizable workflow part on a second storage resource. The merger engine retrieves the restricted workflow part based on the product version and merge the restricted workflow part with the customizable workflow part associated with the restricted workflow part.

Abstract: Examples relate to providing data backup for a multi-tenant application. One example enables determination that a first data set for a first tenant from the application should be backed up and determination, independently from determining the first data set should be backed up, that a second data set for a second tenant from the application should be backed up. Responsive to determining the first data set should be backed up, a first portion of the first data set stored at a first data resource of a first type may be accessed via a first adaptor for the first type of data resource, and a second portion of the first data set stored at a second data resource of a second type may be accessed via a second adaptor for the second type of data resource. The accessed portions of the first data set may be stored.

Abstract: In one implementation, a workflow system can include a storage engine and a merger engine. The storage engine maintains a restricted workflow part on a first storage resource and maintains a customizable workflow part on a second storage resource. The merger engine retrieves the restricted workflow part based on the product version and merge the restricted workflow part with the customizable workflow part associated with the restricted workflow part.

Abstract: Examples relate to providing data backup for a multi-tenant application. One example enables determination that a first data set for a first tenant from the application should be backed up and determination, independently from determining the first data set should be backed up, that a second data set for a second tenant from the application should be backed up. Responsive to determining the first data set should be backed up, a first portion of the first data set stored at a first data resource of a first type may be accessed via a first adaptor for the first type of data resource, and a second portion of the first data set stored at a second data resource of a second type may be accessed via a second adaptor for the second type of data resource. The accessed portions of the first data set may be stored.

Abstract: Updating service level targets may include aggregating a plurality of actions performed over each of a plurality of information technology service management (ITSM) records in a single service level target (SLT) database table since a prior update. Examples may include applying the aggregated plurality of actions to the SLT database table in a bulk operation. Examples may further include updating, at a predetermined elapsed time, each of the plurality of ITSM records in the SLT database table.

Abstract: Disclosed herein are a system, computer-readable medium, and method for querying configuration management databases. A topological query from an interpretation of an ambiguous query is executed in a configuration management database.