Abstract: In an embodiment, a cloud server determines a point in time in a current task, and identifies a corresponding point in time in each of a number of completed tasks retrieved from a first database. User activity data from a second database is used to calculate time spent on the current task up to the identified point in time, a ratio between time spent on each completed task after the corresponding point in time and time spent on the completed task before the corresponding point in time. The cloud server also calculates a similarity score between each completed task and the current task based on a number of parameters and using a predetermined algorithm. A weighted arithmetic mean of the time ratios can be calculated using the similarity scores as weights, and can be used in conjunction with the time spent on the current task up to the identified point in time, to calculate time required to complete the current task.

Abstract: Through a first processing thread, a first database is accessed via a first API to retrieve a list of event objects of the first database. Through a second processing thread, for each of the event objects, participant identifiers (IDs) are determined from the event object. For each of the participant IDs, a domain ID is extracted from the participant ID. A list of one or more entity objects are identified based on the domain ID, where the entity objects are stored in a second database such as a task database storing and managing many tasks. At least one attribute of at least one of the entity objects is modified based of the participant ID and the domain ID, which generates a modified entity object. Through a third processing thread, any event objects that have been modified are transmitted to the second database via a second API over the network.

Abstract: For a given user, a task database system associated with the user is queried to identify a list of tasks associated with the user. For each of the tasks, an email system associated with the user is queried to obtain one or more emails and calendar events associated with the task. An IM system associated with the user is queried to obtain IM messages of an IM channel of which the user is a member. The IM channel has been specifically created to exchange messages concerning the task amongst the members of the IM channel. The task is then determined whether it satisfies a predetermined state (e.g., inactive, lack of future meetings) in view of emails, calendar events, and IM messages associated with the task based on a set of rules. If the task is determined to satisfy the predetermined state, a notification message is transmitted to a preconfigured destination.

Abstract: According to one embodiment, a customer relationship management (CRM) system is queried to obtain a list of projects that are associated with a particular user. A subset of the projects is selected from the list. Each of the projects in the subset includes an attribute that has been set to a predetermined attribute value or attribute state by the user (e.g., flagged, starred, a checkbox). For each of the projects in the subset, a communication channel (e.g., an instant messaging or IM system, an email group, a group chat, a social network community) associated with the project is identified. It is determined whether the user is already a member of the communication channel. If the user is not a member of the communication channel, the user is automatically added to the communication channel without user intervention from the user.

Abstract: For a given user, a task database system associated with the user is queried to identify a list of tasks associated with the user. For each of the tasks, an email system associated with the user is queried to obtain one or more emails and calendar events associated with the task. An IM system associated with the user is queried to obtain IM messages of an IM channel of which the user is a member. The IM channel has been specifically created to exchange messages concerning the task amongst the members of the IM channel. The task is then determined whether it satisfies a predetermined state (e.g., inactive, lack of future meetings) in view of emails, calendar events, and IM messages associated with the task based on a set of rules. If the task is determined to satisfy the predetermined state, a notification message is transmitted to a preconfigured destination.

Abstract: According to one embodiment, a customer relationship management (CRM) system is queried to obtain a list of projects that are associated with a particular user. A subset of the projects is selected from the list. Each of the projects in the subset includes an attribute that has been set to a predetermined attribute value or attribute state by the user (e.g., flagged, starred, a checkbox). For each of the projects in the subset, a communication channel (e.g., an instant messaging or IM system, an email group, a group chat, a social network community) associated with the project is identified. It is determined whether the user is already a member of the communication channel. If the user is not a member of the communication channel, the user is automatically added to the communication channel without user intervention from the user.

Abstract: In an embodiment, a cloud server determines a point in time in a current task, and identifies a corresponding point in time in each of a number of completed tasks retrieved from a first database. User activity data from a second database is used to calculate time spent on the current task up to the identified point in time, a ratio between time spent on each completed task after the corresponding point in time and time spent on the completed task before the corresponding point in time. The cloud server also calculates a similarity score between each completed task and the current task based on a number of parameters and using a predetermined algorithm. A weighted arithmetic mean of the time ratios can be calculated using the similarity scores as weights, and can be used in conjunction with the time spent on the current task up to the identified point in time, to calculate time required to complete the current task.

