Systems and methods to effectuate sets of automated actions outside and/or within a collaboration environment based on trigger events occurring outside and/or within the collaboration environment

Description

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods to effectuate sets of automated actions outside and/or within a collaboration environment based on trigger events occurring outside and/or within the collaboration environment.

BACKGROUND

Collaboration environments, sometimes referred to as integrated collaboration environments, may enable users to assign projects, tasks, or other assignments to assignees (e.g., other users) to complete. A collaboration environment may comprise an environment in which a virtual team of users does its work. A collaboration environment may enable users to work in a more organized and efficient manner. A collaboration environment may integrate features and/or functionality such as web-based conferencing and collaboration, desktop videoconferencing, and/or instant message into a single easy-to-use, intuitive interface.

SUMMARY

One aspect of the present disclosure relates to a system configured to effectuate sets of automated actions outside a collaboration environment based on trigger events occurring within the collaboration environment. Another aspect of the present disclosure relates to a system configured to effectuate sets of automated actions within a collaboration environment based on trigger events occurring outside the collaboration environment. Yet another aspect of the present disclosure relates to a system configured to effectuate sets of automated actions outside a collaboration environment based on trigger events occurring outside the collaboration environment.

Collaboration environments may require users to manually interact within the collaboration environment and/or applications/services outside of the collaboration environment in response to actions of other users and/or other events occurring within the collaboration environment. The responsive interactions outside the collaboration environment may include, for example, calendaring events into a personal calendar application, drafted and/or sending emails, sending personal messages over a messaging application and/or service separate from the collaboration environment, effectuating electronic payments, and/or other interactions. Over time, the users may tend to follow patterns with how they react to certain events and/or actions within the collaboration environment. This may create a negative experience for users who may tire of the potentially repetitive work. Requiring such repetitive manual interaction may increase friction within and/or outside of the collaboration environment. One or more implementations of the systems and methods presented herein may create less friction and/or more efficient use of the collaboration environment and one or more applications and/or services outside the collaboration environment by effectuating automatic sequences of actions outside the collaboration environment in response to trigger events occurring within the collaboration environment, and vice versa. The automated actions and/or trigger events may be user specified.

One or more implementations of a system configured to effectuate sets of automated actions outside a collaboration environment based on trigger events occurring within the collaboration environment may include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to manage environment state information maintaining a collaboration environment. Managing may include one or more of obtaining, sending, receiving, storing, updating, deleting, archiving, reporting, and/or other processes. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may specify values of environment parameters and/or other information. The environment parameters may include one or more of user parameters, work unit parameters, and/or other parameters. The values of the user parameters may describe one or more of the users, user actions of the users within the collaboration environment, user settings of the users, and/or other information about the users. The values of work unit parameters may describe units of work managed, created, and/or assigned within the collaboration environment, and/or other information about units of work.

The processor(s) may be configured to generate automation information and/or other information. The automation information may be generated based on user entry and/or selection of the automation information into a user interface. The automation information may specify sets of automated actions to carry out outside of the collaboration environment in response to occurrence of trigger events within the collaboration environment. The user entry and/or selection of the automation information may include entry and/or selection of one or more of individual automated actions in individual sets of automated actions, individual trigger events, and/or other information. By way of non-limiting illustration, the automation information may specify a first set of automated actions to carry out outside of the collaboration environment in response to a first trigger event occurring within the collaboration environment.

The processor(s) may be configured to detect occurrence of the trigger events within the collaboration environment. The occurrence of the trigger events may be based on changes in the values of the environment parameters and/or other events occurring within the collaboration environment. By way of non-limiting illustration, an occurrence of the first trigger event may be detected based on a first change in a first value of a first environment parameter to a second value. In some implementations, the first trigger event may be associated with the first change (e.g., a state change of the first environment parameter). In some implementations, the first trigger event may be associated with the second value (e.g., a data change of the first environment parameter).

The processor(s) may be configured to effectuate individual sets of automated actions outside the collaboration environment. The effectuation of the individual sets of automated actions may be responsive to the detection of the occurrence of individual trigger events. By way of non-limiting illustration, responsive to the detection of the first trigger event, the first set of automated actions may be effectuated outside the collaboration environment.

One or more implementations of the system effectuate sets of automated actions within a collaboration environment based on trigger events occurring outside the collaboration environment may include one or more hardware processors configured by machine-readable instructions. The processor(s) may be configured to manage environment state information maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users within the collaboration environment. The environment state information may specify values of environment parameters and/or other information. The environment parameters may include one or more of user parameters, work unit parameters, and/or other parameters. The values of the user parameters may describe one or more of the users, user actions of the users within the collaboration environment, user settings of the users, and/or other information about the users. The values of work unit parameters may describe units of work managed, created, and/or assigned within the collaboration environment, and/or other information about units of work.

The processor(s) may be configured to generate automation information and/or other information. The automation information may be generated based on user entry and/or selection of the automation information into a user interface. The automation information may specify sets of automated actions to carry out within the collaboration environment in response to occurrence of trigger events outside the collaboration environment. The user entry and/or selection of the automation information may include entry and/or selection of one or more of individual automated actions in individual sets of automated actions, individual trigger events, and/or other information. By way of non-limiting illustration, the automation information may specify a first set of automated actions to carry out within the collaboration environment in response to a first trigger event occurring outside the collaboration environment.

The processor(s) may be configured to obtain information indicating occurrence of the trigger events outside the collaboration environment. By way of non-limiting illustration, first information may be obtaining indicating an occurrence of the first trigger event outside the collaboration environment.

The processor(s) may be configured to effectuate individual sets of automated actions within the collaboration environment. The effectuation of the individual sets of automated actions may be responsive to obtaining the information indicating the occurrence of the trigger events outside the collaboration environment. By way of non-limiting illustration, responsive to obtaining the information indicating the occurrence of the first trigger event outside the collaboration environment, the processor(s) may be configured to effectuate the first set of automated actions within the collaboration environment.

As used herein, any association (or relation, or reflection, or indication, or correspondence) involving servers, processors, client computing platforms, and/or another entity or object that interacts with any part of the system and/or plays a part in the operation of the system, may be a one-to-one association, a one-to-many association, a many-to-one association, and/or a many-to-many association or N-to-M association (note that N and M may be different numbers greater than 1).

As used herein, the term “obtain” (and derivatives thereof) may include active and/or passive retrieval, determination, derivation, transfer, upload, download, submission, and/or exchange of information, and/or any combination thereof. As used herein, the term “effectuate” (and derivatives thereof) may include active and/or passive causation of any effect. As used herein, the term “determine” (and derivatives thereof) may include measure, calculate, compute, estimate, approximate, generate, and/or otherwise derive, and/or any combination thereof.

These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to effectuate sets of automated actions outside and/or within a collaboration environment based on trigger events occurring outside and/or within the collaboration environment, in accordance with one or more implementations.

FIG. 2 illustrates a method to effectuate sets of automated actions outside a collaboration environment based on trigger events occurring within the collaboration environment, in accordance with one or more implementations.

FIG. 3 illustrates a method to effectuate sets of automated actions within a collaboration environment based on trigger events occurring outside the collaboration environment, in accordance with one or more implementations.

FIG. 4 illustrates an exemplary user interface, in accordance with one or more implementations.

FIG. 5 illustrates an exemplary user interface, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to effectuate sets of automated actions within and/or outside a collaboration environment based on trigger events occurring within and/or outside the collaboration environment, in accordance with one or more implementations. In some implementations, system 100 may be configured to effectuate sets of automated actions outside a collaboration environment based on trigger events occurring within the collaboration environment. In some implementations, system 100 may be configured to effectuate sets of automated actions within a collaboration environment based on trigger events occurring outside the collaboration environment.

One or more implementations of the systems and methods presented herein may create less friction and/or more efficient use of the collaboration environment and/or other applications/services by users by effectuating automatic sequences of actions in response to trigger events. The actions and/or triggers may be user specified. In some implementations, automated actions may be carried out outside the collaboration environment in response to trigger events within the collaboration environment. In some implementations, automated actions may be carried out within the collaboration environment in response to trigger events occurring outside the collaboration environment. In some implementations, automated actions may be carried out outside the collaboration environment in response to trigger events occurring outside the collaboration environment. Individual external resources of one or more external resources 126 may be sources of triggers and/or targets of automated actions. In some implementations, system 100 may be configured to communicate with one or more external resources 126 such that individual external resources may communicate reports indicating the occurrence of trigger events by the individual external resources.

In some implementations, system 100 may include one or more of one or more servers 102, one or more client computing platforms 104, one or more external resources 126, and/or other components. Server(s) 102 may be configured to communicate with one or more client computing platforms 104 and/or one or more external resources 126 according to a client/server architecture and/or other architectures. Client computing platform(s) 104 may be configured to communicate with other client computing platforms via server(s) 102 and/or according to a peer-to-peer architecture and/or other architectures. Users may access system 100 via client computing platform(s) 104.

In some implementations, individual external resources of one or more external resources 126 may include individual applications providing one or more services outside of system 100. An application may include one or more of a calendar application, a payment application, an electronic communication application, a social media application, restaurant-reservation application, on-demand delivery application, a project management application, a customer relationship management application, a ticketing application, a partner relationship management application, a web form application, and/or other applications outside of the system providing one or more services. It is noted that this list of applications providing one or more services outside of system 100 is provided for illustrative purposes only and not to be considered limiting. Instead, it is to be understood that other applications providing one or more services outside of system 100 may be considered which are within the scope of the present disclosure. In some implementations, external resources and/or other considerations of applications providing one or more services outside of system 100 may be considered as such by virtue of otherwise being unaffiliated with system 100. In some implementations, external resources and/or other considerations of applications providing one or more services outside of system 100 may be considered as such by virtue of utilizing other servers, processors, and/or other components which may be separate and distinct from system 100. In some implementations, external resources and/or other considerations of applications providing one or more services outside of system 100 may be considered as such by virtue of being created and/or administered by entities that may be separate and distinct from creators and/or administers of system 100.

A calendar application may comprise a software application configured to provide users with an electronic version of a calendar. The calendar application may provide an appointment book, address book, contact list, and/or other features and/or functionality. In some implementations, a calendar application may provide functionality of setting calendar events, setting reminders, and/or other functionality.

A payment application may comprise an e-commerce payment application, electronic payment application, peer-to-peer payments application, an electronic wallet application, and/or other applications that facilitate the sending and/or receiving of electronic payments and/or other online transactions.

An electronic communication application may comprise an application for providing electronic communication services. Electronic communication services may include one or more of electronic mail, instant messaging, private messaging, and/or other communications. An electronic communication application may provide functionality of one or more of compiling, sending, receiving, archiving, deleting, and/or performing other actions with respect to electronic communications.

