DELEGATION OF TASKS IN AN ENTERPRISE ENVIRONMENT

Disclosed are various embodiments for delegating tasks in an enterprise service. A user can associate an action or task within the enterprise service with a delegate. The user can also specify temporal restrictions with the delegation of the task. The temporal restrictions specified time limitations on the authority of the delegate.

BACKGROUND

In an enterprise environment, certain users can be tasked with approving or denying requests of various types. For example, a user in a managerial or supervisory role can be tasked with approving or denying requests for vacation from workers associated with the enterprise. As another example, a user can be tasked with approving or denying requests for changes to the compensation of workers in the enterprise. As yet another example, a user can be tasked with approving or denying requests for reimbursement of expense report for workers associated with the enterprise. Accordingly, certain users associated with an enterprise can be tasked with all manner of requests for approval or denial of requests from or on behalf of other users in the enterprise. If a user in this role is unavailable to approve or deny requests, these requests can cause delays or other issues within the organization.

DETAILED DESCRIPTION

The present disclosure relates to delegating tasks among users in an enterprise. Delegation of tasks can be discretely defined to link a particular action in an enterprise system with a set of temporal restrictions and one or more delegates of a user. Additionally, according to examples of the disclosure, the act of delegating a task to another user can be performed for any action in an enterprise system where a decision is sought from a primary deciding user. In this way, delegation logic need not be built into the logic or process that defines the action. Instead, any action can leverage the generalized delegation logic according to examples of the disclosure to delegate a decision or action in an enterprise application or service.

In many cases, employers have human resources (HR) systems that enable various features. For example, an HR system can allow employees, contractors, or other users associated with an enterprise to perform various HR-related tasks and receive HR services. The HR system can operate as a portal for compensation, vacation, employee benefits, time or attendance tracking, and other services associated with employees and/or contractors of an enterprise.

The HR system can allow to managers or supervisory users to interact with employees and contractors as well as to service various requests on behalf of other users in an organization. For example, the HR system can allow for employees to submit requests for vacation or sick leave. Such a request might be required to be approved or denied by the employee's supervisor or manager. In some cases, a supervisory or managerial user might have a large number of requests that require review and approval or denial. Additionally, the supervisory or managerial user might be unavailable to review the requests. In this scenario, a delegation framework can be desirable that allows delegates of the supervisory user to approve or deny requests on behalf of the user.

Examples of the disclosure provide a delegation framework in which supervisory users can delegate a task requiring a decision to one or more other users in the HR system. The delegation can also include temporal limitations that define a time period during which the other users are authorized to make a decision on behalf of the delegating user. The delegation framework does not allow the other users to log into the HR system as the delegating user. Instead, the delegation framework only permits delegates to make a decision regarding a task but do so under their own respective identifies within the HR system.

Accordingly, the delegating user can define a delegation that identifies one or more delegates as well as the task or action that the delegate is authorized to act upon on behalf of the delegating user. The delegating user can also define a time period during which the delegates are authorized to act on behalf of the delegating user. Examples of the disclosure can provide various user interfaces through which the delegating user and the delegate can access the HR system to setup delegation of a task as well as act upon a delegated task. In the following discussion, a general description of the system and its components is provided, followed by a discussion of the operation of the same.

FIG.1Ais an example of a management user interface100for viewing employee profiles. Presently, the management user interface100illustrates a user profile for a user, illustrated as the user “Jane Doe.” The management user interface100can represent a view into an HR system that can be accessed by the user. The user can be associated with a user account within the HR system.

The management user interface100can display one or more tasks in a task section103and potentially other suitable elements which are not shown and are not necessary for an understanding of examples of the disclosure. The task section103can list or categorize the tasks requiring approval or grant by the user. For example, as shown in the example ofFIG.1A, the HR system can generate a user interface that shows the approval tasks that are in a task queue associated with a user account. The task queue can contain the various tasks within the HR system that require review or approval by a user. The task queue can be presented in various ways. In one example, as shown inFIG.1A, the task queue can be categorized by the type of request. In another example, the task queue can be presented chronologically.

