Abstract: Embodiments of the present invention provide methods and apparatuses enabling groupware to track time associated with a workflow task. A workflow object representing a workflow task is provided. The workflow object is associating with a time period, a project code, and an identifier of a groupware client user participating in the workflow task. In response to an event indicating completion of the workflow task, the time period, the project code, and the identifier is automatically transmitted to a backend application.

Abstract: A system includes a portal connected to user interface (UI) components, application logic linking the UI components to a repository layer and connectivity layer through an object access layer, and source systems linked to the repository layer and the connectivity layer.

Abstract: Methods and apparatuses provide contextual awareness to a groupware client with respect to an enterprise backend system. The groupware client generates a query or request for data within a context of the groupware client. A backend determines the context, which may include processing an indication of the context received with the query. Data is selectively chosen based on the context, and the selected data is provided to the groupware client to fulfill the request. In one embodiment, the backend determines a permission associated with the context.

Abstract: Methods and apparatuses to provide extension to a groupware client to enable the groupware client to access a workflow of a business process from the context of the groupware client. An enterprise server that manages the workflow can interface with the groupware client to provide action on the workflow from within the context of the groupware client. The enterprise server passes the action to the enterprise backend to implement the action on the workflow. Thus, action on the workflow from the groupware client affects the workflow on the enterprise level. Status information about the workflow may be persisted in the groupware client to enable continued interaction with the workflow from within the groupware client.

Abstract: Methods and apparatuses enable providing a structured business query interface to receive a structured business query. The interface can be provided as an extension to a business productivity application. The query is made without having to change context from the application to another program, but rather can be made within the context of the application. The query triggers access to a backend, which may result in accessing a data object that is inserted or embedded into the application, or a document of the application. In one embodiment, a business process extension is also available to the application, which enables a task pane within the application with other features and/or data. In one embodiment, related data can be accessed in response to selecting the inserted data object, which can provide additional information on the data object without leaving the context of the application.

Abstract: Methods and apparatuses enable providing a structured business query interface to receive a structured business query. The interface can be provided as an extension to a business productivity application. The query is made without having to change context from the application to another program, but rather can be made within the context of the application. The query triggers access to a backend, which may result in accessing a data object that is inserted or embedded into the application, or a document of the application. In one embodiment, a business process extension is also available to the application, which enables a task pane within the application with other features and/or data. In one embodiment, related data can be accessed in response to selecting the inserted data object, which can provide additional information on the data object without leaving the context of the application.

Abstract: Methods and apparatuses provide contextual awareness to a groupware client with respect to an enterprise backend system. The groupware client generates a query or request for data within a context of the groupware client. A backend determines the context, which may include processing an indication of the context received with the query. Data is selectively chosen based on the context, and the selected data is provided to the groupware client to fulfill the request. In one embodiment, the backend determines a permission associated with the context.

Abstract: Embodiments of the present invention provide methods and apparatuses enabling groupware to track time associated with a workflow task. A workflow object representing a workflow task is provided. The workflow object is associating with a time period, a project code, and an identifier of a groupware client user participating in the workflow task. In response to an event indicating completion of the workflow task, the time period, the project code, and the identifier is automatically transmitted to a backend application.

Abstract: Methods and apparatuses to provide extension to a groupware client to enable the groupware client to access a workflow of a business process from the context of the groupware client. An enterprise server that manages the workflow can interface with the groupware client to provide action on the workflow from within the context of the groupware client. The enterprise server passes the action to the enterprise backend to implement the action on the workflow. Thus, action on the workflow from the groupware client affects the workflow on the enterprise level. Status information about the workflow may be persisted in the groupware client to enable continued interaction with the workflow from within the groupware client.

Abstract: A system and method for implementing workflow in groupware. According to an embodiment of the invention, a groupware application receives one or more communications over a network from a business process server, the one or more communications associated with one or more work items to be performed by a user via the groupware application, the one or more work items associated with a phase of a workflow managed by the business process server, the groupware application receives one or more other communications over the network from the business process server, the one or more other communications including status information associated with one or more other phases of the workflow managed by the business process, and the groupware application provides the status information to the user within the context of the one or more work items to be performed by the user via the groupware application.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A method includes providing a single logical physically distributed information system across one or more information systems of at least two enterprises, wherein the enterprises are being combined, and providing a user interface to access the single logical physically distributed information system to execute one or more merger activities of the enterprises, the merger activities comprising a sales-related integration and a management of sales support activities, the sales support activities comprising addressing one or more customer issues for customer retention.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A method for planning a merger of at least two organizations includes human-resource tools, the human-resource tools including a compensation cost assessment tool, a compensation comparison and level mapping tool, and a self-servicing tool for employees and managers, the human-resource tools including one or more user interfaces.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A system for planning a merger of at least two organizations includes at least one of an organizational strategy tool, a strategy management tool, a strategy risk management tool, a strategy portfolio management tool, a strategy planning tool, and one or more software tools presenting a user with at least one of a personalized object, a preferred object, a recently accessed object, and a merger-related object.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A system for planning a restructuring of at least two organizations includes an intranet interface adapted for at least one employee of one of the organizations, an extranet interface adapted for an external restructuring member of at least one of the organizations, and an information repository related to at least one of the organizations, the information repository being accessible by the intranet interface.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A method for managing a corporate restructuring of at least two organizations includes presenting a user interface including information relating to consolidating customer accounts for at least one of the restructuring organizations, and presenting a template in the user interface, the template including a rollout template menu, a pull down window, a list of action items, and a status relating to each action item in the list.

Abstract: Systems and techniques relating to software for enterprise change, in particular to merger and acquisition processes and tools for one or more organizations. A method includes providing a single logical physically distributed information system across one or more information systems of at least two enterprises, wherein the enterprises are being combined, and providing a user interface to access the single logical physically distributed information system to execute one or more pre-merger activities, merger activities, and post-merger activities, wherein the merger activities comprise procurement realignment.

Abstract: A method for planning a restructuring of at least two organizations includes a first interface adapted to allow a user to plan a project with a resource management capability and a time management capability, a second interface adapted to provide collaborative capabilities to restructuring members to plan the project, and one or more tools adapted to allow a user to exchange restructuring information with a person associated with one of the organizations.

Abstract: A method includes providing a single logical physically distributed information system across one or more information systems of at least two enterprises, wherein the enterprises can be being combined, and providing a user interface to access the single logical information system, wherein the single logical physically distributed information system executes one or more merger activities, pre-merger activities, and post-merger activities, wherein the merger activities comprise organizational restructuring and personnel redeployment.

Abstract: Systems and techniques relating to software for enterprise change, in particular to restructuring processes and tools for one or more organizations. In one general implementation, the technique includes the generation of a single logical information system across one or more information systems of at least two enterprises, wherein the enterprises are combined, and the single logical information system is used to execute restructuring activities. The logical information system facilitates restructuring-related issue management.