A social media application may comprise an application configured to facilitate the creation and/or sharing of information via virtual communities and/or networks. A social media application may provide functionality of compiling, posting, reviewing, deleting, searching, and/or performing other actions with respect to information created and/or shared via virtual communities and/or networks.

A restaurant-reservation application may include an application configured to set and/or request reservations and restaurants in response to web-based requests for reservations. The restaurant-reservation application may be specific to a given restaurant and/or an application that services many restaurants. A restaurant-reservation application may provide the functionality of searching restaurants, searching availability of reservations, communicating with restaurants, setting reservations, sending confirmations, and/or other features and/or functionality.

An on-demand delivery application may comprise an application configured to effectuate real-world deliveries of real-world goods and/or services in response to web-based requests for those goods and/or services. The on-demand delivery application may be associated with what may commonly be referred to as a “gig economy” application. By way of non-limiting illustration, an on-demand delivery application may be directed to food delivery, consumer items, and/or other goods and/or services.

A project management application may comprise an application configured to facilitate planning, organizing, and/or otherwise managing resources. A project management application may provide functionality of estimation and planning, scheduling, cost control and budget management, resource allocation, communication, decision-making, quality management, time management and documentation, administration systems, and/or other functionality.

Server(s) 102 may include one or more of non-transitory electronic storage 128, one or more processors 130 configured by machine-readable instructions 106, and/or other components. Machine-readable instructions 106 may include one or more instruction components. The instruction components may include computer program components. Executing the machine-readable instructions 106 may cause server(s) 102 to facilitate effectuating sets of automated actions outside a collaboration environment based on trigger events occurring within the collaboration environment and/or effectuating sets of automated actions within a collaboration environment based on trigger events occurring outside the collaboration environment. The instruction components may include one or more of an environment state component 108, an automation component 110, a conflict component 112, a user interface component 114, and/or other instruction components.

Environment state component 108 may be configured to manage environment state information and/or other information used in maintaining a collaboration environment. The environment state information may include values of one or more environment parameters. The environment parameters may include one or more of user parameters, work unit parameters, and/or other parameters. The values of the user parameters may specify user information and/or other information. The values of the work unit parameters may specify work information and/or other information.

The values of the user parameters may be organized in user records corresponding to users interacting with and/or viewing the collaboration environment. The values of the user parameters associated with the users interacting with and/or viewing the collaboration environment may include information describing the users, user actions of the users within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user interacting with and/or viewing the collaboration environment.

The values of the user parameters may, by way of non-limiting example, specify one or more of: a user name, a group parameter, a user account, a user role, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, one or more projects (which may include project parameters defined by one or more work unit records), one or more portfolios of projects, one or more items of work (which may include one or more unit of work parameters defined by one or more unit of work records), one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, other unit of work order, etc.), one or more authorized applications, one or more interaction parameters (e.g., indicating a user is working on/worked on a given unit of work, a given user viewed a given work unit of work, a given user selected a given unit of work, a timeframe a given user last interacted with and/or worked on a given unit of work, a time period that a given unit of work has been idle, and/or other interaction parameters), a presence parameter (e.g., indicating presence and/or interaction level at an environment level, unit of work level, project level, task level, application level, etc.), one or more notification settings, one or more progress parameters, status information for one or more work units the user is associated with (units of work assigned to the user, assigned to other users by the user, completed by the user, past-due date, and/or other information), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, one or more values of one or more workload parameters (e.g., one or more measures of current and future workload associated with units of work assigned to a user), and/or other information for the given user.

The values of the work unit parameters may be organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. A given work unit may have one or more assignees and/or team members working on the given work unit. Work units may include one or more to-do items, action items, objectives, and/or other units of work one or more users should accomplish and/or plan on accomplishing. Units of work may be created by a given user for the given user and/or created by the given user and assigned to one or more other users. A given unit of work may include one or more of a project, a task, a sub-task, a conversation (e.g., a message posting within a message board and/or other considerations), and/or other unit of work assigned to and/or associated with one or more users. In some implementations, users may be identified based on one or more of specific user identification (e.g., by name, username, and/or other information), descriptive user information (e.g., role, department, availability, and/or other information), and/or other considerations.

By way of non-limiting illustration, the one or more work unit parameters may include one or more of a work assignment parameter, a work management parameter, work creation parameter, and/or other parameters. The values of the work assignment parameter may describe units of work assigned to the individual users. The values of the work management parameter may describe units of work managed by the individual users. The values of the work creation parameter may describe units of work created by the individual users.

In some implementations, the units of work may be described based on one or more of a unit of work name, a unit of work description, one or more unit of work dates (e.g., a start date, a due date, a completion date, and/or dates), one or more members associated with a unit of work (e.g., an owner, one or more other project/task members, member access information, and/or other unit of work members and/or member information), a status parameter (e.g., an update, a hardcoded status update, a completed/uncomplete/mark complete, a measured status, a progress indication, quantity of sub-work units remaining for a given unit of work, completed work units in a given project, and/or other status parameter), one or more user comment parameters (e.g., permission for who may comments such as a creator, a recipient, one or more followers, and/or one or more other interested parties; content of the comments; one or more times; presence or absence of the functionality of up-votes; one or more hard-coded responses; and/or other parameters.), one or more interaction parameters (e.g., indicating a given unit of work is being worked on/was worked on, given work unit of work was viewed, a given unit of work was selected, how long the given unit of work has been idle, a last interaction parameter indicating when and what user last interacted with the given unit of work, users that interacted with the given unit of work, and/or other interaction parameters indicating sources of the interactions, context of the interactions, content of the interactions and/or time for the interactions), one or more file attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within a given unit of work (e.g., tasks within a project, subtasks within a task, etc.), state of a workspace for a given unit of work (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a unit of work), dependencies between one or more work units, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other values of work unit parameters.

The values of the work assignment parameter describing units of work assigned to the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign one or more unit of work to themselves and/or an other user. In some implementations, a user may be assigned a unit of work and the user may effectuate a reassignment of the unit of work from the user or one or more other users.

In some implementations, values of the work assignment parameter may indicate that a status parameter of a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, a status of complete for a unit of work may be associated with the passing of an end date associated with the unit of work. In some implementations, a status of “marked complete” may be associated with a user providing input via the collaboration environment at the point in time the user completes the unit of work (which may be before or after an end date).

In some implementations, user actions within the collaboration environment may include effectuating one or more changes in one or more values of one or more of the environment parameters. User actions may be facilitated through a user interface presenting the collaboration environment. By way of non-limiting illustration, a user action may include marking a unit of work “complete.” Marking a unit of work complete may change a value of a work unit parameter for the unit of work from “incomplete” to “marked complete.” User actions may include other changes to other values of other environment parameters described herein.

The automation component 110 may be configured to generate automation information and/or other information. The automation information may be generated based on user entry and/or selection of the automation information into a user interface (see, e.g., user interface component 114, FIG. 4, and/or FIG. 5). In some implementations, automation information may specify sets of automated actions to carry out outside the collaboration environment in response to occurrence of trigger events within the collaboration environment. In some implementations, automation information may specify sets of automated actions to carry out within the collaboration environment in response to occurrence of trigger events outside the collaboration environment. In some implementations, automation information may specify sets of automated actions to carry out outside the collaboration environment in response to occurrence of trigger events outside the collaboration environment.

The user entry and/or selection of the automation information may include entry and/or selection of one or more of individual automated actions in individual sets of automated actions, individual trigger events, and/or other information. By way of non-limiting illustration, the automation information may specify a first set of automated actions to carry out in response to a first trigger event. The first set of automated actions and/or the first trigger event may be generated based on input by a first user into a user interface. The first set of automated actions may include one or more automated actions to carry out outside the collaboration environment. The first trigger event may include an event occurring within the collaboration environment. By way of non-limiting illustration, the automation information may specify a second set of automated actions to carry out in response to a second trigger event. The second set of automated actions and/or the second trigger event may be generated based on input by a first user into a user interface. The second set of automated actions may include one or more automated actions to carry out within the collaboration environment. The second trigger event may include an event occurring outside the collaboration environment.

The automation component 110 may be configured to detect occurrence of the trigger events within the collaboration environment based on changes in the values of the environment parameters and/or other information. Detection may be based on monitoring environment state information, user actions, and/or other components of system 100. By way of non-limiting illustration, an occurrence of the first trigger event may be detected based on a first change in a first value of a first environment parameter to a second value.

The automation component 110 may be configured to obtain information indicating occurrence of trigger events outside the collaboration environment. In some implementations, information indicating occurrence of trigger events outside the collaboration environment may be obtained by virtue of individual external resources communicating the information to system 100. The communicated information may include status reports and/or other information. In some implementations, the communication of the information may be based on automation component 110 sending requests for the information. In some implementations, the communication of the information may be based on individual external resources performing scheduled and/or predetermined reporting protocols (e.g., push notifications and/or other protocols). By way of non-limiting illustration, automation component 110 may be configured to obtain first information indicating an occurrence the second trigger event outside the collaboration environment.

In some implementations, an individual automated action within the collaboration environment may include effectuating one or more of creation of, change in, and/or specification of, one or more values of one or more of the environment parameters. In some implementations, the creation of, change in, and/or specification of values of environment parameters may be accomplished by accessing a corresponding record (e.g., user record, work unit record, and/or other records). In some implementations, creation of, change in, and/or specification of an individual value may be reflected in views of the collaboration environment accessed by users.

In some implementations, individual automated actions within the collaboration environment may be classified by individual action types. An action type may dictate the extent in which an automation action effects the collaboration environment. An action type may include one or more of a record creation type, value specification type, and/or other types. A record creation type automated action may include creating one or more of a user record, work unit record, and/or other records. The creation of a record may include generating an instance of the record in the collaboration environment. The creation of the record by a record creation type automated action may not specifically define values of the environment parameters within the record and/or may set values to one or more of default values, null values, and/or other values. A value specification type automated action may include changing, and/or specifying, one or more values of one or more of the environment parameters contained within a record.

In some implementations, value specification type automated action may further be classified by one or more action subtypes based on the individual values of the individual environment parameters associated with the individual automated actions. An action subtype may include one or more of a time-based subtype, privacy and/or permissions subtype, accessibility subtype, interaction subtype, and/or other subtype.

An automated action of the time-based subtype may effectuate change in, and/or specification of, one or more values of one or more of the environment parameters related to time. For a work unit record, this may include one or more unit of work dates (e.g., a start date, a due date, a completion date, and/or dates). For a user record, this may include one or more of a start of employment date, an end of employment date, a length of employment period, a length of vacation period, and/or other information.