The task section103can also provide a visual indicator of how many tasks require review and/or approval by the user. The visual indicator can show a quantity of each category of task that requires action by the user, as shown in the example ofFIG.1A. The user can select one of the categories of tasks from the task section103to view the tasks requiring review and approval.

Continuing the example ofFIG.1A, reference is made toFIG.1B. In the management user interface100shown inFIG.1B, the user has selected one of the categories of tasks from the task section103ofFIG.1A. Accordingly, inFIG.1B, a task list user interface109can be shown, which lists the requests that require action by the user. The user can then select a request, review the request, and either approve or deny the request based upon the data within the request.

Accordingly, managing a potentially constant inflow of requests that require review and/or approval by a user can result in a backlog of requests that do not get handled in a timely manner. Therefore, examples of the disclosure can provide a framework for delegation of tasks in an HR system so that users can delegate the authority to approve or deny requests to one or more other users of the HR system. Additionally, examples of the disclosure can allow for temporal restrictions to be placed on the delegation of the authority to approve or deny requests.

With reference toFIG.2, shown is a networked environment200according to various embodiments. The networked environment200includes a computing environment203, and one or more client devices206, which are in data communication with each other via a network215. The network215includes, for example, the Internet, intranets, extranets, wide area networks (WANs), local area networks (LANs), wired networks, wireless networks, or other suitable networks, etc., or any combination of two or more such networks. For example, such networks may comprise satellite networks, cable networks, Ethernet networks, and other types of networks.

Various applications and/or other functionality may be executed in the computing environment203according to various embodiments. The components executed on the computing environment203, for example, may include a delegation service221, an enterprise service223, and other applications, services, processes, systems, engines, or functionality not discussed in detail herein. The enterprise service223can include, for example, an HR service. The enterprise service223can also include other types of network accessible services that can service multiple users over a network215. For example, the enterprise service223can include an email service, an enterprise resource planning (ERP) service, a customer relationship management (CRM) service, or any other type of service that can serve multiple users.

The delegation service221can be executed to facilitate delegation of tasks between users of the enterprise service223. In some examples, the delegation service221can represent a standalone service that is separate from the enterprise service223or as a module or functionality that is integrated into the enterprise service223. The delegation service221can allow users to define tasks that can be delegated to other users or user groups who are also users of the enterprise service223. The delegation service221can also allow users to specify temporal limitations on the delegation of tasks to other users. In some examples, the delegation service221can automatically discover tasks that can be delegated to other users based upon whether a given user is out-of-office or is failing to respond to requests in a timely manner.

Various data is stored in a data store225that is accessible to the computing environment203. The data store225may be representative of a plurality of data stores225as can be appreciated. The data stored in the data store225, for example, is associated with the operation of the various applications and/or functional entities described below. In some embodiments, the data store225can also represent a search index database for identifying user profiles228based at least in part on a search query. For example, the search query can include items (e.g., search criteria) for identifying a user profile stored in the data store225. The search index data can include an index that associates the user profile228with the data associated with the user profile228. The data stored in the data store225includes, for example, user profiles228, and potentially other data. The user profile228can represent a user account for a user at a company. The user profile228can include profile data233, a task queue236, delegate data239, a user identifier230, and other suitable data.

The user identifier230can represent a unique identifier for each user profile228. In some examples, the user identifier230can be an alphanumeric character string, a data signature, a device signature, or other suitable identifiers. In some embodiments, the data signature can include a set of unique data for the user (e.g., hire data, social security number, employee number or identifier, residence location, etc.). The device signature for a user can include one or more of an internet protocol (IP) address, a device identifier of a client device206, a device type, an operating system version, a set of installed applications, and other suitable unique data for a user.

The profile data233can represent background information, such as the user's name, title, hiring date, company department, and other suitable information. The profile data233can also include a role of a user within an organization or enterprise. The profile data233can also include privileges or authorizations associated with the user, such as what applications or services to which the user has access as well as what actions or requests within the profile data233that should be sent to the user for review and/or approval.

For example, the profile data233can identify a group of users for whom a given user is a manager or supervisor and for whom certain requests should be sent to review. The requests can include vacation requests, requests to edit compensation, a working schedule, a change in employee or contractor status, a change to a role within an organization, or any other request that can be made by or on behalf of another user. In some examples, the enterprise service223can rely upon data from a user directory, such as Microsoft ActiveDirectory® in addition to information that can be stored in a user profile228to determine a relationship of a given user account to other users within an organization.

