Abstract: Embodiments of the present disclosure may include a system and method for passing documents between sandboxed applications in an efficient manner. When a document is passed from a source application to a target application, information regarding when the document was passed and to which application the document was passed to is stored in a document history table. Once the document is passed back to the source application, a document matching manager relies on information stored in the history table to determine if the document being passed back should overwrite a previous version of the document. If the document matching manager cannot determine that the previous version of the document should be overwritten, a user may be prompted to store the document at a desired location.

Abstract: A first component originally has a persistency decoupled from a persistency of a second component. The second component requires a table from the persistency of the first component. The first component is assigned a first database schema and the second component is assigned a second database schema. A table link is created in the second database schema of the second component, wherein the table link refers to the required table from the first database schema of the first component.

Abstract: A session transfer request is received from a cloud operating system, the session transfer request identifying a first active session and a second enhanced application server of a plurality of enhanced application servers. Then it is verified that cross user data containing information used by a plurality of sessions, including the first active session, is mapped to a first work process in a process pool of the cloud computing environment. Then a central dispatcher on the second enhanced application server is triggered to create a virtual context and a virtual machine corresponding to the first client device. When a subsequent user request is received from a first client device, the subsequent user request is sent to the central dispatcher of the second enhanced application server and the central dispatcher of the second enhanced application server is caused to roll-in the virtual context by attaching it to a free work process.

Abstract: An upgrade of a first version of a database application to a second version of a database application that both have a same data schema is initiated. The first database application has a first access schema such that at least one table in the data schema is linked to the first access schema. The second version of the database application has a second access schema such that at least one database table in the data schema is linked to the second access schema. The first access schema differs from the second access schema. During the upgrade, each access schema is provided access to a first sequence in the data schema for both of the first version of the database application and the second version of the database application. Subsequent to the upgrade, the second version of the database application is provided access to a second sequence in the data schema.

Abstract: An upgrade of a first version of a database application to a second version of a database application that both have a same data schema is initiated. The first database application has a first access schema such that at least one table in the data schema is linked to the first access schema. The second version of the database application has a second access schema such that at least one database table in the data schema is linked to the second access schema. The first access schema differs from the second access schema. Concurrent access is provided for each access schema to at least one sequence in the data schema to both the first version of the database application and the second version of the database application. Related apparatus, systems, techniques and articles are also described.

Abstract: In one aspect, the present disclosure relates to a method which comprises obtaining a set of software change process parameters characterizing the particular process, based on the obtained set of software change process parameters, selecting hot spot information corresponding to the obtained set of software change process parameters, the hot spot information being based on a statistical analysis of previous software change processes and wherein the hot spot information identifies one or more steps of the multiple steps of the process during which problems have occurred in the previous processes, providing the hot spot information to the host computer system for use in the software change process and obtaining status information relating to the software change process at multiple times during the execution of the software change process, a level of detail of the status information being increased for steps of the process identified in the hot spot information.

Abstract: A business software customer deploying both on-premises and cloud-based applications can be provided with an automatically-generated, customer-tailored release master plan for a hybrid networked business solution that can include specific information and instructions tailored to the business software customer's customer-specific system landscape.

Abstract: In some example implementations, there is provided a method. The method may include selecting an action element located on a user interface, wherein the user interface includes a plurality of action elements, whereby each action element corresponds to an action performable by a user and causing a change in a state of the user interface; identifying a help overlay graphics element for each selected action element in the plurality of action elements, the help overlay graphics element describing the action corresponding to the selected action element; and dynamically positioning a plurality of help overlay graphics elements identified for at least a portion of the plurality of selected action elements on the user interface, wherein the plurality of help overlay graphics elements are positioned proximate to associated action elements. Related systems, methods, and articles of manufacture are also provided.

Abstract: In one aspect, the present disclosure relates to a method which comprises obtaining a set of software change process parameters characterizing the particular process, based on the obtained set of software change process parameters, selecting hot spot information corresponding to the obtained set of software change process parameters, the hot spot information being based on a statistical analysis of previous software change processes and wherein the hot spot information identifies one or more steps of the multiple steps of the process during which problems have occurred in the previous processes, providing the hot spot information to the host computer system for use in the software change process and obtaining status information relating to the software change process at multiple times during the execution of the software change process, a level of detail of the status information being increased for steps of the process identified in the hot spot information.