An automated action of the privacy and/or permissions subtype may correspond to values of environment parameters related to privacy and/or permissions. By way of non-limiting illustration, an automated action performed on a user record being of the privacy and/or permissions subtype may include change of, and/or specification of, one or more of one or more teams a user belongs to, one or more user display settings (e.g., colors, size, project order, task order, other unit of work order, etc.), one or more authorized applications, application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, and/or other information for the user. By way of non-limiting illustration, an automated action performed on a work unit record being of the privacy and/or permissions subtype may include change of, and/or specification of, one or more of one or more user comment parameters (e.g., permission for who may comments such as a creator, a recipient, one or more followers, and/or one or more other interested parties; content of the comments; one or more times; presence or absence of the functionality of up-votes; one or more hard-coded responses; and/or other parameters.), notification settings, privacy settings, dependencies between one or more work units, and/or other values.

An automated action of the accessibility subtype may correspond to values of environment parameters which may be required in a record (user and/or work unit) in order for the record to take effect within the collaboration environment. Values of environment parameters which may be required in a record in order for the record to take effect may refer to values that, if left undefined, would not provide any meaningful use within the collaboration environment. In other words, the values of environment parameters which may be required in a record in order for the record to take effect may refer to a minimum quantity of environment parameters which may need to be specified in order to allow users to interact with and/or access the record. By way of non-limiting illustration, an automated action performed on a user record being of the accessibility subtype may include change of, and/or specification of, one or more of a user name, a user account, a user role, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, and/or other values. By way of non-limiting illustration, an automated action performed on a work unit record being of the accessibility subtype may include change of, and/or specification of, one or more of a unit of work description, one or more members associated with a unit of work (e.g., an owner, one or more other project/task members, member access information, one or more assignees, and/or other information), an associated URL, and/or other values.

An automated action of the interaction subtype may correspond to values of environment parameters which may be specified in a record (user and/or work unit) in order to provide further functionality and/or accessibility within the collaboration environment. Values of environment parameters which may be specified in a record (user and/or work unit) in order to provide further functionality and/or accessibility may refer to values other than those associated with the time-based subtype, privacy and/or permissions subtype, accessibility subtype, and/or other subtypes.

It is noted that the classification of automated actions into action types and/or subtypes, and/or the descriptions of the different actions types and/or subtypes are provided for illustrative purposes only. Instead, it is to be understood that action types and/or subtype may be described in other ways, and/or automated actions may be classified in other ways.

In some implementations, an individual automated action may be carried out simultaneously (or near simultaneously) with an individual detection of an individual occurrence of an individual trigger event and/or within a specified time frame following an individual detection of an individual occurrence of an individual trigger event. In some implementations, a specified time frame may include a “waiting” period of time before an action is carried out. In some implementations, the waiting period of time may be satisfied by one or more of the passage of the period of time, some other trigger event, and/or other events and/or actions within the collaboration environment.

In some implementations, individual trigger events may be specified as individual occurrences of change of the values of the environment parameters. Occurrences of change may convey a state change of an environment parameter. The state change may not consider what the change is, but instead that a change occurred. For example, a trigger event may include an occurrence of a reassignment of a unit of work from one user to an other user. By way of non-limiting illustration, the first trigger event may be associated with the first change.

In some implementations, individual trigger events may be specified as individual values of the environment parameters. Changes to specific values may be referred to as data state changes. The data state change may refer to a change of a parameter to a specific value from an other value (and/or from a state of being unspecified). For example, a trigger event may include an occurrence of a reassignment of a unit of work from one user to another specific user. For example, a trigger event may include a comment having one or more specific words and/or phrases. By way of non-limiting illustration, the first trigger event may be associated with the second value and/or other values.

In some implementations, a set of automated actions may be associated with one or more of a sequence in which automated actions in the set are to be carried out, concurrent carrying out of two or more of the automated actions in the set, and/or other features and/or functionality. The automated actions within a set of automated actions may have a specified ordered sequence in which the automated actions are to be carried out. In some implementations, one or more actions may be followed by, and/or preceded by, a specified waiting period. A set of automation actions may specify that two or more actions may be carried out concurrently. In some implementations, a user may specify a combination and/or sequence of multiple triggers and/or multiple automated actions as a multi-step “workflow” that may include branching logic. By way of non-limiting illustration, a chain of trigger/action pairs of a given sequence may result in facilitating a workflow.

The automation component 110 may be configured to, responsive to the detection of the occurrence of individual trigger events, effectuate individual sets of automated actions outside the collaboration environment. By way of non-limiting illustration, responsive to the detection of the first trigger event, automation component 110 may be configured to effectuate the first set of automated actions outside the collaboration environment.

In some implementations, effectuating individual sets of automated actions outside the collaboration environment may include communicating instructions to effectuate the action to an external resource outside the collaboration environment. In some implementations, effectuating individual sets of automated actions outside the collaboration environment may include performing an application programming interface (API) call and/or other interaction with the external resource to cause the external resource to execute one or more routines in accordance with the instructions. An API interaction may include one or more of Remote Procedure Call, Representational State Transfer, GraphQL, and/or other interaction.

The automation component 110 may be configured to, responsive to obtaining the information indicating the occurrence of the trigger events outside the collaboration environment, effectuate individual sets of automated actions within the collaboration environment. By way of non-limiting illustration, responsive to obtaining the first information indicating occurrence of the second trigger event, automation component 110 may be configured to effectuate the second set of automated actions within the collaboration environment.

In some implementations, individual sets of automated actions and associated individual trigger events may be stored in individual automation records. An automation record may define one or more of individual actions, individual trigger events, and/or other information. Individual actions may be defined by a target component, an action component, and/or other information. The target component of an automation record may include the environment parameter (or parameters) to which an action is to be carried out on and/or an external resource to which the action is to be carried out with. The action component of an automation record may define what change is to be made on the environment parameter(s) and/or instructions to effectuate the action by the external resource defined by the target component.

Individual trigger events may be defined by a source component, an event component, and/or other information. The source component of an automation record may include the environment parameter(s) and/or external resource(s) from which occurrences of a trigger event may be derived. The event component may include the value (or change in the value) for the environment parameter(s) and/or the information indicating occurrence of an event within the external resource defined by the source component from which occurrences of a trigger event may be derived.

In some implementations, individual automation records may store counts of occurrences of individual trigger events and/or occurrences of carrying out individual automation actions in the sets of automation actions.

It is noted that while some descriptions presented herein may be directed to an individual trigger event causing an individual set of automated actions to be carried out, this is for illustrative purposes only and not to be considered limiting. For example, in some implementations, multiple trigger events may be combined together through some logic criteria, that when satisfied, may cause an individual set of automated actions to be carried out within and/or outside the collaboration environment. Logic may include, for example, Boolean logic. By way of non-limiting illustration, logic operators such as “AND”, “OR”, “NOT”, and/or other operations may be utilized to generate more complex trigger combinations for sets of automated actions. In some implementations, the use of logic operators may allow for fewer discrete trigger events to be defined yet still have more complex behavior available to users. For example, there may not need to specify a trigger event of “when task is unassigned”, since through the use of a logic operator “NOT”, a trigger event may be defined by “when task assigned” combined with the operator “NOT”. Further, the Boolean logic may facilitate multistage automation. By way of non-limiting illustration, instead of input “than-if-then” or “if-and-if-then”, logic may include “if-then-then” and/or other operators. In some implementations, a user may specify a set, or pool, of trigger events to trigger one or more automated actions. In some implementations, user may specify that one or more of the trigger events in the set may individually and/or in combination trigger the one or more automated actions. This way, a user may specify multiple options of trigger events which may trigger one or more automated actions. Further, an individual trigger event may trigger multiple automated actions.

The automation component 110 may be configured to determine individual sets of repeated user actions by the individual users. The determination may be based on monitoring environment state information (e.g., change in values of environment parameters and/or other monitoring), user actions, information indicating occurrence of the trigger events outside the collaboration environment, and/or other information generated by and/or accessible to system 100. In some implementations, determining individual sets of repeated user actions by the individual users may include determining one or more actions and/or events occurring within and/or outside the collaboration environment which precede the individual sets of repeated user actions. In some implementations, a set of user actions may be deemed “repeated” after the set of user actions occur more than once.

The automation component 110 may be configured to generate recommendations for automation information based on individual sets of repeated user actions and/or other information. The recommendations may include individual recommended sets of automated actions and/or individual recommended trigger events which correspond to the individual sets of repeated user actions. In some implementations, recommended trigger events may include the actions and/or events occurring within and/or outside the collaboration environment which precede the individual sets of repeated user actions. In some implementations, individual recommended sets of automated actions may include the individual sets of repeated user actions. In some implementations, a recommendation may include a notification (e.g., pop-up message, email, and/or other notification) describing one or more of the individual sets of repeated user actions, the individual recommended sets of automated actions, the individual recommended trigger events, and/or other information. By way of non-limiting illustration, a set of repeated user actions for a given user may include generating a specific task, assigning the specific task to a specific person (or persons), adding a comment to the task, causing an external application of an external resource to perform some action, and/or other actions. The automation component 110 may determine that the set of repeated user actions for the given user is preceded by an other specific task being marked completed. The automation component 100 may be configured to generate a recommendation for automation information including a set of recommended automated actions including generating the specific task, assigning the specific task to the specific person (or persons), adding a comment to the task, generating and/or sending instructions to effectuate the action by the external application, and/or other actions. The automation component 110 may be configured such that the recommendation includes a recommended trigger event including the other specific task being “marked complete.”

In some implementations, automation component 110 may be configured to obtain and/or generate one or more automation templates. An automation template may specify a predetermined set of automated actions to carry out in and/or outside the collaboration environment in response to occurrence of a predetermined trigger event. The one or more automation templates may be stored by electronic storage 128 and/or other storage device. In some implementations, an automation template may represent sets of actions users may commonly carry out in response to an action and/or occurrence within and/or outside the collaboration environment. In some implementations, automation templates may be created by system administrators, other users, based on repeated user actions, and/or created in other ways. In some implementations, the automation templates may be stored in a library for access and/or implementation by individual users.

The conflict component 112 may be configured to analyze automation information to identify conflicts within the sets of automated actions and/or the trigger events. In some implementations, analyzing automation information may include simulating execution of the automation information in a testing environment to determine a potential outcome of the automation information. In some implementations, conflicts may include one or more of repeating and/or ongoing automated actions (e.g., where a set of automated actions may not have a finite end), an instance when an individual automated action comprises an individual trigger event (e.g., resulting in a looping of trigger-action-trigger-action, etc.), and/or other conflicts.

