Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Various embodiments of systems and methods for generating mnemonics are described herein. In an aspect, the method includes receiving a trigger for a mnemonic. Upon receiving the trigger, a menu including options for creating the mnemonic is displayed. A selection of an option from the menu is received for creating the mnemonic. Based upon the selection of the option, one or more pop-up windows for creating the mnemonic is rendered.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Various embodiments of systems and methods for generating mnemonics are described herein. In an aspect, the method includes receiving a trigger for a mnemonic. Upon receiving the trigger, a menu including options for creating the mnemonic is displayed. A selection of an option from the menu is received for creating the mnemonic. Based upon the selection of the option, one or more pop-up windows for creating the mnemonic is rendered.

Abstract: In one embodiment, a method is illustrated as including displaying an editing window, the editing window being a Graphical User Interface (GUI) used to design an application interface, associating a User Interface (UI) element with a layout element, and generating metadata, the metadata containing data illustrating the association between the UI element and the layout element. Further, another embodiment is illustrated as including receiving a service request relating to an application, the service request including a first set of rendering data illustrating a display area within which a first GUI relating to the application will be displayed, retrieving metadata, the metadata illustrating layout elements and associated UI elements relating to the first GUI, retrieving display logic associated with the metadata, retrieving business logic associated with the metadata, and generating the first GUI, wherein the first GUI is generated using the metadata, display logic and business logic.

Abstract: A method and system to monitor steps in a business process or complex tasks are described. The method may include displaying a graphical step monitor in a graphical user interface of an application, using a plurality of graphical elements indicating statuses of a plurality of steps in a sequence of steps in a process. The method may include receiving update information related to one or more steps of the plurality of steps. The method may also include updating the statuses of the steps for which the update information was received and as indicated by the plurality of graphical elements. Furthermore, the method may include displaying a description region including a further plurality of graphical elements and texts, the texts describing the steps, the statuses of which are indicated by the graphical elements.

Abstract: Various embodiments of systems and methods for accessing a plurality of services using a service abstraction layer are described herein. A plurality of services from one or more service provider is registered in a service abstraction layer. A request, from a service requestor, for accessing at least one service of the registered plurality of services is received at the service abstraction layer. Further, the received service request, at a service invoker of the service abstraction layer is forwarded to at least one corresponding service provider. Furthermore, successful execution of the requested service by the corresponding service providers is determined at the service invoker. Based on the determination, a response from the corresponding service provider is returned to the service requestor. Therefore, communication between the service requestor and the multiple service providers is handled by the service abstraction layer, which acts as a centralized layer.