In some examples, a profile data233can include authentication tokens, credentials, password information, password reset data, certificate data, encryption key data, and other security or authentication-related data that is utilized by the user to access the enterprise service223or secure communications between a client device206or the user and the enterprise service223.

The task queue236can represent a list or queue of tasks that require action by a given user associated with a user account. In the context of this disclosure, tasks in a task queue236can represent requests that are made by or on behalf of other users that require review and approval or denial by a user. For example, a user can submit a request time off to the enterprise service223. The enterprise service223can identify that the request requires approval by one or more other users, such as the user's supervisors or managers. The enterprise service223can then create a task that is placed into a task queue236or one or more supervisors or managers of the requesting user. The enterprise service223can subsequently remove the task from the task queue236of the supervisors or managers once the request is either approved or denied.

Delegate data239represents information about delegates that are linked to a user account. A delegate of a user is authorized to act upon certain tasks in the task queue236of the user. A user can delegate authority to a delegate using user interfaces provided by the enterprise service223or the delegation service221. The delegating user can identify one or more actions or tasks that are delegated to the delegate. The delegating user can also identify temporal data241that specifies time restrictions associated with the delegation of an action or task to the delegate. For example, if a delegating user is scheduled to be on vacation during a time period, the delegating user can specify a delegate for a particular task during the time period. In some cases, the temporal data241can merely specify a beginning date but not ending date for the delegation of the task. In this scenario, delegation of the task to the delegate can have an indefinite time period.

Task data243represents information about a task that can delegated using the delegation service221. The task data243can include a particular action within the223. In one scenario, the action can be specified with an API call, a callback uniform resource locator (URL), or any other mechanism by which an action can be programmatically identified by the delegation service221. The task data243can also include one or more arguments or options to approve or deny a request associated with the action so that the delegation service221determine how to programmatically approve or deny the request. The task data243can further include information about how a task can be displayed to a user in a user interface so that the delegation service221can facilitate creating a user interface in which a delegate can review and act upon a delegated task.

The client device206may be configured to execute various applications such as a client application251and/or other applications. The client application251is executed to facilitate identifying data for storage in the user profile228(e.g., task queue236and delegate data239). Additionally, the client application251may be executed in a client device206, for example, to access network content served up by the computing environment203and/or other servers, thereby rendering a user interface253on the display248. To this end, the client application251may include a browser, a dedicated application, etc., and the user interface may comprise a network page, an application screen, etc. The client device206may be configured to execute applications beyond the client application251such as, for example, email applications, social networking applications, word processors, spreadsheets, and/or other applications.

A user can authenticate his or her identity with the enterprise service223using the client application251. The enterprise service223can provide content to the client application251, which can include user interfaces through which the user can review, approve, or deny requests in the task queue236of the user. Additionally, the enterprise service223can transmit notifications to the client device206of a user. Notifications can comprise mobile application notifications provided to the client application251, emails, text messages sent via messaging services, push notifications, or other notifications. Notifications can inform a user that tasks are awaiting to the user in their respective task queue236or that a request submitted by or on behalf of a user, such as a vacation request, has been approved or denied by another user with the appropriate authority to do so.

Next, a general description of the operation of the various components of the networked environment200is provided. To begin, a user of the enterprise service223can utilize client application251to access the enterprise service223to view tasks in a task queue236of the user. The user can be a managerial or supervisory user that accesses an HR system to view requests submitted by or on behalf of other users. The requests should be either approved or denied by the user. In one aspect, the user can review or approve these requests on their own. The user can utilize various user interface workflows provided by the enterprise service223to do so.

For example, the user can view a task section103of a user interface that shows a task list to identify tasks in the task queue236of the user. The user can select one or more tasks to review the details associated with a task. The user can then review and either approve or deny a request associated with a task.

In some examples, the user can also set up delegation of a task to one or more other users. A task can be delegated to a user or a user group. A user can be identified using a user identifier within the enterprise service223such as an email address, user ID, or other identifier. A user group can also be identified within the enterprise service223using a group email address, group identifier, multiple user identifiers, or other identifier that can be used to identify a user group.