In some implementations, analyzing automation information may further include only allowing the execution of automated actions after a triggering event if the state specified in the actions are not already true. If they are already true, conflict component 112 may recognize this as a conflict and not execute the action(s) again.

In some implementations, a user may use a user interface to construct and manipulate a representation of an automation record, rather than editing information within the automation record itself. This may allow conflict component 112 to prevent conflicts in the execution of the automation records being edited in the “live” versions of the automated records. Further, conflict component 112 may validate the representations and prevent configuration errors before saving them to the system 100.

In some implementations, conflict component 112 may be configured to analyze automation information as a user is specifying the automation information within a user interface (see, e.g., user interface component 114) and/or after the automation information has been specified and saved. The user interface may be configured to present errors at a number of possible failure points as the user is interacting with the user interface in real-time and/or near-real time. The possible failure points may include one or more of configuration failures, run time failures, cadence failures, container failures, editing failures, invalid permissions to an external resource, and/or other information.

The configuration failures may be related to if a user constructs a representation of an automation record that contains some sort of conflict and/or is invalid, conflict component 112 may validate that representation before saving or executing it, and notify the user contextually about the fixes that should be made in order to save and enable the automation record.

The run time failures may be related to determining that an automation record may be misconfigured when it attempts to execute the record. The conflict component 112 may send notifications (e.g., email, on-screen notifications, and/or other notification) containing information about the configuration error, and/or how to resolve it. A similar notification may also be sent by conflict component 112 if the execution fails due to some sort of system issue. In this case, the user may be notified that they do not need to take any action to resolve this failure.

The cadence failures may be related to when a trigger event may be misconfigured, the associated set of automated actions would never be executed because the trigger event may never be activated. To prevent this silent failure, the conflict component 112 may be configured to run checks on a regular cadence of the automation records within the system 100. This cadence check may iterate through the triggers and/or actions on individual automation records, and notify an appropriate user.

The container failures may be related to when a user visits a container object (e.g., project, portfolio, etc.). The conflict component 112 may present the user with pertinent status information about automation records associated with the container object, allowing them to fix any problems that may have arisen even without having seen any of the relevant notifications in other areas.

The editing failures may be related to editing an automation record with invalid components. A user may be directed through the user interface towards the specific components and/or associated inputs that may be causing an automation record to be invalid. This guided process may allow users to easily address and fix those issues so an automation record may resume operation.

The conflict component 112 may be configured to generate conflict reports based on the analysis. In some implementations, a conflict report may include a description of one or more conflicts and/or an indication of nonexistence of conflicts. In some implementations, a conflict report may provide an indication of elements of an automated action and/or trigger event which may comprise a source of conflict.

In some implementations, conflict component 112 may be configured to rate limit automated actions of one or more automation records. Rate limiting may include canceling and/or throttling execution of one or more automated actions based on one or more conditions. By way of non-limiting illustration, if one or more automated actions are triggered to execute more than X times in Y seconds, conflict component 112 may be configured to cancel one or more executions in that Y-second window. The values of X and/or Y may be user specified and/or specified by the system 100. In some implementations, if one or more automated actions at a project level are executed more than A times in B seconds, conflict component 112 may be configured to cancel one or more executions in that B-second window. The values of A and/or B may be user specified and/or specified by the system 100.

User interface component 114 may be configured to effectuate presentation of individual user interfaces on individual client computing platforms of one or more client computing platforms 104. For example, the individual client computing platforms may access a user interface over network 116. A given user interface may be configured to facilitate user specification of sets of automated actions and/or trigger events. In some implementations, user interface component 114 may be configured to prevent presentation of individual user interfaces configured to facilitate user specification (and/or modification) of sets of automated actions and/or trigger events by users who may not be authorized within system 100.

The user interface component 114 may be configured to effectuate presentation of a user interface through which users may specify and/or select one or more of one or more automated actions, one or more trigger events, one or more automation templates, and/or other information. In some implementations, a user interface may display one or more conflict reports and/or other prompts and/or notifications to a user. In some implementations, users may provide entry and/or selection of a period of time or times when an automation record may be active (e.g., configured to be executed) and/or paused (e.g., configured to not be executed). By way of non-limiting illustration, a user interface element may comprise an “active/paused” toggle button.

The user interface may include one or more user interface portions. By way of non-limiting illustration, a user interface may include one or more input portions and/or other components. Individual portions may include one or more user interface elements configured to facilitate user interaction with the user interface. By way of non-limiting illustration, user interface elements may include one or more of text input fields, drop down menus, check boxes, display windows, virtual buttons, and/or other elements configured to facilitate user interaction.

An input portion of a user interface may be configured to obtain user input comprising one or more of user entry and/or selection of environment parameters to carry out actions on, entry and/or selection of values to apply to the entered and/or selected environment parameters, entry and/or selection of environment parameters associated with trigger events, entry and/or selection of values of environment parameters associated with trigger events, user entry and/or selection of one or more automation templates, entry and/or selection of external resource(s) to carry out actions on, entry and/or selection of action(s) within selected external resource(s) to carry out, entry and/or selection of external resource(s) associated with trigger events, entry and/or selection of occurrence(s) within external resource(s) which may comprise trigger events, and/or other information. In some implementations, in response to entry and/or selection of an external resource (for either an action and/or trigger), the user interface may present a prompt confirming the use of the external resource. This may be a safeguard against inadvertently carrying out actions on items outside the collaboration environment. A user may confirm and/or deny the prompt, via, for example, selecting a virtual button and/or an authentication procedure.

FIG. 4 illustrates an exemplary user interface 400, in accordance with one or more implementations. The user interface 400 may be configured to obtain user entry and/or selection of automation information and/or other information. The user entry and/or selection may be in the form of specification of automated actions, trigger events, and/or other information.

In some implementations, automated actions may be specified based on entry and/or selection of one or more of individual external resources, individual actions for the individual external resources to carry out, and/or other information. In some implementations, trigger events may be specified based on one or more of entry and/or selection of environment parameters associated with trigger events, entry and/or selection of values of environment parameters associated with trigger events, and/or other information.

In some implementations, automated actions may be specified based on entry and/or selection of environment parameters to carry out actions on, entry and/or selection of values to apply to the entered and/or selected environment parameters, and/or other information. In some implementations, trigger events may be specified based on one or more of entry and/or selection one or more of individual external resources from which trigger events may be derived, individual actions by the individual external resources from which occurrence of the trigger events may be derived, and/or other information.

The user interface 400 may include a trigger input portion 404 to obtain entry and/or selection of a trigger event. The trigger input portion 404 may include a user interface element 408 configured to obtain information identifying a unit of work associated with the trigger event, a user interface element 410 configured to obtain entry and/or selection of an environment parameter associated with the trigger event, and a user interface element 412 configured to obtain entry and/or selection of a value for the environment parameter associated with the trigger event. For illustrative purposes, the trigger event in FIG. 4 may refer to the status of the task named “Task1” being “marked complete.”

The user interface 400 may include an automated action input portion 414 to obtain entry and/or selection of a set of automated actions. The automated action input portion 414 may include a user interface element 420 configured to obtain entry and/or selection of an identification of an external resource (e.g., a name of an external application of the external resource). For illustrative purposes, the external resource may be identified as “MyCalendar” which may be an external calendar application.

The automated action input portion 414 may include user interface element 424 configured to obtain entry and/or selection of an action to carry out in the identified external resource. For illustrative purposes, the action to carry out may include “Set a reminder.”

The automated action input portion 414 may include a user interface element 428 configured to obtain entry and/or selection of a further specification of the action to carry out in the identified external resource. For illustrative purposes, the further specification may include setting the content of the reminder to “Follow up.”

It is noted that FIG. 4 is for illustrative purposes only and is not to be considered limiting. Instead, it is to be understood that the user interface 400 may be configured in other ways and/or including other elements in accordance with one or more implementations of the system 100 presented herein.

FIG. 5 illustrates a user interface 500, in accordance with one or more implementations. The user interface 500 may include one or more user interface elements configured to facilitate user interaction with the user interface 500. The user interaction may include input to select one or more automation templates. By way of non-limiting illustration, the user interface 500 may include a first user interface element 502, a second user interface element 506, and/or other user interface elements. The first user interface element 502 may be selected to effectuate a first template 504. The second user interface element 506 may be selected to effectuate a second template 508.

It is noted that FIG. 5 is for illustrative purposes only and is not to be considered limiting. Instead, it is to be understood that the user interface 500 may be configured in other ways and/or including other elements in accordance with one or more implementations of the system 100 presented herein.

In FIG. 1, in some implementations, server(s) 102, client computing platform(s) 104, and/or external resource(s) 126 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network 116 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, client computing platform(s) 104, and/or external resource(s) 126 may be operatively linked via some other communication media.

A given client computing platform may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform to interface with system 100 and/or external resources 126, and/or provide other functionality attributed herein to client computing platform(s) 104. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

External resource(s) 126 may include sources of information outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resource(s) 126 may be provided by resources included in system 100.

Server(s) 102 may include electronic storage 128, one or more processors 130, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network 116 and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.

Electronic storage 128 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 128 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connected to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 128 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 128 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 128 may store software algorithms, information determined by processor(s) 130, information received from server(s) 102, information received from client computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.

Processor(s) 130 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 130 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 130 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 130 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 130 may represent processing functionality of a plurality of devices operating in coordination. Processor(s) 130 may be configured to execute components 108, 110, 112, 114, and/or other components. Processor(s) 130 may be configured to execute components 108, 110, 112, and/or 114, and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 130. As used herein, the term “component” may refer to any component or set of components that perform the functionality attributed to the component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although components 108, 110, 112, and/or 114 are illustrated in FIG. 1 as being implemented within a single processing unit, in implementations in which processor(s) 130 includes multiple processing units, one or more of components 108, 110, 112, and/or 114 may be implemented remotely from the other components. The description of the functionality provided by the different components 108, 110, 112, and/or 114 described below is for illustrative purposes, and is not intended to be limiting, as any of components 108, 110, 112, and/or 114 may provide more or less functionality than is described. For example, one or more of components 108, 110, 112, and/or 114 may be eliminated, and some or all of its functionality may be provided by other ones of components 108, 110, 112, and/or 114. As another example, processor(s) 130 may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components 108, 110, 112, and/or 114.

FIG. 2 illustrates a method 200 to effectuate sets of automated actions outside a collaboration environment based on trigger events occurring within the collaboration environment, in accordance with one or more implementations. The operations of method 200 presented below are intended to be illustrative. In some implementations, method 200 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 200 are illustrated in FIG. 2 and described below is not intended to be limiting.

In some implementations, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.

