Abstract: Techniques and solutions are described for copying data from a source client to a target client. It may be selected, such as by a user, whether a full copy or a partial copy of a set of source client data should be made. If a partial copy is selected, a set of file types is provided. The file types can be used to define files that should be included in, or excluded from, the copy. A data source of the source client is analyzed to determine data associated with a file type that is to be included in a copy, or is associated with a file type that is not indicated as to be excluded from the copy. The determined data is copied from the source client to the target client.

Abstract: Techniques and solutions are provided for metadata-driven data maintenance. One or more data object queries are obtained from one or more data object frameworks. One or more sets of data objects are received based on the one or more data object queries. One or more data object nets are built based on the one or more sets of data objects and the one or more data object frameworks and respectively associated with one or more processes. The one or more data object nets and their associated processes are analyzed. Data object maintenance is performed on the data objects of the one or more data object nets based on the analysis of the one or more data object nets and their associated processes.

Abstract: Systems, methods, and computer media for implementing a process map navigation tool are provided herein. A process map provides a graphical user interface that represents a process. Icons represent process components or steps and are related using flow connectors to indicate an ordered relationship between the process components. Users can click on an icon and either initiate the corresponding process component or launch a menu of tasks relevant to the step. The icons can also include indicators to provide workflow information.

Abstract: Systems, methods, and computer media for implementing a process map navigation tool are provided herein. A process map provides a graphical user interface that represents a process. Icons represent process components or steps and are related using flow connectors to indicate an ordered relationship between the process components. Users can click on an icon and either initiate the corresponding process component or launch a menu of tasks relevant to the step. The icons can also include indicators to provide workflow information.

Abstract: Techniques and solutions are described for copying data from a source client to a target client. It may be selected, such as by a user, whether a full copy or a partial copy of a set of source client data should be made. If a partial copy is selected, a set of file types is provided. The file types can be used to define files that should be included in, or excluded from, the copy. A data source of the source client is analyzed to determine data associated with a file type that is to be included in a copy, or is associated with a file type that is not indicated as to be excluded from the copy. The determined data is copied from the source client to the target client.

Abstract: Techniques and solutions are provided for metadata-driven data maintenance. One or more data object queries are obtained from one or more data object frameworks. One or more sets of data objects are received based on the one or more data object queries. One or more data object nets are built based on the one or more sets of data objects and the one or more data object frameworks and respectively associated with one or more processes. The one or more data object nets and their associated processes are analyzed. Data object maintenance is performed on the data objects of the one or more data object nets based on the analysis of the one or more data object nets and their associated processes.

Abstract: A notification job is executed as a background job in a recurrent notification framework. The registered scenario along with the recurrent notification information is retrieved from a central notification scenario registration table. The user information along with an application context is retrieved from a notification scenario BADI. The user information along with a notification preference is retrieved from a user registration table. The mapping information of the user identifier and the device identifier is retrieved from the device registration table. Based on the retrieved information, the notification channel is identified from the recurrent notification information. A recurrent notification is sent through the notification channel to a device.

Abstract: Methods and system are disclosed that build or generate an enterprise mobile apps. In an aspect, a project package including multiple plugins, common functionalities, some functionalities, graphical user interface elements, etc., may be generated at a mobile application development framework (MADF). Further, the MADF may receive a request for building or generating an enterprise mobile app. The MADF may reuse the components of the project package and integrate with the application functionalities to generate a corresponding enterprise mobile app.

Abstract: A notification job is executed as a background job in a recurrent notification framework. The registered scenario along with the recurrent notification information is retrieved from a central notification scenario registration table. The user information along with an application context is retrieved from a notification scenario BADI. The user information along with a notification preference is retrieved from a user registration table. The mapping information of the user identifier and the device identifier is retrieved from the device registration table. Based on the retrieved information, the notification channel is identified from the recurrent notification information. A recurrent notification is sent through the notification channel to a device.

Abstract: A computer-implemented method for testing a user interface includes: receiving, in a computer system, a first manual check result from a first manual check of a user interface of an application; generating a first markup-language record from the user interface and associating the first markup-language record with the first manual check result; after one or more changes are made in the application, generating a second markup-language record from the user interface; performing, in the computer system, at least one test on the user interface that involves a comparison of the first markup-language record with the second markup-language record; and performing, in the computer system, an action based on a result from the performed at least one test.

Abstract: A computer-implemented method for testing a user interface includes: receiving, in a computer system, a first manual check result from a first manual check of a user interface of an application; generating a first markup-language record from the user interface and associating the first markup-language record with the first manual check result; after one or more changes are made in the application, generating a second markup-language record from the user interface; performing, in the computer system, at least one test on the user interface that involves a comparison of the first markup-language record with the second markup-language record; and performing, in the computer system, an action based on a result from the performed at least one test.

Abstract: Business objects can be implemented in a single persistence scenario that supports both online transaction processing (OLTP) and online analytical processing (OLAP). A consumption-centric approach can use a same business object attribute data format model for consumption and persistence. Also, a singular model can be implemented in different layers of a system processing business objects. Extra software layers can be avoided. A business-objects-based system can take advantage of the technologies to provide greater flexibility, ease of extensibility, and performance improvements.

Abstract: Business objects can be implemented in a single persistence scenario that supports both online transaction processing (OLTP) and online analytical processing (OLAP). A consumption-centric approach can use a same business object attribute data format model for consumption and persistence. Also, a singular model can be implemented in different layers of a system processing business objects. Extra software layers can be avoided. A business-objects-based system can take advantage of the technologies to provide greater flexibility, ease of extensibility, and performance improvements.

Abstract: Systems, method and devices for adaptively suppressing data items based on one or more dynamic characteristics of the data items are disclosed. Adaptive data suppression of an operational data item may be accomplished by monitoring the operational data item for one or more dynamic characteristics required by a data aging rule associated with the operational data item, wherein at least one of the database and operational data item are stored in memory, detecting the one or more dynamic characteristics required by the data aging rule, recording the one or more detected dynamic characteristics and assessing whether the one or more detected dynamic characteristics satisfy the data aging rule. If a data aging rule is satisfied, the operational data item may be suppressed to persistent data storage. Related systems, methods, and articles of manufacture are also described.