Abstract: An incident associated with a software logistic tool occurs. At a host agent a notification for the incident is received. The host agent is associated with a corresponding host where the software logistic tool is running. The notification for the incident is pushed to a customer operation cockpit operating at a customer system landscape via a push channel for communication from the software logistic tool to the customer operation cockpit. The notification for the incident is received at the customer operation cockpit for a customer support user to analyze.

Abstract: A method includes receiving a target Uniform Resource Locator (URL), receiving a scan of a Quick Response (QR) code, where the QR code includes an alias URL, and mapping the alias URL encoded on the QR code to the target URL.

Abstract: A technique is described to selectively synchronize content on a client database with content from a server database. As the user traverses a hierarchical folder structure of the client database, he may run into content that has been deleted or moved in the server database. If the content is something that the user wishes to store locally, the content can be stored as an orphan. An orphan is content stored on the client that cannot be traversed by the hierarchical folder structure. When the user traverses to a node in the hierarchical folder structure that is missing an object existing on the server, a determination can be made as to whether the orphan object is the missing object. If so, the orphan object can be connected once against to the hierarchical folder structure. This may minimize the content that needs to be re-downloaded from the server.

Abstract: Methods and system are disclosed that scramble business data before transferring to a test environment. In one aspect, a business data scrambling logic may detect a transfer of the business data from a proprietary database (e.g., source database) to another database (e.g., target database) in test environment. The business data scrambling logic may determine metadata associated with the business data stored in source tables in the source database. Based on the metadata, the columns in the source tables including indicia may be identified. For the identified columns, alias values and associated hash codes may be generated. In the target database, target tables may be generated upon transferring the business data from the source database to the target database. The target tables may include values (e.g. actual values) and alias values associated with the business data. The alias values may represent scrambled business data.

Abstract: As part of an upgrade procedure transitioning from a source system to a target system, table entries used by both the source system and the target system can be selectively locked on a row-by-row basis using a lock table and one or more select triggers. Related apparatus, systems, techniques and articles are also described.

Abstract: A business software customer deploying both on-premises and cloud-based applications can be provided with an automatically-generated, customer-tailored release master plan for a hybrid networked business solution that can include specific information and instructions tailored to the business software customer's customer-specific system landscape.

Abstract: Various embodiments of systems, methods, and software provide attachment-based mass data input and output for a distributed application system. Software for interactive, attachment-based data management may comprise computer readable instructions operable when executed to receive a request from a logically remote client via a network interface, where the request indicates a data file and a business object associated with a business application. The business object is then updated with a message in a format associated with the business application based on the data file. The data file is then stored in a repository and a dependent object (included in, or referenced by, or otherwise associated with the business object) is then updated with a logical location of the data file in the repository.

Abstract: The present disclosure describes methods, systems, and computer program products for establishing business networks based on shared usage of a common platform. One process includes receiving a set of registry data associated with a collaboration system from a first network participant executing a first application based on a first application platform. A request from a second network participant executing a second application on a compatible platform to the first application platform to access the set of registry data from the first network participant is received. Access is provided to the second network participant of a subset of data shared by the first network participant for collaboration.

Abstract: The present disclosure involves systems, software, and computer implemented methods for integrating a source system with a target system. One computer-implemented method includes: starting a process, by operation of computer, the process missing actual data required for the process to complete; creating a proxy data object as a substitute for the actual data to allow the process to execute; executing the process using the proxy data object until the actual data is required for the process to continue execution; replacing the proxy data object with the actual data; and continuing to execute the process with the actual data.

Abstract: In one aspect, the present disclosure relates to a method which comprises obtaining a set of software change process parameters characterizing the particular process, based on the obtained set of software change process parameters, selecting hot spot information corresponding to the obtained set of software change process parameters, the hot spot information being based on a statistical analysis of previous software change processes and wherein the hot spot information identifies one or more steps of the multiple steps of the process during which problems have occurred in the previous processes, providing the hot spot information to the host computer system for use in the software change process and obtaining status information relating to the software change process at multiple times during the execution of the software change process, a level of detail of the status information being increased for steps of the process identified in the hot spot information.

Abstract: An incident associated with a software logistic tool occurs. At a host agent a notification for the incident is received. The host agent is associated with a corresponding host where the software logistic tool is running. The notification for the incident is pushed to a customer operation cockpit operating at a customer system landscape via a push channel for communication from the software logistic tool to the customer operation cockpit. The notification for the incident is received at the customer operation cockpit for a customer support user to analyze.