An operation 202 may manage environment state information maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may specify values of environment parameters and/or other information. The environment parameters may include one or more of user parameters, work unit parameters, and/or other parameters. The values of the user parameters may describe one or more of the users, user actions of the users within the collaboration environment, user settings of the users, and/or other information about the users. The values of work unit parameters may describe units of work managed, created, and/or assigned within the collaboration environment, and/or other information about units of work. Operation 202 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108, in accordance with one or more implementations.

An operation 204 may generate automation information and/or other information. The automation information may be generated based on user entry and/or selection of the automation information into a user interface. The automation information may specify sets of automated actions to carry out outside of the collaboration environment in response to occurrence of trigger events within the collaboration environment. The user entry and/or selection of the automation information may include entry and/or selection of one or more of individual automated actions in individual sets of automated actions, individual trigger events, and/or other information. By way of non-limiting illustration, the automation information may specify a first set of automated actions to carry out outside of the collaboration environment in response to a first trigger event occurring within the collaboration environment. The first set of automated actions and/or the first trigger event may be generated based on input by a first user into a user interface. Operation 204 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to automation component 110, in accordance with one or more implementations.

An operation 206 may detect occurrence of the trigger events within the collaboration. The occurrence of the trigger events within the collaboration may be based on changes in the values of the environment parameters and/or other events occurring within the collaboration environment. By way of non-limiting illustration, an occurrence of the first trigger event may be detected based on a first change in a first value of a first environment parameter to a second value. In some implementations, the first trigger event may be associated with the first change (e.g., a state change of the first environment parameter). In some implementations, the first trigger event may be associated with the second value (e.g., a data change of the first environment parameter). Operation 206 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to automation component 110, in accordance with one or more implementations.

An operation 208 may effectuate individual sets of automated actions outside the collaboration environment. The effectuation of the individual sets of automated actions outside the collaboration environment may be responsive to the detection of the occurrence of individual trigger events within the collaboration environment. By way of non-limiting illustration, responsive to the detection of the first trigger event, the first set of automated actions may be effectuated outside the collaboration environment. Operation 208 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to automation component 110, in accordance with one or more implementations.

FIG. 3 illustrates a method 300 to effectuate sets of automated actions within a collaboration environment based on trigger events occurring outside the collaboration environment, in accordance with one or more implementations. The operations of method 300 presented below are intended to be illustrative. In some implementations, method 300 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 300 are illustrated in FIG. 3 and described below is not intended to be limiting.

In some implementations, method 300 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 300 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 300.

An operation 302 may manage environment state information maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may specify values of environment parameters and/or other information. The environment parameters may include one or more of user parameters, work unit parameters, and/or other parameters. The values of the user parameters may describe one or more of the users, user actions of the users within the collaboration environment, user settings of the users, and/or other information about the users. The values of work unit parameters may describe units of work managed, created, and/or assigned within the collaboration environment, and/or other information about units of work. Operation 302 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108, in accordance with one or more implementations.

An operation 304 may generate automation information and/or other information. The automation information may be generated based on user entry and/or selection of the automation information into a user interface. The automation information may specify sets of automated actions to carry out within of the collaboration environment in response to occurrence of trigger events outside the collaboration environment. The user entry and/or selection of the automation information may include entry and/or selection of one or more of individual automated actions in individual sets of automated actions, individual trigger events, and/or other information. By way of non-limiting illustration, the automation information may specify a first set of automated actions to carry out within of the collaboration environment in response to a first trigger event occurring outside the collaboration environment. The first set of automated actions and/or the first trigger event may be generated based on input by a first user into a user interface. Operation 304 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to automation component 110, in accordance with one or more implementations.

An operation 306 may obtain information indicating occurrence of the trigger events outside the collaboration environment. By way of non-limiting illustration, first information may be obtained. The first information may indicate an occurrence of the first trigger event outside the collaboration environment. Operation 306 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to automation component 110, in accordance with one or more implementations.

An operation 308 may effectuate individual sets of automated actions within the collaboration environment. The effectuation of the individual sets of automated actions outside the collaboration environment may be responsive to obtaining the information indicating the occurrence of the trigger events outside the collaboration environment. By way of non-limiting illustration, responsive to obtaining the information indicating the occurrence of the first trigger event outside the collaboration environment, the first set of automated actions may be effectuated within the collaboration environment. Operation 308 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to automation component 110, in accordance with one or more implementations.

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.

Claims

1. A system configured to effectuate sets of automated actions outside a collaboration environment based on trigger events occurring within the collaboration environment, the system comprising: one or more physical processors configured by machine-readable instructions to: manage environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment, the environment state information including values of environment parameters, the environment parameters including user parameters and work unit parameters, the values of the user parameters describing one or more of the users, user actions of the users within the collaboration environment, or user settings of the users, the values of the work unit parameters describing units of work created and assigned within the collaboration environment, the units of work being described based on one or more actions that the users assigned to the units of work are expected to accomplish in order to mark the units of work as complete;generate automation information based on user entry or selection of the automation information into a user interface, the automation information specifying sets of automated actions to carry out by a payment application resource that is managed outside of the collaboration environment in response to occurrence of trigger events within the collaboration environment, the user entry or selection of the automation information including entry or selection of individual automated actions and individual trigger events, such that the automation information specifies a first set of automated actions to carry out by the payment application resource outside of the collaboration environment in response to a first trigger event occurring within the collaboration environment;detect the occurrence of the trigger events within the collaboration environment based on changes to the units of work, the changes including one or both of completion state changes or due date changes, such that an occurrence of the first trigger event is detected based on a first change to a first unit of work; andresponsive to detection of the occurrence of the individual trigger events: establish a connection with the payment application resource that is managed outside of the collaboration environment; andcause the payment application resource to perform the sets of automated actions outside the collaboration environment, such that responsive to detection of the occurrence of the first trigger event, cause the payment application resource to perform the first set of automated actions outside the collaboration environment, the first set of automated actions performed by the payment application resource including sending one or more electronic payments.
2. The system of claim 1, wherein an automated action is defined by a target component and an action component, the target component identifying the payment application resource outside the collaboration environment to which an action is to be carried out with, and the action component defining instructions to effectuate the action by the payment application resource outside the collaboration environment.
3. The system of claim 2, wherein the instructions to effectuate the action by the payment application resource outside the collaboration environment includes performing an application programming interface call to the payment application resource to cause the payment application resource to execute a routine in accordance with the action.
4. The system of claim 1, wherein the one or more physical processors are further configured by the machine-readable instructions to: responsive to the detection of the occurrence of the individual trigger events: establish a connection with a social media application resource that is managed outside of the collaboration environment; andcause the social media application resource to perform the sets of automated actions outside the collaboration environment, such that responsive to detection of the occurrence of a second trigger event, cause the social media application resource to perform a second set of automated actions outside the collaboration environment, the second set of automated actions performed by the social media application resource including posting content within a social media platform.
5. The system of claim 1, wherein the individual trigger events are associated with individual occurrences of the changes to the units of work, such that the first trigger event is associated with an occurrence of the first change.
6. The system of claim 1, wherein the individual trigger events are associated with substance of the changes to the units of work, such that the first trigger event is associated with the substance of the first change.
7. The system of claim 1, wherein an individual automated action is carried out immediately or within a specified time frame following an individual detection of an individual occurrence of an individual trigger event.
8. The system of claim 1, further comprising non-transitory electronic storage storing one or more automation templates, an automation template specifying a predetermined set of automated actions to carry out outside the collaboration environment in response to occurrence of a predetermined trigger event occurring within the collaboration environment.
9. The system of claim 1, wherein the first change is a due date change.
10. The system of claim 1, wherein the first change is a completion state change.
11. A method to effectuate sets of automated actions outside a collaboration environment based on trigger events occurring within the collaboration environment, the method comprising: managing environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by users with the collaboration environment, the environment state information including values of environment parameters, the environment parameters including user parameters and work unit parameters, the values of the user parameters describing one or more of the users, user actions of the users within the collaboration environment, or user settings of the users, the values of the work unit parameters describing units of work created and assigned within the collaboration environment, the units of work being described based on one or more actions that the users assigned to the units of work are expected to accomplish in order to mark the units of work as complete;generating automation information based on user entry or selection of the automation information into a user interface, the automation information specifying sets of automated actions to carry out by a payment application resource that is managed outside of the collaboration environment in response to occurrence of trigger events within the collaboration environment, the user entry or selection of the automation information including entry or selection of individual automated actions and individual trigger events, the automation information specifying a first set of automated actions to carry out by the payment application resource outside of the collaboration environment in response to a first trigger event occurring within the collaboration environment;detecting the occurrence of the trigger events within the collaboration environment based on changes to the units of work, the changes including one or both of completion state changes or due date changes, including detecting an occurrence of the first trigger event based on a first change to a first unit of work; andresponsive to detection of the occurrence of the individual trigger events: establishing a connection with the payment application resource that is managed outside of the collaboration environment; andcausing the payment application resource to perform the sets of automated actions outside the collaboration environment, including responsive to detection of the occurrence of the first trigger event, causing the payment application resource to perform the first set of automated actions outside the collaboration environment, the first set of automated actions performed by the payment application resource including sending one or more electronic payments.
12. The method of claim 11, wherein an automated action is defined by a target component and an action component, the target component identifying the payment application resource outside the collaboration environment to which an action is to be carried out with, and the action component defining instructions to effectuate the action by the payment application resource outside the collaboration environment.
13. The method of claim 12, wherein the instructions to effectuate the action by the payment application resource outside the collaboration environment includes performing an application programming interface call to the payment application resource to cause the payment application resource to execute a routine in accordance with the action.
14. The method of claim 11, further comprising: responsive to the detection of the occurrence of the individual trigger events: establishing a connection with a social media application resource that is managed outside of the collaboration environment; andcausing the social media application resource to perform the sets of automated actions outside the collaboration environment, including responsive to detection of the occurrence of a second trigger event, causing the social media application resource to perform a second set of automated actions outside the collaboration environment, the second set of automated actions performed by the social media application resource including posting content within a social media platform.
15. The method of claim 11, wherein the individual trigger events are associated with individual occurrences of the changes to the units of work, such that the first trigger event is associated with an occurrence of the first change.
16. The method of claim 11, wherein the individual trigger events are associated with substance of the changes to the units of work, such that the first trigger event is associated with the substance of the first change.
17. The method of claim 11, wherein an individual automated action is carried out immediately or within a specified time frame following an individual detection of an individual occurrence of an individual trigger event.
18. The method of claim 11, further comprising storing one or more automation templates, an automation template specifying a predetermined set of automated actions to carry out outside the collaboration environment in response to occurrence of a predetermined trigger event occurring within the collaboration environment.
19. The method of claim 11, wherein the first change is a due date change.
20. The method of claim 11, wherein the first change is a completion state change.