Abstract: Through a first processing thread, a first database is accessed via a first API to retrieve a list of event objects of the first database. Through a second processing thread, for each of the event objects, participant identifiers (IDs) are determined from the event object. For each of the participant IDs, a domain ID is extracted from the participant ID. A list of one or more entity objects are identified based on the domain ID, where the entity objects are stored in a second database such as a task database storing and managing many tasks. At least one attribute of at least one of the entity objects is modified based of the participant ID and the domain ID, which generates a modified entity object. Through a third processing thread, any event objects that have been modified are transmitted to the second database via a second API over the network.

Abstract: In an embodiment, a cloud server determines a point in time in a current task, and identifies a corresponding point in time in each of a number of completed tasks retrieved from a first database. User activity data from a second database is used to calculate time spent on the current task up to the identified point in time, a ratio between time spent on each completed task after the corresponding point in time and time spent on the completed task before the corresponding point in time. The cloud server also calculates a similarity score between each completed task and the current task based on a number of parameters and using a predetermined algorithm. A weighted arithmetic mean of the time ratios can be calculated using the similarity scores as weights, and can be used in conjunction with the time spent on the current task up to the identified point in time, to calculate time required to complete the current task.

Abstract: Through a first processing thread, a first database is accessed via a first API to retrieve a list of event objects of the first database. Through a second processing thread, for each of the event objects, participant identifiers (IDs) are determined from the event object. For each of the participant IDs, a domain ID is extracted from the participant ID. A list of one or more entity objects are identified based on the domain ID, where the entity objects are stored in a second database such as a task database storing and managing many tasks. At least one attribute of at least one of the entity objects is modified based of the participant ID and the domain ID, which generates a modified entity object. Through a third processing thread, any event objects that have been modified are transmitted to the second database via a second API over the network.

Abstract: Through a first processing thread, a first database is accessed via a first API to retrieve a list of event objects of the first database. Through a second processing thread, for each of the event objects, participant identifiers (IDs) are determined from the event object. For each of the participant IDs, a domain ID is extracted from the participant ID. A list of one or more entity objects are identified based on the domain ID, where the entity objects are stored in a second database such as a task database storing and managing many tasks. At least one attribute of at least one of the entity objects is modified based of the participant ID and the domain ID, which generates a modified entity object. Through a third processing thread, any event objects that have been modified are transmitted to the second database via a second API over the network.

Abstract: In an embodiment, a cloud server determines a point in time in a current task, and identifies a corresponding point in time in each of a number of completed tasks retrieved from a first database. User activity data from a second database is used to calculate time spent on the current task up to the identified point in time, a ratio between time spent on each completed task after the corresponding point in time and time spent on the completed task before the corresponding point in time. The cloud server also calculates a similarity score between each completed task and the current task based on a number of parameters and using a predetermined algorithm. A weighted arithmetic mean of the time ratios can be calculated using the similarity scores as weights, and can be used in conjunction with the time spent on the current task up to the identified point in time, to calculate time required to complete the current task.

Abstract: For a given user, a task database system associated with the user is queried to identify a list of tasks associated with the user. For each of the tasks, an email system associated with the user is queried to obtain one or more emails and calendar events associated with the task. An IM system associated with the user is queried to obtain IM messages of an IM channel of which the user is a member. The IM channel has been specifically created to exchange messages concerning the task amongst the members of the IM channel. The task is then determined whether it satisfies a predetermined state (e.g., inactive, lack of future meetings) in view of emails, calendar events, and IM messages associated with the task based on a set of rules. If the task is determined to satisfy the predetermined state, a notification message is transmitted to a preconfigured destination.

Abstract: According to one embodiment, a customer relationship management (CRM) system is queried to obtain a list of projects that are associated with a particular user. A subset of the projects is selected from the list. Each of the projects in the subset includes an attribute that has been set to a predetermined attribute value or attribute state by the user (e.g., flagged, starred, a checkbox). For each of the projects in the subset, a communication channel (e.g., an instant messaging or IM system, an email group, a group chat, a social network community) associated with the project is identified. It is determined whether the user is already a member of the communication channel. If the user is not a member of the communication channel, the user is automatically added to the communication channel without user intervention from the user.