Sap Se

Thomas Spangemacher

Peer Hilgers

Leif Jensen-Pistorius

Martin Wezowski

Ole Lilienthal

Pit Humke

Dave Schikora

Michael Burwig

Alexander Gehres

Techniques are described for providing normalized object exposure in a collaborative platform. Implementations provide a collaborative platform to enable multiple users to collaborate to address an issue collectively. The platform enables a user to create a work routine in which objects may be added and manipulated by multiple users. The objects may be normalized through use of a normalized object contract. Tools may be added to the work routine, and linked to objects to apply functionality to the object data of the objects. The tools may also comply with the normalized object contract to be consumable within the platform. Through the contract, objects may exhibit a shared common state such that multiple users and/or processes access the same state for a particular object at any given time in a work routine.

Normalized object exposure for collaborative platforms

Techniques are described for service mapping and other backend operations for a collaborative platform. A platform may access data objects from any suitable number of source services. The data model of the platform may be dependent on the data models of its associated source services as well as source service annotations, where such annotations describe the mapping onto the various data model elements. The process of mapping requests and results between the platform and the external data sources at runtime may employ a schema mapping data structure to minimize potential performance impacts. Implementations may employ a hierarchical class structure that is configured to achieve efficient traversal by shifting computational load to initialization time when the source service data models and annotations are processed. The initialization of the structure may be triggered at initialization time of the platform or whenever an administrative action causes changes to the schema mapping.

Source service mapping for collaborative platforms

An identity verification application receives data encapsulating a request to verify an identity of a user that includes user-provided identification data. Thereafter, the identity verification application then hashes the user-provided data and traverses a decentralized ledger including a data structure comprising a plurality of linked segments to identify a match of the hash of the user-provided identification data. The identity verification application then provides verification data that either (i) confirms the identity of the user if the hash of the user-provided identification data has a match in the decentralized ledger, or (ii) rejects the identity of the user if the hash of the user-provided identification data does not have a match in the decentralized ledger. Related apparatus, systems, techniques and articles are also described.

Identity verification using computer-implemented decentralized ledger

Techniques are described for polymorph rendering of objects in a collaborative platform and/or other environments, through which the same object is presented differently in the user interface depending on which perspective is being used to render the object. In some implementations, the platform supports multiple renderers and each renderer is associated with a particular perspective. Polymorph rendering may also be described as adaptive rendering, given that the presentation of an object may be adapted to the particular accessors of a work routine, and such adaptation is achieved through use of different renderers to render the object according to different perspectives. A particular renderer can be written once and added to the platform, and that renderer may be applied to a variety of objects. Tools may also be rendered according to various perspectives, given that tools also support the normalized object contract and at least expose the mandatory perspectives.

Polymorph rendering for collaborative platforms

Techniques are described for providing and/or managing work routines (WRs) in a collaborative platform. Implementations provide a platform that enables collaboration between multiple entities (e.g., users) to address an issue collectively, for process management, issue resolution, and so forth. The platform enables the creation of a WR that includes any suitable number of data objects to facilitate management of a process, resolution of an issue, and/or other tasks. The WR may also include any suitable number of tools for controlling the manipulation and/or rendering of the data objects. The platform provides a polymorphism through which data objects may be rendered differently based on the tools that are used to render the tool objects. The platform also provides for the automatic creation of a WR, or a template for a WR, where such creation may be triggered by an event and/or based on a current context.

Growing community of inventors

Neulussheim, Germany

Thomas Spangemacher