US Referenced Citations (449)

Number	Name	Date	Kind
5233687	Henderson, Jr.	Aug 1993	A
5524077	Faaland	Jun 1996	A
5530861	Diamant	Jun 1996	A
5623404	Collins	Apr 1997	A
5721770	Kohler	Feb 1998	A
5983277	Heile	Nov 1999	A
6024093	Cron	Feb 2000	A
6256651	Tuli	Jul 2001	B1
6292830	Taylor	Sep 2001	B1
6385639	Togawa	May 2002	B1
6621505	Beauchamp	Sep 2003	B1
6629081	Cornelius	Sep 2003	B1
6769013	Frees	Jul 2004	B2
6859523	Jilk	Feb 2005	B1
7020697	Goodman	Mar 2006	B1
7039596	Lu	May 2006	B1
7086062	Faour	Aug 2006	B1
7349920	Feinberg	Mar 2008	B1
7418482	Lusher	Aug 2008	B1
7428723	Greene	Sep 2008	B2
7640511	Keel	Dec 2009	B1
7676542	Moser	Mar 2010	B2
7779053	Beck	Aug 2010	B2
7805327	Schulz	Sep 2010	B1
7917855	Satish	Mar 2011	B1
7996744	Ojala	Aug 2011	B2
7996774	Sidenur	Aug 2011	B1
8214747	Yankovich	Jul 2012	B1
8314809	Grabowski	Nov 2012	B1
8499300	Zimberg	Jul 2013	B2
8522240	Merwarth	Aug 2013	B1
8527287	Bhatia	Sep 2013	B1
8554832	Moskovitz	Oct 2013	B1
8572477	Moskovitz	Oct 2013	B1
8627199	Handley	Jan 2014	B1
8639552	Chen	Jan 2014	B1
8768751	Jakowski	Jul 2014	B2
8831879	Stamm	Sep 2014	B2
8843832	Frields	Sep 2014	B2
8863021	Bee	Oct 2014	B1
9009096	Pinckney	Apr 2015	B2
9024752	Tumayan	May 2015	B2
9143839	Reisman	Sep 2015	B2
9152668	Moskovitz	Oct 2015	B1
9201952	Chau	Dec 2015	B1
9208262	Bechtel	Dec 2015	B2
9251484	Cantor	Feb 2016	B2
9350560	Hupfer	May 2016	B2
9383917	Mouton	Jul 2016	B2
9405532	Sullivan	Aug 2016	B1
9405810	Smith	Aug 2016	B2
9454623	Kaptsan	Sep 2016	B1
9491249	Rosenshine	Nov 2016	B2
9514424	Kleinbart	Dec 2016	B2
9565246	Tsypliaev	Feb 2017	B1
9600136	Yang	Mar 2017	B1
9712576	Gill	Jul 2017	B1
9785445	Mitsui	Oct 2017	B2
9842312	Rosati	Dec 2017	B1
9949681	Badenes	Apr 2018	B2
9953282	Shaouy	Apr 2018	B2
9959420	Kiang	May 2018	B2
9978040	Lee	May 2018	B2
9990636	Lewis	Jun 2018	B1
10001911	Breedvelt-Schouten	Jun 2018	B2
10003693	Wolthuis	Jun 2018	B2
10083412	Suntinger	Sep 2018	B2
10157355	Johnson	Dec 2018	B2
10192181	Katkar	Jan 2019	B2
10235156	Johnson	Mar 2019	B2
10264067	Subramani	Apr 2019	B2
10308992	Chauvin	Jun 2019	B2
10373084	Kurjanowicz	Aug 2019	B2
10373090	Holm	Aug 2019	B2
10382501	Malatesha	Aug 2019	B2
10455011	Kendall	Oct 2019	B2
10496943	De	Dec 2019	B2
10594788	Larabie-Belanger	Mar 2020	B2
10606859	Smith	Mar 2020	B2
10613735	Karpe	Apr 2020	B1
10671692	Koopman	Jun 2020	B2
10684870	Sabo	Jun 2020	B1
10706484	Murnock	Jul 2020	B1
10785046	Raghavan	Sep 2020	B1
10810222	Koch	Oct 2020	B2
10846105	Granot	Nov 2020	B2
10846297	Smith	Nov 2020	B2
10922104	Sabo	Feb 2021	B2
10956845	Sabo	Mar 2021	B1
10977434	Pelz	Apr 2021	B2
10983685	Karpe	Apr 2021	B2
11082281	Rosenstein	Aug 2021	B2
11095468	Pandey	Aug 2021	B1
11140174	Patel	Oct 2021	B2
11204683	Sabo	Dec 2021	B1
11212242	Cameron	Dec 2021	B2
11263228	Koch	Mar 2022	B2
11288081	Sabo	Mar 2022	B2
11290296	Raghavan	Mar 2022	B2
11327645	Karpe	May 2022	B2
11341444	Sabo	May 2022	B2
11341445	Cheng	May 2022	B1
20020065798	Bostleman	May 2002	A1
20020082889	Oliver	Jun 2002	A1
20020143594	Kroeger	Oct 2002	A1
20030028595	Vogt	Feb 2003	A1
20030036934	Ouchi	Feb 2003	A1
20030041317	Sokolov	Feb 2003	A1
20030097410	Atkins	May 2003	A1
20030126001	Northcutt	Jul 2003	A1
20030225598	Yu	Dec 2003	A1
20030233265	Lee	Dec 2003	A1
20030233268	Taqbeem	Dec 2003	A1
20040030992	Moisa	Feb 2004	A1
20040083448	Schulz	Apr 2004	A1
20040093290	Doss	May 2004	A1
20040093351	Lee	May 2004	A1
20040098291	Newburn	May 2004	A1
20040125150	Adcock	Jul 2004	A1
20040187089	Schulz	Sep 2004	A1
20040207249	Baumgartner	Oct 2004	A1
20040230447	Schwerin-Wenzel	Nov 2004	A1
20040268451	Robbin	Dec 2004	A1
20050216111	Ooshima	Sep 2005	A1
20050222971	Cary	Oct 2005	A1
20060028917	Wigginton	Feb 2006	A1
20060047454	Tamaki	Mar 2006	A1
20060085245	Takatsuka	Apr 2006	A1
20060095859	Booking	May 2006	A1
20060136441	Fujisaki	Jun 2006	A1
20060167736	Weiss	Jul 2006	A1
20060190391	Cullen	Aug 2006	A1
20060200264	Kodama	Sep 2006	A1
20060218551	Berstis	Sep 2006	A1
20060224430	Butt	Oct 2006	A1
20060277487	Poulsen	Dec 2006	A1
20070016646	Tendjoukian	Jan 2007	A1
20070025567	Fehr	Feb 2007	A1
20070038494	Kreitzberg	Feb 2007	A1
20070041542	Schramm	Feb 2007	A1
20070050225	Leslie	Mar 2007	A1
20070073575	Yomogida	Mar 2007	A1
20070143169	Grant	Jun 2007	A1
20070147178	Masuda	Jun 2007	A1
20070150327	Dromgold	Jun 2007	A1
20070232278	May	Oct 2007	A1
20070245300	Chan	Oct 2007	A1
20070255674	Mahoney	Nov 2007	A1
20070255715	Li	Nov 2007	A1
20070260499	Greef	Nov 2007	A1
20070288283	Fitzpatrick	Dec 2007	A1
20070294344	Mohan	Dec 2007	A1
20080005235	Hegde	Jan 2008	A1
20080033777	Shukoor	Feb 2008	A1
20080046471	Moore	Feb 2008	A1
20080079730	Zhang	Apr 2008	A1
20080082389	Gura	Apr 2008	A1
20080082956	Gura	Apr 2008	A1
20080120129	Seubert	May 2008	A1
20080126930	Scott	May 2008	A1
20080126945	Munkvold	May 2008	A1
20080134069	Horvitz	Jun 2008	A1
20080155547	Weber	Jun 2008	A1
20080158023	Chung	Jul 2008	A1
20080167937	Coughlin	Jul 2008	A1
20080175104	Grieb	Jul 2008	A1
20080195964	Randell	Aug 2008	A1
20080221946	Balon	Sep 2008	A1
20080222566	Daughtrey	Sep 2008	A1
20080268876	Gelfand	Oct 2008	A1
20080270198	Graves	Oct 2008	A1
20080281665	Opaluch	Nov 2008	A1
20080313004	Ryan	Dec 2008	A1
20080313595	Boulineau	Dec 2008	A1
20090048986	Anderson	Feb 2009	A1
20090055796	Springborn	Feb 2009	A1
20090076878	Woerner	Mar 2009	A1
20090089133	Johnson	Apr 2009	A1
20090094623	Chakra	Apr 2009	A1
20090113310	Appleyard	Apr 2009	A1
20090133027	Gunning	May 2009	A1
20090167553	Hong	Jul 2009	A1
20090187454	Khasin	Jul 2009	A1
20090199192	Laithwaite	Aug 2009	A1
20090204463	Burnett	Aug 2009	A1
20090204471	Elenbaas	Aug 2009	A1
20090234699	Steinglass	Sep 2009	A1
20090241053	Augustine	Sep 2009	A1
20090260010	Burkhart	Oct 2009	A1
20090287523	Lau	Nov 2009	A1
20090296908	Lee	Dec 2009	A1
20090299803	Lakritz	Dec 2009	A1
20100005087	Basco	Jan 2010	A1
20100063860	Gallion	Mar 2010	A1
20100070888	Watabe	Mar 2010	A1
20100088137	Weiss	Apr 2010	A1
20100106627	O'Sullivan	Apr 2010	A1
20100114786	Aboujaoude	May 2010	A1
20100115523	Kuschel	May 2010	A1
20100122334	Stanzione	May 2010	A1
20100131860	Dehaan	May 2010	A1
20100145801	Chekuri	Jun 2010	A1
20100169146	Hoyne	Jul 2010	A1
20100169802	Goldstein	Jul 2010	A1
20100180212	Gingras	Jul 2010	A1
20100223575	Leukart	Sep 2010	A1
20100269049	Fearon	Oct 2010	A1
20100299171	Lau	Nov 2010	A1
20100312605	Mitchell	Dec 2010	A1
20100313151	Wei	Dec 2010	A1
20110015961	Chan	Jan 2011	A1
20110022662	Barber-Mingo	Jan 2011	A1
20110054968	Galaviz	Mar 2011	A1
20110055177	Chakra	Mar 2011	A1
20110071878	Gingras	Mar 2011	A1
20110071893	Malhotra	Mar 2011	A1
20110072372	Fritzley	Mar 2011	A1
20110093538	Weir	Apr 2011	A1
20110093619	Nelson	Apr 2011	A1
20110107333	Kapoor	May 2011	A1
20110113365	Kimmerly	May 2011	A1
20110154216	Aritsuka	Jun 2011	A1
20110161128	Barney	Jun 2011	A1
20110184768	Norton	Jul 2011	A1
20110270644	Roncolato	Nov 2011	A1
20110307100	Schmidtke	Dec 2011	A1
20110307772	Lloyd	Dec 2011	A1
20120030194	Jain	Feb 2012	A1
20120035942	Graupner	Feb 2012	A1
20120066030	Limpert	Mar 2012	A1
20120066411	Jeide	Mar 2012	A1
20120072251	Mircean	Mar 2012	A1
20120079449	Sanderson	Mar 2012	A1
20120110087	Culver	May 2012	A1
20120117499	Mori	May 2012	A1
20120123835	Chu	May 2012	A1
20120131191	May	May 2012	A1
20120158946	Shafiee	Jun 2012	A1
20120192086	Ghods	Jul 2012	A1
20120221963	Motoyama	Aug 2012	A1
20120239451	Caligor	Sep 2012	A1
20120254218	Ali	Oct 2012	A1
20120266068	Ryman	Oct 2012	A1
20120278388	Kleinbart	Nov 2012	A1
20120296993	Heyman	Nov 2012	A1
20120304187	Maresh	Nov 2012	A1
20120317108	Okazaki	Dec 2012	A1
20130007332	Teh	Jan 2013	A1
20130013560	Goldberg	Jan 2013	A1
20130014023	Lee	Jan 2013	A1
20130018688	Nudd	Jan 2013	A1
20130018952	Mcconnell	Jan 2013	A1
20130021629	Kurilin	Jan 2013	A1
20130066944	Laredo	Mar 2013	A1
20130067375	Kim	Mar 2013	A1
20130067549	Caldwell	Mar 2013	A1
20130073328	Ehrler	Mar 2013	A1
20130103412	Nudd	Apr 2013	A1
20130124638	Barreto	May 2013	A1
20130151421	Van Der Ploeg	Jun 2013	A1
20130151604	Ranade	Jun 2013	A1
20130173486	Peters	Jul 2013	A1
20130179208	Chung	Jul 2013	A1
20130179799	Savage	Jul 2013	A1
20130215116	Siddique	Aug 2013	A1
20130227007	Savage	Aug 2013	A1
20130246110	Nakhayi Ashtiani	Sep 2013	A1
20130246399	Schneider	Sep 2013	A1
20130275229	Moganti	Oct 2013	A1
20130279685	Kohler	Oct 2013	A1
20130317871	Kulkarni	Nov 2013	A1
20130321467	Tappen	Dec 2013	A1
20130339099	Aidroos	Dec 2013	A1
20130339831	Gulanikar	Dec 2013	A1
20140007005	Libin	Jan 2014	A1
20140012603	Scanlon	Jan 2014	A1
20140025767	De Kezel	Jan 2014	A1
20140036639	Boni	Feb 2014	A1
20140040780	Artzt	Feb 2014	A1
20140040905	Tadanobu	Feb 2014	A1
20140058801	Deodhar	Feb 2014	A1
20140059910	Norton	Mar 2014	A1
20140074536	Meushar	Mar 2014	A1
20140089719	Daum	Mar 2014	A1
20140101310	Savage	Apr 2014	A1
20140156539	Brunet	Jun 2014	A1
20140165001	Shapiro	Jun 2014	A1
20140172478	Vadasz	Jun 2014	A1
20140200944	Henriksen	Jul 2014	A1
20140208325	Chen	Jul 2014	A1
20140215344	Ligman	Jul 2014	A1
20140229609	Wong	Aug 2014	A1
20140236663	Smith	Aug 2014	A1
20140244334	De	Aug 2014	A1
20140257894	Melahn	Sep 2014	A1
20140279294	Field-Darragh	Sep 2014	A1
20140288987	Liu	Sep 2014	A1
20140310047	De	Oct 2014	A1
20140310051	Meng	Oct 2014	A1
20140350997	Holm	Nov 2014	A1
20140364987	Shikano	Dec 2014	A1
20150006448	Gupta	Jan 2015	A1
20150007058	Wooten	Jan 2015	A1
20150012330	Sugiura	Jan 2015	A1
20150052437	Crawford	Feb 2015	A1
20150058053	De	Feb 2015	A1
20150113540	Rabinovici	Apr 2015	A1
20150134393	De	May 2015	A1
20150153906	Liao	Jun 2015	A1
20150213411	Swanson	Jul 2015	A1
20150215256	Ghafourifar	Jul 2015	A1
20150262111	Yu	Sep 2015	A1
20150312375	Valey	Oct 2015	A1
20150317595	De	Nov 2015	A1
20150339006	Chaland	Nov 2015	A1
20150363733	Brown	Dec 2015	A1
20150379472	Gilmour	Dec 2015	A1
20160012368	O'Connell	Jan 2016	A1
20160048408	Madhu	Feb 2016	A1
20160048786	Fukuda	Feb 2016	A1
20160063192	Johnson	Mar 2016	A1
20160063449	Duggan	Mar 2016	A1
20160072750	Kass	Mar 2016	A1
20160110670	Chatterjee	Apr 2016	A1
20160124775	Ashtiani	May 2016	A1
20160140474	Vekker	May 2016	A1
20160140501	Figlin	May 2016	A1
20160147773	Smith	May 2016	A1
20160147846	Smith	May 2016	A1
20160148157	Walia	May 2016	A1
20160180277	Skiba	Jun 2016	A1
20160180298	Mcclement	Jun 2016	A1
20160182311	Borna	Jun 2016	A1
20160188145	Vida	Jun 2016	A1
20160224939	Chen	Aug 2016	A1
20160234391	Wolthuis	Aug 2016	A1
20160275436	Kurjanowicz	Sep 2016	A1
20160313934	Isherwood	Oct 2016	A1
20160328217	Hagerty	Nov 2016	A1
20160342927	Reznik	Nov 2016	A1
20170004213	Cunico	Jan 2017	A1
20170009387	Ge	Jan 2017	A1
20170017364	Kekki	Jan 2017	A1
20170017924	Kashiwagi	Jan 2017	A1
20170039503	Jones	Feb 2017	A1
20170061341	Haas	Mar 2017	A1
20170068933	Norton	Mar 2017	A1
20170093874	Uthe	Mar 2017	A1
20170099296	Fisher	Apr 2017	A1
20170103369	Thompson	Apr 2017	A1
20170116552	Deodhar	Apr 2017	A1
20170132200	Noland	May 2017	A1
20170153799	Hoyer	Jun 2017	A1
20170177671	Allgaier	Jun 2017	A1
20170185592	Frei	Jun 2017	A1
20170192642	Fishman	Jul 2017	A1
20170206217	Deshpande	Jul 2017	A1
20170223069	Arora	Aug 2017	A1
20170249577	Nishikawa	Aug 2017	A1
20170316367	Candito	Nov 2017	A1
20170317898	Candito	Nov 2017	A1
20170323233	Bencke	Nov 2017	A1
20170323267	Baek	Nov 2017	A1
20170323350	Laderer	Nov 2017	A1
20170344754	Kumar	Nov 2017	A1
20170344931	Shenk	Nov 2017	A1
20170346861	Pearl	Nov 2017	A1
20180032524	Byron	Feb 2018	A1
20180052943	Hui	Feb 2018	A1
20180053127	Boileau	Feb 2018	A1
20180059910	Wooten	Mar 2018	A1
20180060785	Carnevale	Mar 2018	A1
20180060818	Ishiyama	Mar 2018	A1
20180063063	Yan	Mar 2018	A1
20180068271	Abebe	Mar 2018	A1
20180075387	Kulkarni	Mar 2018	A1
20180088754	Psenka	Mar 2018	A1
20180089625	Rosati	Mar 2018	A1
20180095938	Monte	Apr 2018	A1
20180109421	Laribi	Apr 2018	A1
20180131649	Ma	May 2018	A1
20180157477	Johnson	Jun 2018	A1
20180165610	Dumant	Jun 2018	A1
20180173386	Adika	Jun 2018	A1
20180189706	Newhouse	Jul 2018	A1
20180189736	Guo	Jul 2018	A1
20180225795	Napoli	Aug 2018	A1
20180247352	Rogers	Aug 2018	A1
20180260081	Beaudoin	Sep 2018	A1
20180262620	Wolthuis	Sep 2018	A1
20180285471	Hao	Oct 2018	A1
20180316636	Kamat	Nov 2018	A1
20180331842	Faulkner	Nov 2018	A1
20180357049	Epstein	Dec 2018	A1
20180367483	Rodriguez	Dec 2018	A1
20180373804	Zhang	Dec 2018	A1
20190005048	Crivello	Jan 2019	A1
20190018552	Bloy	Jan 2019	A1
20190034057	Rudchenko	Jan 2019	A1
20190068390	Gross	Feb 2019	A1
20190079909	Purandare	Mar 2019	A1
20190080289	Kreitler	Mar 2019	A1
20190095839	Itabayashi	Mar 2019	A1
20190095846	Gupta	Mar 2019	A1
20190102700	Babu	Apr 2019	A1
20190138583	Silk	May 2019	A1
20190138589	Udell	May 2019	A1
20190138961	Santiago	May 2019	A1
20190139004	Vukovic	May 2019	A1
20190147386	Balakrishna	May 2019	A1
20190187987	Fauchère	Jun 2019	A1
20190213509	Burleson	Jul 2019	A1
20190265821	Pearl	Aug 2019	A1
20190340296	Cunico	Nov 2019	A1
20190340574	Ekambaram	Nov 2019	A1
20190347094	Sullivan	Nov 2019	A1
20190347126	Bhandari	Nov 2019	A1
20190370320	Kalra	Dec 2019	A1
20200019907	Notani	Jan 2020	A1
20200059539	Wang	Feb 2020	A1
20200065736	Relangi	Feb 2020	A1
20200162315	Siddiqi	May 2020	A1
20200192538	Karpe	Jun 2020	A1
20200192908	Smith	Jun 2020	A1
20200193556	Jin	Jun 2020	A1
20200218551	Sabo	Jul 2020	A1
20200233879	Papanicolaou	Jul 2020	A1
20200328906	Raghavan	Oct 2020	A1
20200344253	Kurup	Oct 2020	A1
20200358628	Achyuth	Nov 2020	A1
20210004380	Koch	Jan 2021	A1
20210004381	Smith	Jan 2021	A1
20210097466	Sabo	Apr 2021	A1
20210103451	Sabo	Apr 2021	A1
20210110347	Khalil	Apr 2021	A1
20210136012	Barbitta	May 2021	A1
20210182475	Pelz	Jun 2021	A1
20210216562	Smith	Jul 2021	A1
20210232282	Karpe	Jul 2021	A1
20210320891	Rosenstein	Oct 2021	A1
20210342786	Jiang	Nov 2021	A1
20210382734	Rosenstein	Dec 2021	A1
20220019320	Sabo	Jan 2022	A1
20220058548	Garg	Feb 2022	A1
20220075792	Koch	Mar 2022	A1
20220078142	Cameron	Mar 2022	A1
20220158859	Raghavan	May 2022	A1
20220207489	Gupta	Jun 2022	A1
20220239516	Iyer	Jul 2022	A1

