Abstract: Methods, systems, and computer programs are presented for managing access to resources using scenarios. One method includes an operation for storing first scenario data received for a first control scenario. The first scenario data comprises a control scenario identifier, a first resource, an authorization control, and a scenario trigger that defines an event that causes an activation of the first control scenario for providing access to the first resource. Further, the method includes operations for monitoring for an occurrence of the scenario trigger and detecting an occurrence of the event associated with the scenario trigger. Further, the method determines, in response to the occurrence of the event, a set of users authorized to access the first resource, including accessing the first scenario data to determine the set of users associated with the authorization control. Furthermore, access is provided to the set of users based on the determining.

Abstract: A system displays summaries of relationships of a selected data asset with other data assets at a limited number of levels upstream and downstream from the selected data asset in rows above and below the selected data asset. In each row, data assets are arranged in order of usage, with most used data asset displayed directly above or below the selected data asset. The user views grandparent-level data assets of a parent-level data asset that is directly above the selected data asset. The system includes a carousal feature to further navigate the lineage data upstream or downstream. By selecting a new data asset in the parent row, the user can view grandparent-level data assets of the newly selected data asset. The user can view multiple upstream or downstream levels arranged in respective rows displayed above or below the selected data asset. The system can analyze data from any application.

Abstract: Methods, systems, and computer programs are presented for managing access to resources using scenarios. One method includes an operation for storing first scenario data received for a first control scenario. The first scenario data comprises a control scenario identifier, a first resource, an authorization control, and a scenario trigger that defines an event that causes an activation of the first control scenario for providing access to the first resource. Further, the method includes operations for monitoring for an occurrence of the scenario trigger and detecting an occurrence of the event associated with the scenario trigger. Further, the method determines, in response to the occurrence of the event, a set of users authorized to access the first resource, including accessing the first scenario data to determine the set of users associated with the authorization control. Furthermore, access is provided to the set of users based on the determining.

Abstract: A system displays summaries of relationships of a selected data asset with other data assets at a limited number of levels upstream and downstream from the selected data asset in rows above and below the selected data asset. In each row, data assets are arranged in order of usage, with most used data asset displayed directly above or below the selected data asset. The user views grandparent-level data assets of a parent-level data asset that is directly above the selected data asset. The system includes a carousal feature to further navigate the lineage data upstream or downstream. By selecting a new data asset in the parent row, the user can view grandparent-level data assets of the newly selected data asset. The user can view multiple upstream or downstream levels arranged in respective rows displayed above or below the selected data asset. The system can analyze data from any application.

Abstract: A system displays summaries of relationships of a selected data asset with other data assets at a limited number of levels upstream and downstream from the selected data asset in rows above and below the selected data asset. In each row, data assets are arranged in order of usage, with most used data asset displayed directly above or below the selected data asset. The user views grandparent-level data assets of a parent-level data asset that is directly above the selected data asset. The system includes a carousal feature to further navigate the lineage data upstream or downstream. By selecting a new data asset in the parent row, the user can view grandparent-level data assets of the newly selected data asset. The user can view multiple upstream or downstream levels arranged in respective rows displayed above or below the selected data asset. The system can analyze data from any application.

Abstract: A system displays summaries of relationships of a selected data asset with other data assets at a limited number of levels upstream and downstream from the selected data asset in rows above and below the selected data asset. In each row, data assets are arranged in order of usage, with most used data asset displayed directly above or below the selected data asset. The user views grandparent-level data assets of a parent-level data asset that is directly above the selected data asset. The system includes a carousal feature to further navigate the lineage data upstream or downstream. By selecting a new data asset in the parent row, the user can view grandparent-level data assets of the newly selected data asset. The user can view multiple upstream or downstream levels arranged in respective rows displayed above or below the selected data asset. The system can analyze data from any application.