The user can also specify temporal data241that can be associated with delegation of a task. The temporal data241specifies time restrictions associated with the delegation of an action or task to the delegate. For example, if a delegating user is scheduled to be on vacation during a time period, the delegating user can specify a delegate for a particular task during the time period. In some cases, the temporal data241can merely specify a beginning date but not ending date for the delegation of the task. In this scenario, delegation of the task to the delegate can have an indefinite time period. Specifying temporal data241can be considered optional if a user wishes to indefinitely delegate a task to another user.

Once delegation of a task is setup by a user, the delegation service221can add tasks associated with a request submitted by or on behalf of a requesting user to a task queue236of the delegating user as well as the delegates specified by the delegating user. As the task is acted upon by the delegating user or the delegates, the task can be removed from the task queue236of the delegates and the delegating user.

Additionally, the delegation service221or enterprise service223can generate notifications that can be sent to the delegates, as well as the delegating user, when a request submitted by or on behalf of a requesting user is received by the enterprise service223. Notifications can comprise mobile application notifications provided to the client application251, emails, text messages sent via messaging services, push notifications, or other notifications. Notifications can inform a user that tasks are awaiting to the user in their respective task queue236or that a request submitted by or on behalf of a user, such as a vacation request, has been approved or denied by another user with the appropriate authority to do so.

Turning now toFIG.3A, shown is a delegation user interface301in which a user can view, edit, and add delegates for various types of tasks. As shown in the delegation user interface301, a user can define another user as a delegate. The delegate user can be identified by a user identifier within the enterprise service223, such as an email address of the delegate user. The delegating user can further specify temporal restrictions associated with the delegate. The temporal restrictions can include a start date and an end date of delegation of a specified action. In some examples, the temporal data241can specify a particular time of the day in addition to the dates.

Finally, as shown inFIG.3A, the delegating user can identify one or more actions that can be delegated to the user. The actions can be selected by the user using the delegation user interface301generated by the enterprise service223or delegation service221. In the example shown, multiple actions can be delegated to the delegate by the delegating user. The actions can both be associated with the temporal data241specified by the delegating user. In one implementation, multiple entries for each delegated action can be created within the delegate data239. In another example, a single entry specifying multiple actions can be created within the delegate data239.

In some examples, delegations can be automatically created by obtaining an out of office status of a user. For example, if a user can designate an out of office status, the delegation service221can automatically select a delegate for one or more tasks associated with the user based upon a previous delegation of the one or more tasks. In this scenario, if a user has previously delegated a task to another user or user group, the delegation service221can automatically create a delegation of the task to the same other user or user group if the user is designated as out of office or unavailable. The out of office or unavailability status of the user can be detected from a user directory service or from another data point from the enterprise service223, such as in an HR system directory. In another scenario, the other user or user group to whom a task is delegated can be selected by navigating a user directory to locate a supervisor of the user or a subordinate of the user.

Moving on toFIG.3B, shown is a delegate user interface303that can be rendered on the client device206. The delegate user interface303can be generated by the delegation service221or enterprise service223to display delegations that have been given to a delegate. As shown in the delegate user interface303, the enterprise service223or delegation service221can indicate an identity of a delegating user who has delegated one or more tasks to the delegate. Additionally, the delegate user interface303can display temporal restrictions associated with each delegation. The temporal restrictions can include a start date and an end date of delegation of a specified action. Finally, as shown inFIG.3B, the delegate user interface303can display the one or more actions that have been delegated to the user. The actions can be selected by the user using the delegation user interface301ofFIG.3A.

Moving on toFIG.3C, shown is a delegate history user interface305that can be rendered on the client device206. The delegate history user interface305can be generated by the delegation service221or enterprise service223to display an activity history of a user as a delegate. As shown in the delegate history user interface305, the enterprise service223or delegation service221can display a history of previous approvals or denials made on behalf of a delegating user.

