Abstract: Mechanisms are disclosed for visualizing and comparing an import and update history of content package objects in an analytic content system. Object to package mapping identifiers corresponding to the content package object are received. A package-identifier object state of a state of the content package object is received corresponding to an imported package associated with a particular package identifier. A modified object state to an original object state is compared prior to re-export of the content package object. The current object state to an original object state of the content package object is compared prior to importing the content package object from the imported package. A visualization of an import history of the content package object is displayed. In response to determining that an issue is present with a most recent import of the one or more content package objects, imports are rolled back to a stable set of objects.

Abstract: Content replication between tenants is provided using a user interface to an application of an enterprise tenant. The user interface includes a list of files shared by an embedded tenant. A user can select one or more selected files from the list of files. This initiates a replicate content job based on the one or more selected files. The replicate content job includes pulling each of the one or more selected files from the embedded tenant to the enterprise tenant and storing the file in the enterprise tenant database.

Abstract: Object-based transportation between tenants may provide advantages over persistence layer-based transportation on a cloud platform in situations where persistence layer storage space is limited. Object based transportation involves obtaining a selection from the target tenant application of a set of objects from the plurality of objects and determining objects identifiers for each of the selected set of objects. For each object in the selected set of objects, a request is sent to a source tenant. The requests includes the corresponding object identifier for that object. Corresponding object data is received from the source tenant. At least a portion of the corresponding object data is stored in a target tenant database. An existing object may be updated or a new object may be created.

Abstract: Efficient transport of content packages comprising multiple objects, is achieved utilizing lineage analysis. User selection of an object in a package, triggers a dependency request to a landscape containing the object. The landscape returns a dependencies result, which includes dependencies between the selected object and others present within the landscape. The dependencies result is used to create a dependents tree structure. Based upon the dependents tree and the originally selected object, a lineage view is created and afforded to the user. Example lineage views may comprise spider charts with the selected object at the center. The user may further explore object dependencies by interacting with the lineage view to create other lineage views. Providing intuitive visualization of object dependencies, aids in efficient package transport (e.g., by allowing a user to identify dependent object(s) missing from the package, and/or particular objects having many dependent objects that also require transport).

Abstract: Confidentiality and privacy of user comments stored on the cloud, are protected by encryption. A crypto server, and a browser including a migration engine, are located across a firewall from the cloud storage. In response to a migration instruction (e.g., received from an administrator), the migration engine utilizes batch processing to efficiently accomplish mass •onboarding, •offboarding, or •key rotation for comments stored on the cloud. To allow for graceful rollback, prior to initiating a migration operation the migration engine checks a migration status and a batch timestamp stored on the cloud. Where the migration status indicates a previous migration operation as being already started, and the batch timestamp indicates to be within a predetermined time, the migration engine precludes execution of a new migration operation. The predetermined time is indicative of batch processing that is merely time-consuming, rather than stalled completely (e.g., due to loss of network connectivity).

Abstract: Confidentiality and privacy of user comments are preserved by encryption of comments stored on the cloud. A migration engine and a crypto server including an encryption engine, are positioned behind a firewall from the cloud storage. In response to a comment migration instruction (e.g., •onboarding, •offboarding, or •key rotation), the migration engine performs batch processing across the firewall to retrieve a comment and comment metadata from the cloud storage. The migration engine forwards the comment/comment metadata behind the firewall to the crypto server. Based upon the comment metadata, the encryption engine uses a key for encrypting or decrypting the comment. Once encrypted or decrypted, the comment is returned to the migration engine for forwarding across the firewall and storage on the cloud. Encrypting or decrypting comments using a key determined from comment metadata, can impart flexibility to comment migration (e.g., allowing an administrator to selectively rotate compromised or expired keys).

Abstract: Content packages (including, e.g., visualizations, models) are replicated from one landscape to another that is restricted. The restricted landscape may be governed by regulations relating to privacy or other concerns. For package replication, a poll-pull mechanism is applied. Specifically, the first landscape creates a replicate package job targeting to the restricted landscape. The restricted landscape periodically polls and checks for any replicate package job for targeted for it. If any targeted replicate package jobs are discovered by polling, the restricted landscape will pull the job details to create a new replicate package job in its own (restricted) landscape. Under this approach, even though the replicate package job was initiated in the first landscape, it will be executed in the restricted landscape, thereby conforming to any governing regulations.

Abstract: In an example embodiment, a graphical user interface-based software tool is provided that uses integrated process information and information of a technical infrastructure to provide automatically-analyze integrations. There are several current approaches to capturing information relevant to the above questions available within a computer system, but each of them only captures a fragment of the information that will be utilized and are not linked. Additionally, most of them do not include extensibility information. The provided tool solves these issues.

Abstract: A software package comprising a plurality of software objects and package metadata is accessed and used to provide a graphical user interface including a first area in which details about the software objects are displayed and a second area where a user can select a location path, in an analytic cloud tenant on which the package is to be imported. A selection is made of the location path for at least one resource object. The system determines if the package metadata is of a type that includes information about a parent resource object but not descendant resource objects and not ancestor resource objects other than the parent resource object, for each resource object in the plurality of software objects, and if so, recursively identifies a parent object for each resource object in the plurality of software objects. The ancestor hierarchy from the recursively identified parent object(s) is reversed and inverted.

Abstract: A software package comprising a plurality of software objects and package metadata is accessed and used to provide a graphical user interface including a first area in which details about the software objects are displayed and a second area where a user can select a location path, in an analytic cloud tenant on which the package is to be imported. A selection is made of the location path for at least one resource object. The system determines if the package metadata is of a type that includes information about a parent resource object but not descendant resource objects and not ancestor resource objects other than the parent resource object, for each resource object in the plurality of software objects, and if so, recursively identifies a parent object for each resource object in the plurality of software objects. The ancestor hierarchy from the recursively identified parent object(s) is reversed and inverted.

Abstract: Impact analysis of an object is performed by selecting an object and determining impacted objects corresponding to the object. A type of the object is determined. A query is formulated and executed to retrieve relationship objects from a relationship table matching the type of the selected object. Nested properties associated with the relationship objects for the individual relationship objects are determined iteratively. A parent property associated with the nested properties is identified. A query is formulated and executed to fetch dependent values corresponding to the dependent values. The dependent values are added to a list. A query is formulated and executed to determine impacted objects corresponding to the dependent values. The impacted objects are displayed in a graphical chart.

Abstract: Impact analysis of an object is performed by selecting an object and determining impacted objects corresponding to the object. A type of the object is determined. A query is formulated and executed to retrieve relationship objects from a relationship table matching the type of the selected object. Nested properties associated with the relationship objects for the individual relationship objects are determined iteratively. A parent property associated with the nested properties is identified. A query is formulated and executed to fetch dependent values corresponding to the dependent values. The dependent values are added to a list. A query is formulated and executed to determine impacted objects corresponding to the dependent values. The impacted objects are displayed in a graphical chart.