Abstract: A system displays summaries of relationships of a selected data asset with other data assets at a limited number of levels upstream and downstream from the selected data asset in rows above and below the selected data asset. In each row, data assets are arranged in order of usage, with most used data asset displayed directly above or below the selected data asset. The user views grandparent-level data assets of a parent-level data asset that is directly above the selected data asset. The system includes a carousal feature to further navigate the lineage data upstream or downstream. By selecting a new data asset in the parent row, the user can view grandparent-level data assets of the newly selected data asset. The user can view multiple upstream or downstream levels arranged in respective rows displayed above or below the selected data asset. The system can analyze data from any application.

Abstract: A system displays summaries of relationships of a selected data asset with other data assets at a limited number of levels upstream and downstream from the selected data asset in rows above and below the selected data asset. In each row, data assets are arranged in order of usage, with most used data asset displayed directly above or below the selected data asset. The user views grandparent-level data assets of a parent-level data asset that is directly above the selected data asset. The system includes a carousal feature to further navigate the lineage data upstream or downstream. By selecting a new data asset in the parent row, the user can view grandparent-level data assets of the newly selected data asset. The user can view multiple upstream or downstream levels arranged in respective rows displayed above or below the selected data asset. The system can analyze data from any application.

Abstract: A system displays summaries of relationships of a selected data asset with other data assets at a limited number of levels upstream and downstream from the selected data asset in rows above and below the selected data asset. In each row, data assets are arranged in order of usage, with most used data asset displayed directly above or below the selected data asset. The user views grandparent-level data assets of a parent-level data asset that is directly above the selected data asset. The system includes a carousal feature to further navigate the lineage data upstream or downstream. By selecting a new data asset in the parent row, the user can view grandparent-level data assets of the newly selected data asset. The user can view multiple upstream or downstream levels arranged in respective rows displayed above or below the selected data asset. The system can analyze data from any application.

Abstract: A user interface display is generated with user input mechanisms to receive business process flow definition inputs from a user. The definition inputs can include identifying stages and steps within stages, for a plurality of different entities. When the user accesses the business process, a user interface display shows the stages that are involved in completing the business process, and guides the user through the steps that the user is to complete in performing the process. The process can involve multiple entities, and a single entity can involve multiple processes.

Abstract: Concepts and technologies are described herein for managing recurring appointments without losing historical data associated with the recurring appointments. In accordance with the concepts and technologies disclosed herein, a recurring appointment definition can be modified without deleting the recurring appointment definition and/or losing exceptions, notes, and/or other data associated with the recurring appointment definition. Additionally, the concepts and technologies disclosed herein allow the modification of an existing recurring appointment definition without creating a new recurring appointment definition. Thus, synchronization between rules-based calendaring applications and expansion-based calendaring applications can be accomplished without creating multiple instances of related recurring appointments created due to modifications of the recurring appointment definition.

Abstract: Not-started CRM dialogs are described to facilitate dialog management in a cooperative manner between a CRM system and a client. A workflow defining a set of actions to complete for a business process can trigger a dialog in a “not-started” state and assign the dialog to a particular user. Pending completion of the dialog, the workflow can be paused or continue in the background to a designated stopping point. The dialog that is assigned can appear in a list of scheduled/pending tasks for the particular user and can include a link or other functionality to resume the dialog. Selection of the dialog from the task list can cause the dialog to resume to an “in-progress” state and the status of the dialog can be updated. Thereafter, the workflow can detect completion of the dialog and continue with further actions to complete the business process.

Abstract: Concepts and technologies are described herein for managing recurring appointments without losing historical data associated with the recurring appointments. In accordance with the concepts and technologies disclosed herein, a recurring appointment definition can be modified without deleting the recurring appointment definition and/or losing exceptions, notes, and/or other data associated with the recurring appointment definition. Additionally, the concepts and technologies disclosed herein allow the modification of an existing recurring appointment definition without creating a new recurring appointment definition. Thus, synchronization between rules-based calendaring applications and expansion-based calendaring applications can be accomplished without creating multiple instances of related recurring appointments created due to modifications of the recurring appointment definition.

Abstract: Techniques to manage and display related communications are described. A system may comprise a communication management tool (CMT) operative on a computer, the CMT comprising a threading component operative to associate a plurality of communications from a plurality of communication types with a conversation thread, and a display component operative to display communications in a conversation thread as a conversation view. Other embodiments are described and claimed.