Moving on toFIG.3D, shown is a request result user interface307that can be rendered on the client device206. The request result user interface307can be generated by the delegation service221or enterprise service223to display a result of a request that was handled by a supervisory user or manager of a requesting user. In some examples, the request can be handled by a delegate of the supervisory user or manager. Accordingly, the request result user interface307can indicate that the request was handled by a delegate of the supervisory user or manager.

Referring next toFIG.4, shown is a flowchart that provides one example of the operation of a portion of the delegation service221according to various embodiments. It is understood that the flowchart ofFIG.4provides merely an example of the many different types of functional arrangements that may be employed to implement the operation of the portion of the delegation service221as described herein. As an alternative, the flowchart ofFIG.4may be viewed as depicting an example of elements of a method implemented in the computing environment203(FIG.2) according to one or more embodiments. The functionality shown inFIG.4can also be performed by the enterprise service223in some examples.

Beginning with box401, the delegation service221can identify a task associated with a user of the enterprise service223. The task can be associated with a request made by another user that requires approval or denial by the user. The task can be obtained from a task queue236of the user by the delegation service221. For example, the task can be associated with a request for vacation, a change in compensation, a change to a working schedule, or any other request that can be made using the enterprise service223.

At step404, the delegation service221can determine that the user account has delegated the task to one or more delegate users. The delegation service221can make this determination by consulting delegate data239associated with the user account. The delegate data239can indicate which tasks of a user have been delegated and to which other users of the enterprise service223. Accordingly, the delegation service221can determine whether the characteristics of the request associated with the task, including a request type, are consistent with the delegate data239associated with the user account.

At step407, the delegation service221can determine that a timestamp associated with the request linked to the task falls within a start date and end date specified in the temporal data241. The temporal data241specifies whether the task is delegated during a timestamp associated with the request.

At step410, the delegation service221can generate a notification that can be transmitted to the delegates identified by the delegate data239. The notification can inform the delegates that a delegated task requires action by the delegate. The notification can be sent via email, messaging, a mobile app notification, or through any suitable notification framework.

At step413, the delegation service221can authenticate a delegate user that has responded to the notification by attempting to take action on the request. The delegation service221can verify that the delegate user is authenticated with the delegation service221as well as verify that the delegate user is a delegate for the task.

At step416, the delegation service221can obtain an approval or denial of the request associated with the task. The approval or denial can be obtained through a user interface provided by the delegation service221to the delegate user.

At step419, once the delegate user approves or denies the request associated with the task, the delegation service221can generate a notification informing the subject user associated with the request. The notification can include an indication of whether the request was approved or denied. The notification can also include an indication of the identity of the delegate user that approved or denied the request. Thereafter, the process can proceed to completion.

A number of software components are stored in the memory and are executable by the processor. In this respect, the term “executable” means a program file that is in a form that can ultimately be run by the processor. Examples of executable programs may be, for example, a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of the memory and run by the processor, source code that may be expressed in proper format such as object code that is capable of being loaded into a random access portion of the memory and executed by the processor, or source code that may be interpreted by another executable program to generate instructions in a random access portion of the memory to be executed by the processor, etc. An executable program may be stored in any portion or component of the memory including, for example, random access memory (RAM), read-only memory (ROM), hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (CD) or digital versatile disc (DVD), floppy disk, magnetic tape, or other memory components.

Also, the processor may represent multiple processors and/or multiple processor cores and the memory may represent multiple memories that operate in parallel processing circuits, respectively. In such a case, the local interface may be an appropriate network that facilitates communication between any two of the multiple processors, between any processor and any of the memories, or between any two of the memories, etc. The local interface may comprise additional systems designed to coordinate this communication, including, for example, performing load balancing. The processor may be of electrical or of some other available construction.

Further, any logic or application described herein may be implemented and structured in a variety of ways. For example, one or more applications described may be implemented as modules or components of a single application. Further, one or more applications described herein may be executed in shared or separate computing devices or a combination thereof. For example, a plurality of the applications described herein may execute in the same computing device, or in multiple computing devices in the same computing environment203. Additionally, it is understood that terms such as “application,” “service,” “system,” “engine,” “module,” and so on may be interchangeable and are not intended to be limiting.

Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X; Y; Z; X and/or Y; X and/or Z; Y and/or Z; X, Y, and/or Z; etc.). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.