Foreign Referenced Citations (8)

Number	Date	Country
101305350	Nov 2008	CN
101563671	Oct 2009	CN
101339642	Dec 2011	CN
102378975	May 2015	CN
2015036817	Mar 2015	WO
2015123751	Aug 2015	WO
2016033493	Mar 2016	WO
2020006634	Jan 2020	WO

Non-Patent Literature Citations (48)

Entry
Sheth, A., Kochut, K.J., Workflow Applications to Research Agenda: Scalable and Dynamic Work Coordination and Collaboration Systems. In: Do{hacek over (g)}aç, A., Kalinichenko, L., Özsu, M.T., Sheth, A. (eds) Workflow Management Systems and Interoperability. NATO ASI Series, vol. 164. (Year: 1998).
Ghiani et al, Personalization of Context-Dependent Applications Through Trigger-Action Rules, ACM Transactions on Computer-Human Interaction vol. 24 Issue 2 Article No. 14 pp. 1-33 (Year: 2017).
Hartmann, “TimeProjectscheduling with resource capacities and requests varying with time: a case study,” 2013, Flexible services and manufacturing journal, vol. 25, No. 1, pp. 74-93 (Year: 2013).
Paul Minors, How to automate your tasks, youtube excerpts, Oct. 18, 2019 https://www.youtube.com/watch?v=lwF9XyUQrzw (Year: 2019).
Mauricio Aizawa, Zapier, How to Automate Asana Tasks creation using Evernote, youtube excerpts, Mar. 16, 2018 https://www.youtube.com/watch?v=BjDQ4Gny4WI (Year: 2018).
Critical chain project management, Wikipedia, archives org, Dec. 17, 2016 https://web.archive.Org/web/20161217090326/https://en.wikipedia.org/wiki/Critical_chain_project_management (Year: 2016) 5 pages.
Critical Path Method, Wikipedia, archives org, Sep. 19, 2017 https://web.archive.Org/web/20170919223814/https://en.wikipedia.org/wiki/Critical_path_method (Year: 2017) 6 pages.
Fruhlinger, Joshua. “The Best To-Do ListApps for Feeling Productive; With the right app, feeling productive can be just as gratifying as actually getting things done” Wall Street Journal (Online); New York, N.Y. [New York, N.Y]Nov. 8, 2013 (Year: 2013) 4 pages.
www.asana.com (as retrieved from https://web.archive.Org/web/20160101054536/https://asana.com/press and https://web.archive.org/web/20160101054527/https://asana.com/product) (Year: 2016) 15 pages.
“U.S. Appl. No. 14/584,750, Examiner Interview Summary dated Feb. 25, 2016”, 3 pgs.
“U.S. Appl. No. 14/584,750, Non Final Office Action dated Aug. 28, 2015”, 21 pgs.
“U.S. Appl. No. 14/584,750, Notice of Allowance dated Mar. 28, 2016”, 8 pgs.
“U.S. Appl. No. 14/584,750, Response filed Feb. 29, 2015 to Non Final Office Action dated Aug. 28, 2015”, 16 pgs.
“U.S. Appl. No. 14/584,850, Final Office Action dated Sep. 1, 2017”, 31 pgs.
“U.S. Appl. No. 14/584,850, Non Final Office Action dated Jan. 10, 2017”, 9 pgs.
“U.S. Appl. No. 14/584,850, Response filed Apr. 10, 2017 to Non Final Office Action dated Jan. 10, 2017”, 13 pgs.
Asana Demo and Product Tour, you tube excerpt, Dec. 7, 2017 https://www.youtube.com/watch?v=IMAFWVLGFyw (Year: 2017) (16 pages).
Asana integrations, Asana tutorial, youtube, excerpt, Nov. 16, 2016 https://www.youtube.com/watch?v=hBiQ7DJNinE (Year: 2016) (21 pages).
Asana Workload and Portfolios,youtube,excerpt, Aug. 1, 2019 https://www.youtube.com/watch?v=7XkNcfFDG6M (Year: 2019) (20 pages).
Asana YouTube channel, list of all product videos, Nov 19, 2014-Aug. 19, 2019 https://www.youtube.com/user/AsanaTeam/videos?disable_polymer=1 (Year: 2019) (5 pages).
Asana, Task dependencies, archives org, Aug. 25, 2017 https://web.archive.org/web/20170825002141/https://asana.com/guide/help/tas ks/dependencies (Year: 2017) (5 pages).
Asana,Manage your team capacity with Workload, youtube, excerpt, Aug. 1, 2019 https://www.youtube.com/watch?v=2ufXyZDzZnA&list=PLJFG93oi0wJAi UwyOhlGWHdtJzJrzylBv (Year: 2019) (1 page).
Biggs, “GateGuru Relaunches With New Ways to Streamline Your Travel Experience”, Techcrunch, (Apr. 26, 2013), 3 pgs.
Castaneda Samuel, Introduction Manual—Asana, Sep. 25, 2017 https://static1.squarespace.com/static/586d532ae58c6232db243a65/t/5c210c10f950b7fc7a8e3274/1545669658049/Asana+Manual.pdf (Year: 2017) (20 pages).
How to Asana Asana time tracking, youtube, excerpt, May 24, 2017 https://www.youtube.com/watch?v=z91qlex-TLc (Year: 2017) (1 page).
How to Asana, Asana project management, youtube, excerpt, Mar. 7, 2017 https://www.youtube.com/watch?v=qqANMTvVpE (Year: 2017) (28 pages).
How to Asana, Creating your first Asana project, youtube, excerpt, Jan. 31, 2017 https://www.youtube.com/watch?v=L04WmcUdsLo (Year: 2017) (1 page).
How to Asana, Getting Asana into your workflow, youtube, excerpt, Jul. 17, 2017 https://www.youtube.com/watch?v=7YLrNMdv3o (Year: 2017) (24 pages).
How to Asana, Planning with Asana calendar, youtube excerpt, Feb. 14, 2017 https://www.youtube.com/watch?v=w8t6KYiVPyc (Year: 2017) (19 pages).
How to Asana, Using Asana for task management, youtube, excerpt, Feb. 7, 2017 https://www.youtube.com/watch?v=vwvbgiejhQ (Year: 2017) (8 pages).
How to Asana, Visualizing work with Asana kanban boards, youtube, excerpt, Feb. 21, 2017 https://www.youtube.com/watch?v=jmZaZGydfPY (Year: 2017) (41 pages).
How to Asana, Workflow management, youtube, excerpt, May 30, 2017 https://www.youtube.com/watch?v=rk8nPWmXsRo (Year: 2017) (9 pages).
How to use Advanced Search in Asana, Asana tutorial, May 25, 2016 https://www.youtube.com/watch?v=5VyJ3toPfQM (Year: 2016) (28 pages).
Justin Rosenstein, Unveiling the Future of Asana, Mar. 28, 2018 https://www.youtube.com/watch?v=nRI?d_WM4Bc (Year: 2018) (2 pages).
Prioritize My Tasks in Asana, Asana tutorial, youtube, excerpt, May 25, 2016 https://www.youtube.com/watch?v=UbCnMvw01nl (Year: 2016) (3 pages).
Project views, Asana tutorial, youtube, excerpt May 25, 2016 https://www.youtube.com/watch?v=FYjA8ZH3ceQ (Year: 2016) (5 pages).
Using Asana Premium, Asana tutorial, youtube, excerpt, Sep. 10, 2016 https://www.youtube.com/watch?v=vMgLtDDmyeo (Year: 2016) (4 pages).
Where does Asana fit in, archives org, Jul. 8, 2017 https://web.archive.org/web/20170708150928/https://asana.com/guide/resource s/infosheets/where-does-asana-fit (Year: 2017) (5 pages).
www.cogmotive.com/blog/author/alan Alan Byrne: “Creating a company Shared Calendar in Office 365”; pp. 1-17; Sep. 10, 2013.
Assef, F., Cassius, T. S., & Maria, T. S. (2018). Confrontation between techniques of time measurement. Journal of Manufacturing Technology Management, 29(5), 789-810. (Year: 2018).
(Tiburca, Andrew) Best Team Calendar Applications for 2018-Toggl https://toggl.com/blog/best-team-calendar-applications-for-2018 (Year: 2017).
“How to Asana: Inviting teammates to Asana.” YouTube, Asana, Mar. 21, 2017, https://www.youtube.com/watch?v=TLOruY1KyxU (Year: 2017), 13 pages.
Lauren Labrecque, “Fostering Consumer-Brand Relationships in Social Media Environments: The Role of Parasocial Interaction”, 2014, Journal of Interactive Markeing, 28 (2014), pp. 134-148 (Year: 2014).
Macro, computer science, Wikipedia, archives org Feb. 11, 2020 http://web.archive.org/web/20200211082902/https://en.wikipedia.org/wiki/Macro_(computer_science) (Year: 2020).
Command and control, Wikipedia, archives org, Mar. 16, 2018 https://web.archive.org/web/20180316193655/https://en.wikipedia.org/wiki/Command_and_control (Year: 2018), 6 pages.
Dawei Li, “Deepcham: Collaborative Edge-Mediated Adaptive Deep Learning for Mobile Object Recognition”, 2016, IEEE/ACM, pp. 64-76. (Year: 2016).
Peter Wurman, “Coordinating Hundreds of Cooperative, Autonomous Vehicles in Warehouses,” 2008, AI Magazine, vol. 29, No. 1, pp. 9-19. (Year: 2008).
Sara Perez-Soler, “Towards Conversational Syntax for Domain-Specific Languages using Chatbots”, 2019, Journal of Object Technology, vol. 18, No. 2, pp. 5:1-21. (Year: 2019).

Systems and methods to effectuate sets of automated actions outside and/or within a collaboration environment based on trigger events occurring outside and/or within the collaboration environment

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Term Extension

Abstract

Description

Claims

US Referenced Citations (449)

Foreign Referenced Citations (8)

Non-Patent Literature Citations (48)