Patent Application
20170048285
This disclosure relates to managing content in a cloud-based service platform, and more particularly to techniques for managing flow-based user interactions with shared content in a highly collaborative cloud-based environment.
Cloud-based platforms offer the ability to securely share large volumes of content among trusted collaborators on a variety of user devices such as mobile phones, tablets, laptop computers, desktop computers, and/or other devices. For example, a large enterprise with thousands of users (e.g., employees) and many terabytes of content might use a cloud-based content storage platform to efficiently and securely facilitate content access to various individual users and/or collaborative groups of users. In such cases, a user can access a large volume of objects stored in the cloud-based platform from a user device that might store merely a small portion of that volume locally. Such access can enable multiple users (e.g., collaborators) to manage certain shared objects for various collaborative purposes (e.g., document review, document approval, content development, audience presentation, etc.).
In many cases, such collaboration might be constrained by a flow of interactions (e.g., flow-based interactions, flow-based events, workflow, etc.) with the shared content. For example, a certain flow of events (e.g., launch, alert, review, edit, approve, sign, etc.) might be designed to accompany one or more documents (e.g., sales contract, legal agreement, financial underwriting proposal, etc.) to facilitate certain work items (e.g., completion, approval, etc.) pertaining to the documents. In some cases, one enterprise might invite users from one or more other external enterprises to participate in selected work items comprising a given workflow. For example, an external user might be selected for a reviewing role, an auditing role, a signing role, and/or other roles. Implementation of such cross-enterprise workflow collaboration continues to increase as many of today's business models rely on extensive partnering (e.g., with contract partners, with external employees, with external service providers, etc.).
Unfortunately, legacy techniques for managing flow-based interactions with shared content can be limited at least as pertaining to efficiently facilitating such interactions over shared documents.
What is needed is a technique or techniques to improve over legacy and/or over other considered approaches. Some of the approaches described in this background section are approaches that could be pursued, but not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.
The present disclosure provides a detailed description of techniques used in systems, methods, and in computer program products for managing flow-based user interactions with shared content in a highly collaborative cloud-based environment, which techniques advance the relevant technologies to address technological issues with legacy approaches. More specifically, the present disclosure provides a detailed description of techniques used in systems, methods, and in computer program products for managing flow-based user interactions with shared content in a highly collaborative cloud-based environment. Certain embodiments are directed to technological solutions for implementing a metadata-based workflow attribute management platform to facilitate cross-enterprise, flow-based, shared content collaboration.
The disclosed embodiments modify and improve over legacy approaches. In particular, the herein-disclosed techniques provide technical solutions that address the technical problems attendant to flow-based collaboration on shared content across multiple enterprises. Such technical solutions serve to reduce the demand for computer memory, reduce the demand for computer processing power, reduce network bandwidth use, and reduce the demand for inter-component communication. Some embodiments disclosed herein use techniques to improve the functioning of multiple systems within the disclosed environments, and some embodiments advance peripheral technical fields as well. As one specific example, use of the disclosed techniques and devices within the shown environments as depicted in the figures provide advances in technical fields related to online collaboration and data storage.
In one aspect, a server in a cloud-based environment is interfaced with storage devices that store one or more stored objects accessible by two or more users. The stored objects comprise folders and files as well as other objects such as workflow objects that are associated with the folders or the files. The workflow objects comprise workflow metadata that describes a workflow as a set of workflow tasks to be carried out in a progression. Processing of a workflow task and/or carrying out a portion of the progression includes modification of shared content objects. The processing or modification events are detected through workflow events, which in turn cause one or more workflow responses to be generated. Workflow responses comprise updates to the workflow metadata to record progression through the workflow and/or workflow responses comprise updates to any one or more of the stored objects.
Further details of aspects, objectives, and advantages of the technological embodiments are described herein and in the following descriptions, drawings and claims.
The drawings described below are for illustration purposes only. The drawings are not intended to limit the scope of the present disclosure.
FIG. 16C1, FIG. 16C2, and FIG. 16C3 illustrate a workflow attribute update technique facilitated by a metadata-based workflow attribute management platform for cross-enterprise flow-based shared content collaboration, according to an embodiment.
Some embodiments of the present disclosure address the problem of flow-based collaboration on shared content across multiple enterprises and some embodiments are directed to approaches for implementing a metadata-based workflow attribute management platform to facilitate cross-enterprise, flow-based, shared content collaboration. The accompanying figures and discussions herein present example environments, systems, methods, and computer program products for managing flow-based user interactions with shared content in a highly collaborative cloud-based environment.
Disclosed herein are techniques that implement a metadata-based workflow attribute management platform to facilitate cross-enterprise, flow-based, shared content collaboration. Specifically, in some embodiments, various workflows comprising work items are defined at least in part by metadata that is stored in a cloud-based storage system, which workflows can mark progress by performing various updates to the metadata. In some embodiments, the metadata can characterize work item attributes pertaining to associated content objects, participants, participant experiences, flow logic, flow status, and/or other work item characteristics and therefore trigger other events. In certain embodiments, events invoked by the workflow participants can be matched to a set of workflow rules to determine one or more workflow responses such as metadata updates, shared content updates, participant alerts, the use of a specific application, customized collaboration visualization, and/or other responses. In some embodiments, participants external to a given enterprise can be invited to collaborate on a workflow defined by the enterprise. Some approaches deliver custom code (e.g., user interface, workflow logic, etc.) and content storage capabilities (e.g., dedicated storage facilities, custom provisioning, etc.) to provide a collaborative workflow solution for a given set of customized workflow tasks that are associated with respective shared documents.
Various embodiments are described herein with reference to the figures. It should be noted that the figures are not necessarily drawn to scale and that elements of similar structures or functions are sometimes represented by like reference characters throughout the figures. It should also be noted that the figures are only intended to facilitate the description of the disclosed embodiments—they are not representative of an exhaustive treatment of all possible embodiments, and they are not intended to impute any limitation as to the scope of the claims. In addition, an illustrated embodiment need not portray all aspects or advantages of usage in any particular environment.
An aspect or an advantage described in conjunction with a particular embodiment is not necessarily limited to that embodiment and can be practiced in any other embodiments even if not so illustrated. Also, references throughout this specification to “some embodiments” or “other embodiments” refers to a particular feature, structure, material or characteristic described in connection with the embodiments as being included in at least one embodiment. Thus, the appearance of the phrases “in some embodiments” or “in other embodiments” in various places throughout this specification are not necessarily referring to the same embodiment or embodiments.
Some of the terms used in this description are defined below for easy reference. The presented terms and their respective definitions are not rigidly restricted to these definitions—a term may be further defined by the term's use within this disclosure. The term “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application and the appended claims, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or is clear from the context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A, X employs B, or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. As used herein, at least one of A or B means at least one of A, or at least one of B, or at least one of both A and B. In other words, this phrase is disjunctive. The articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or is clear from the context to be directed to a singular form.
Reference is now made in detail to certain embodiments. The disclosed embodiments are not intended to be limiting of the claims.
The client devices 102 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, or cellular connections with another device, a server and/or other systems such as host server 100 and/or notification server 150. Client devices 102 will typically include a display and/or other output functionalities to present information and data exchanged between the client devices 102 and/or the host server 100 and/or notification server 150.
For example, the client devices 102 can include mobile, hand held, portable devices, or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, and/or portable devices including a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Treo, a handheld tablet (e.g., an iPad, a Galaxy, Xoom Tablet, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console, an iPhone, and/or any other portable, mobile, hand held devices, etc. running on any platform or any operating system (e.g., Mac-based OS (OS X, iOS, etc.), Windows-based OS (Windows Mobile, Windows 7, etc.), Android, Blackberry OS, Embedded Linux platforms, Palm OS, or Symbian platform. In one embodiment, the client devices 102, host server 100, and/or app servers are coupled via a network 106. In some embodiments, the devices 102 and host server 100 may be directly connected to one another.
The input mechanism on client devices 102 can include a touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, a motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.); a light sensor, capacitance sensor, resistance sensor, temperature sensor, or proximity sensor; a piezoelectric device; a device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer); or a combination or variation of the above.
Signals received or detected indicating user activity at client devices 102 through one or more of the above input mechanism, or others, can be used in the disclosed technology by various users or collaborators (e.g., collaborators 175) for accessing, through network 106, a web-based collaboration environment or online collaboration platform (e.g., hosted by the host server 100).
The collaboration platform or environment hosts workspaces with work items that one or more users can access (e.g., view, edit, update, revise, comment, download, preview, tag, or otherwise manipulate, etc.). A work item can generally include any type of digital or electronic content that can be viewed or accessed via an electronic device (e.g., devices 102). The digital content can include .pdf files, .doc or .docx files, slides (e.g., Powerpoint slides), images, audio files, multimedia content, web pages, blogs, etc. A workspace can generally refer to any grouping of a set of digital content in the collaboration platform. The grouping can be created, identified, or specified by a user or through other means. This user may be a creator user or administrative user, for example.
In general, a workspace can be associated with a set of users or collaborators 175 (e.g., creator user 108a or an administrative user 108b) which have access to the content included therein. The levels of access (e.g., based on permissions or rules) of each user or collaborator to access the content in a given workspace may be the same or may vary among the users. Each user may have their own set of access rights to every piece of content in the workspace, or each user may have different access rights to different pieces of content. Access rights may be specified by a user associated with a workspace and/or a user who created/uploaded a particular piece of content to the workspace, or any other designated user or collaborator.
In general, the collaboration platform allows multiple users or collaborators to access or collaborate efforts on work items such that each user can see, remotely, edits, revisions, comments, or annotations being made to specific work items through their own user devices. For example, a user can upload a document to a workspace for other users to access (e.g., for viewing, editing, commenting, signing-off, or otherwise manipulating). The user can login to the online platform and upload the document (or any other type of work item) to an existing workspace or to a new workspace. The document can be shared with existing users or collaborators in a workspace.
A diagrammatic illustration of the online collaboration environment and the relationships between workspaces and users/collaborators are illustrated with further reference to the example of
In one embodiment, client devices 102 communicate with the host server 100 and its repository 130 and/or notification server 150 over network 106. In general, network 106, over which the client devices 102, the host server 100, and/or the notification server 150 communicate may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, open system interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.
The network 106 can be any collection of distinct networks operating wholly or partially in conjunction with each other so as to provide connectivity to the client devices 102 and the host server 100, and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 102 can be achieved by an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol such as a secure sockets layer (SSL) or a transport layer security (TLS) protocol.
In addition, communications can be achieved via one or more networks such as, but are not limited to, one or more of WiMax, a local area network (LAN), wireless local area network (WLAN), a personal area network (PAN), a campus area network (CAN), a metropolitan area network (MAN), a wide area network (WAN), and/or a wireless wide area network (WWAN) enabled with technologies such as, by way of example, global system for mobile communications (GSM), personal communications service (PCS), digital advanced mobile phone service (D-Amps), Bluetooth, Wi-Fi, fixed wireless data, 2G, 2.5G, 3G, 4G, IMT-advanced, pre-4G, 3G LTE, 3GPP LTE, LTE advanced, mobile WiMax, WiMax 2, wirelessMAN-advanced networks, enhanced data rates for GSM evolution (EDGE), general packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1×RTT, EV-DO, and messaging protocols such as TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.
A diagrammatic illustration of the cloud-based environment (e.g., collaboration environment) and the relationships between workspaces and users/collaborators are illustrated with further reference to the example of
In one embodiment, actions performed on work items or other activities that occur in a workspace can be detected in real time or in near real-time. The host server can generate notifications or notification events for one or more of the plurality of activities and select one or more recipients for each notification. Various mechanisms or external messaging applications can then be used to notify users or collaborators, including notification through the web interface to access the collaboration platform, via email, and/or SMS, for example.
In one embodiment, the host server can comprise a distributed system including both front-end and back-end components (systems). Although not shown, the host server can include an action log, an event dispatcher, one or more processors, one or more databases, and/or one or more real-time clients. Together these components are generally referred to herein as an “action log framework” (ALF). Components of the ALF may reside in the front-end systems, the back-end systems, and/or a combination thereof.
In one embodiment, the event dispatcher (also referred to as the event manager dispatcher, see e.g.,
The web-based platform for collaborating on projects or jointly working on documents can be used by individual users and shared among collaborators. In addition, the collaboration platform can be deployed in an organized setting including, but not limited to, a company (e.g., an enterprise setting), a department in a company, an academic institution, a department in an academic institution, a class or course setting, or any other type of organization or organized setting.
When deployed in an organizational setting, multiple workspaces (e.g., workspace A-N) may be created to support different projects or a variety of work flows. Each workspace may have its own associate work items. For example, workspace A 205 may be associated with work items 215, workspace B 225 may be associated with work items 235, and workspace N may be associated with work items 255. The work items 215, 235, and 255 may be unique to each workspace, but need not be. For example, a particular word document may be associated with only one workspace (e.g., workspace A 205) or it may be associated with multiple workspaces (e.g., workspace A 205 and workspace B 225, etc.).
In general, each workspace has a set of users or collaborators associated with it. For example, workspace A 205 is associated with multiple users or collaborators 206. In some instances, workspaces deployed in an enterprise may be department specific. For example, workspace B may be associated with department 210 and some users shown as example user A 208, and workspace N 245 may be associated with departments 212 and 216 and a user shown as example user B 214.
Each user associated with a workspace may generally access the work items associated with the workspace. The level of access may depend on permissions associated with the specific workspace and/or with a specific work item. Permissions may be set for the workspace or set individually on a per work item basis. For example, the creator of a workspace (e.g., one of user A 208 who creates workspace B) may set one permission setting applicable to all work items 235 for other associated users and/or users associated with the affiliate (e.g., department 210). Creator user A 208 may also set different permission settings for each work item, which may be the same for different users, or varying for different users.
In each workspace A, B, . . . , N, when an action is performed on a work item by a given user or any other activity is detected in the workspace, other users in the same workspace may be notified (e.g., in real time or in near real-time, or not in real time). Activities which trigger real time notifications can include, by way of example but not limitation, adding, deleting, and/or modifying collaborators in the workspace; uploading, downloading, adding, and/or deleting a work item in the workspace; and creating a discussion topic in the workspace.
In some embodiments, items or content (content items) downloaded or edited in accordance with the techniques described in the present disclosure can cause notifications to be generated. Such notifications can be sent to relevant users to notify them of actions surrounding a download, an edit, a change, a modification, a new file, a conflicting version, or an upload of an edited or modified file. Additionally, as discussed above, actions performed on the content items can be maintained by an ALF system.
In one embodiment, in a user interface of the web-based collaboration platform where notifications are presented, users can, via the user interface, create action items (e.g., tasks) and delegate the action items to other users including collaborators pertaining to a work item 215, for example. The collaborators 206 may be in the same workspace A 205 or the user may include a newly invited collaborator. Similarly, in the same user interface where discussion topics can be created in a workspace (e.g., workspace A, B or N, etc.), actionable events on work items can be created and/or delegated/assigned to other users such as collaborators of a given workspace or other users. Through the same user interface, task status and updates from multiple users or collaborators can be indicated and reflected. In some instances, the users can perform the tasks (e.g., review or approve or reject, etc.) via the same user interface.
Each of users 316, 318, and 320 may individually use multiple different devices to access and/or manipulate work items 324 (e.g., content items) in the workspace 302 with which they are associated with. For example, users 316, 318, 320 may be collaborators on a project to which work items 324 are relevant. Since the work items 324 are hosted by the collaboration environment (e.g., a cloud-based environment), each user may access the work items 324 at any time and from any physical location using any device (e.g., including devices they own or any shared/public/loaner devices).
Work items to be edited or viewed may be accessed from the workspace 302 in accordance with the platform and/or application independent mechanisms. Users may also be notified of access-, edit-, modification-, and/or upload-related actions performed on work items 324 by other users or any other types of activities detected in workspace 302. For example, if user 316 modifies a document, one or both of the other collaborators (e.g., user 318 and user 320) can be notified of the modification in real time, or near real-time, or not in real time. The notifications can be sent through any or all or some of the devices associated with a given user, in various formats including one or more of email, SMS, or via a pop-up window in a user interface which the user uses to access the collaboration platform. In the event of multiple notifications, each notification may be depicted preferentially (e.g., ordering in the user interface) based on user preferences and/or relevance to the user (e.g., implicit or explicit).
For example, a notification of a download-, access-, read-, write-, edit-, or upload-related activities may be presented in a feed stream among other notifications through a user interface on the user device according to relevancy to the user determined based on current or recent activity of the user in the web-based collaboration environment.
In one embodiment, a notification feed stream includes updates when an invited user accepts an invitation and/or successfully creates a new account through receipt of an invitation from an existing user. The invited user, upon creation of the new account, receives the account having enhanced features. The new user can automatically be connected to the existing user who sent the invitation. The system can also automatically prompt both users to query who they wish to be collaborators in a common workspace.
Work items hosted by a collaboration environment (e.g., a cloud-based collaboration environment) can be accessed by users (e.g., user 316, user 318, and user 320) via multiple different devices (e.g., devices 304-314) for viewing, editing, processing or performing other manipulations on work items. The devices can include applications for accessing a server hosting a cloud-based platform or service or other back-end web service (hereinafter “cloud-based collaboration platform application”) and applications for viewing, editing, processing, or performing other manipulations on work items. The communication between such applications are generally facilitated by a communication mechanism of the OS. For example, in Android OS, the communication mechanism is based on “Intents”. As previously described, the underlying communication mechanism is generally not secure, and any data passed between applications is visible to all other applications on a device.
In one embodiment, the cloud-based collaboration platform 405 can include the host server 100 and/or the notification server 150 of
Additionally, in some embodiments, an administrator's system (e.g., client system 410) can be configured to bypass the front-end systems in order to directly submit a job, determine the status of a job, kill a job, etc. via a web interface or application program interface built into the event-based automation engine 430. In some embodiments, clients, users and/or administrators can access the metadata service engine 450 in order to select, configure, and/or generate templates or provide input for metadata searching.
In one embodiment, the front-end system(s) 420 can include various web applications and/or web servers. Additionally, in some embodiments, the front-end system(s) 420 can provide ALF events to the event-based automation engine 430. As discussed in greater detail with reference to
In one embodiment, the rules-based engine can be configured to generate and manage user-defined (or specified) metadata rules and apply the metadata rules to metadata events generated by the metadata service engine 450. As described in greater detail with reference to
Additional or fewer components/modules/engines can be included in the metadata service engine 500 and/or in each illustrated component/module/engine. Further, although illustrated as included as part of the metadata service engine 500, the components/modules/engines and/or the template databases 525 can be physically and/or functionally distributed.
One embodiment of the metadata service engine 500 includes the administrator/user interface 515. The administrator/user interface 515 can comprise any interface configured to facilitate receiving and processing of templating inputs for selection, configuration, and/or generation of metadata templates. For example, the administrator/user interface 515 can include a network interface having a networking module that facilitates the metadata service engine 500 to mediate data in a network with an entity that is external to the metadata service engine 500 through any known and/or convenient communications protocol supported by the host and the external entity. The network interface can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
Additionally, the administrator/user interface 515 can comprise any interface configured to facilitate receiving of metadata search input. As discussed below, the administrator/user interface 515 interacts with the metadata search engine 560 to provide users and/or administrators the ability to search by metadata.
One embodiment of the metadata service engine 500 includes the templating engine 520. The templating engine 520 can include customizable and/or pre-built metadata templates which can be used to automatically apply a metadata framework (e.g., particular fields) to files (or work items) based on, for example, the upload or placement of a particular file in a particular folder, selection of those files by a user or administrator, and/or in other manners discussed herein or known in the art. As discussed above, the templating engine 520 includes a template selection engine 522, template generation engine 524, and a template configuration engine 526. The template selection engine 522 is configured to select one or more preconfigured templates for application of those templates to work items in the cloud-based collaborative environment. The template generation engine 524 and a template configuration engine 526 are configured to generate and configure metadata templates responsive to the templating input. One or more template database(s) 525 persistently stores the templates in the cloud-based collaborative environment.
One embodiment of the metadata service engine 500 includes the metadata event generation engine 530, the metadata change detection engine 540, and the metadata monitoring engine 550. The metadata monitoring engine 550 monitors actions, events, jobs, job requests, etc. to identify changes to metadata occurring to work items within the collaborative cloud-based environment. The metadata change detection engine 540 detects these changes to the metadata and the metadata event generation engine 530 responsively generates the metadata events.
One embodiment of the metadata service engine 500 includes the metadata search engine 560. The metadata search engine 560 is configured to facilitate searching of the metadata in the collaborative cloud-based environment. In some embodiments, the metadata search engine 560 can index the metadata. For example, the metadata search engine 560 collects, parses, and stores data to facilitate fast and accurate metadata information retrieval.
One embodiment of the metadata service engine 500 includes the metadata rules interface 570. The metadata rules interface 570 is configured to interact with the rule manager to, for example, automatically provide rules to be generated based on configurations/customizations of metadata templates.
The rule manager 620 can include any system and/or service that is configured to receive incoming ALF events and/or metadata events and apply rules (or metadata rules) to the events to automatically generate corresponding job requests and send the job requests to the jobs manager 640. The administrator interface 610 allows administrative users to generate (or set) rules or metadata rules which are then stored, by the rule manager 620, in the rules database 625. An example a rule manager is discussed in greater detail with reference to
The jobs manager 640 can, among other functions, receive job requests from the rule manager, generate jobs corresponding to job requests, determine relevant queues for jobs, route jobs to relevant queues for performance by workers, and track and/or otherwise monitor the status of each of the jobs. In addition to supporting content workflow, the jobs manager is also intended to be a general-purpose job system that can provide asynchronous job execution for other services. An example jobs manager is discussed in greater detail with reference to
The rule manager 700 can include an administrator interface 705, a rule generation/definition engine 710, an action/event interface 715, a metadata event interface 716, a parsing engine 720, a rule matching/selection engine 730, and a job request generation engine 740. The parsing engine 720 can include an event type parser 722, an enterprise identifier (ID) parser 724, and a metadata identification module 726. As shown in the example of
Additional or fewer components/modules/engines can be included in the rule manager 700 and/or in each illustrated component/module/engine. Further, although illustrated as included as part of the rule manager 700, the components/modules/engines and/or the rules database 750 and/or the metadata rules database 755 can be physically and/or functionally distributed.
One embodiment of the rule manager 700 includes the administrator interface 705. The administrator interface 705 can comprise any interface configured to facilitate setting and/or generation of the user-defined rules by an administrator. For example, the administrator interface 705 can include a network interface having a networking module that facilitates the rule manager 700 to mediate data in a network with an entity that is external to the rule manager 700, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
One embodiment of the rule manager 700 includes the rule generation/definition engine 710. The rule generation/definition engine 710 facilitates rule generation/definition by users or administrators. For example, users can define rules in a rule descriptive language (RDL) that can be automatically triggered and executed by the rule manager. The users or administrators can also define metadata rules in a similar matter. Alternatively or additionally, metadata rules can be automatically generated and input into the system based on user-generated or pre-existing metadata templates defined by the metadata service engine 500.
Each rule can include one or more conditions that can be determined by the user and/or automatically by the system. Each condition is associated with a job. In operation, when a condition is evaluated to be true, the associated job is triggered and/or otherwise generated. Metadata rules can be defined in a similar fashion. Alternatively or additionally, metadata rules can be defined based on keys of key-value pairs. In some embodiments, threshold or defined values for the metadata key-value pairs can be set that trigger the rule. For example, if the metadata template defines a contract, then one metadata attribute may be the value of the contract. A rule can be set that triggers a particular action or job in the event that the value of the contract exceeds a particular preset value. For instance, one or more notifications may be sent to particular individuals for review. Similarly, a metadata attribute of a contract template could include a status attribute that causes a particular action or job to be performed when the value of the key-value pair changes from ‘PENDING’ to ‘APPROVED’. In this manner, metadata or changes to metadata can trigger job requests (e.g., events or actions).
One embodiment of the rule manager 700 includes the action/event interface 715. The action/event interface 715 can receive events including ALF events. For example, the action/event interface 715 can receive events from an action log dispatcher (ALD) (also referred to as a dispatcher or an event manager dispatcher herein). In one embodiment, the ALD accumulates and distributes actions taken and logged by collaborators in the collaboration environment. The distributed events can be, for example, ALF events that indicate the user actions taken on content items in the web applications. The ALD can accumulate and distribute and/or otherwise provide sets of ALF events (e.g., multiple events) to the rule manager simultaneously. For example, in one embodiment, the ALF events can be distributed via an action such as, for example, action log 605 of
One embodiment of the rule manager 700 includes the metadata event interface 716. The metadata event interface 716 can receive metadata events. For example, the metadata event interface 716 can receive metadata events from a metadata service engine such as, for example, metadata service engine 500 of
One embodiment of the rule manager 700 includes the parsing engine 720. The parsing engine 720 parses each of the events to identify event criteria associated with the event such as, for example, an action type and/or an enterprise identifier (ID). The parsing engine 720 can also parse and/or otherwise process the metadata events and identify the relevant information such as, for example, the associated key-value pair.
The example rule manager 700 of
One embodiment of the rule manager 700 includes the rule matching/selection engine 730. The rule matching/selection engine 730 is configured to access predefined rules from the rules database 750, and scan the predefined rules to select predefined rules that match particular event criteria. For example, the rule manger 700 can utilize filters (or criteria) to select or match ALF events with rules. Example filters include, but are not limited to, enterprise_id, all_enterprises, all_users, and event type. Additionally, the rule matching/selection engine 730 can parse the metadata rules to select predefined rules that match a particular key and/or value of a key-value pair associated with a particular metadata event.
In one embodiment, the rule matching/selection engine 730 includes a rule parser 732, a metadata rules parser 734, and a classification module 736. The rule parser 732 is configured to parse the rules to identify one or more conditions associated with the rule and the corresponding job descriptions (also referred to herein as job templates) that are triggered if the condition occurs. The job descriptions are embedded in the rules and define the job to be performed. For example, each job indicates a process or type of work that is to be performed by one of the workers (e.g., distributed processing machines).
The metadata rule parser 734 is configured to parse the metadata rules to identify one or more keys and or values that match the key-value pair associated with the metadata event. For example, the metadata rule parser 734 can determine a predefined metadata rule that matches the key of the key-value pair.
One embodiment of the rule manager 700 includes the job request generation engine 740. The job request generation engine 740 is configured to generate one or more job requests for each rule. For example, in one embodiment, the job request generation engine 740 generates a job request based on each job description (or job template) corresponding to each rule condition. As discussed above, the jobs indicate work to be performed by workers (e.g., workers 650 of
The job manager 800 can include an administrator interface 805, a jobs interface 810, a leader election engine 815, an error detection engine 820, a status engine 825, a retry engine 830, a replication engine 840, a job scheduler 850, and various queues 860. As shown in the example of
One embodiment of the job manager 800 includes the administrator interface 805. The administrator interface 805 can comprise any interface (e.g., a web interface) configured to facilitate direct administrator access for job submission, job status, or killing of jobs. In one embodiment, the administrator interface 805 can include a network interface having a networking module that facilitates the job manager 800 to mediate data in a network with an entity that is external to the job manager 800, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
One embodiment of the job manager 800 includes the jobs interface 810. The jobs interface 810 can receive jobs including batched jobs. As discussed above, the jobs indicate work to be performed by workers (e.g., workers 650 of
One embodiment of the job manager 800 includes the jobs interface 810 to leader election engine 815. As described herein, multiple instances of the job manager can be utilized in a distributed environment to prevent data loss and facilitate scalability. The leader election engine 815 can be used to guarantee that only one instance of the job manager 800 is performing operations so that the operations are not duplicated. For example, in one embodiment, the leader election engine 815 is utilized to ensure that only one service in each cluster is retrying and/or replicating jobs.
One embodiment of the job manager 800 includes the error detection engine 820. For example, the error detection engine 820 can provide infinite loop detection. That is, in some cases, users/admins can generate rules that create an infinite loop such as, for example:
Rule 1: Condition/Job
Rule 2: Condition/Job
In one embodiment, the error detection engine 820 prevents such scenarios by injecting a unique token into the worker-initiated API requests. The token flows through the API and web app and back into the ALF stream with the associated event. The rule manager can then pass the token along to the job manager where the job manager prevents jobs from being queued if the token had been seen too many times. Otherwise, the token would be added to the new job and the workers would need to reuse the token when executing the job.
One embodiment of the job manager 800 includes the status engine 825. The status engine 825 can track and/or otherwise monitor the status of jobs submitted to the queues. The status engine 825 ensures that jobs are executed. In one embodiment, jobs and status updates (started, completed, failed) are persisted in a local database (e.g., the local HBase cluster). The status engine 825 also responds to status queries received at the administrator interface (or web interface).
In one embodiment, status or progress cache is maintained by the job manager. The status or progress cache can provide status and/or progress updates (i.e., 10%, 20%, etc.) of jobs completed to interested clients (administrators). Additionally, as discussed above, the job manager supports an API or administer interface for receiving these updates from the workers and then providing the details to clients via a job status query response. In one embodiment, because of the temporary nature of the updates, rather than storing the updates in HBase, the job manager will store them in memcache.
One embodiment of the job manager 800 includes the replication engine 840. The replication engine 840 can save or store the jobs to first database 842 and second database 844. Each database can comprise an HBase at geographically remote data centers. As described in more detail below, once the job is stored in multiple data centers, the job manager 800 can then respond to the rule manager (e.g., to acknowledge receipt of the jobs).
One embodiment of the job manager 800 includes the job scheduler 850. The job scheduler 850 can generate jobs based on the job requests and determine the appropriate queues 860 for the jobs, then distribute the jobs to the appropriate queues. In one embodiment, the appropriate queues 860 are selected based on the type of job. That is, particular queues can be designed for and serviced by workers that are specifically configured to perform those jobs. By way of example and not limitation, the system can designate dedicated queues for the following jobs: preview jobs, video conversion jobs, text extraction jobs, virus scan jobs, thumbnail creation jobs, data loss prevention (DLP) jobs, etc. Alternatively or additionally, one or more general-purpose queues could be utilized by one or more general-purpose workers (i.e., workers configured to perform a variety of different types of jobs).
To begin, in process 910, the metadata service engine monitors changes in metadata. For example, the metadata service engine can monitor job requests, changed work items, events, actions, etc. in order to identify changes or potential changes to metadata within the collaborative cloud-based environment. In process 912, the metadata service engine determines if a change in the metadata is detected. The change in the metadata can be, for example a change in a metadata key-value pair.
If a change is detected in process 912, the metadata service engine optionally, in process 914, determines if the metadata is associated with a predetermined metadata template. For example, in some instances, the metadata service engine only monitors a subset of the metadata (e.g., metadata for which rules have been established and/or metadata associated with a defined metadata template). In process 916, the metadata service engine generates the metadata event. In some embodiments, the metadata event can be optionally generated based on whether the metadata or changed metadata is associated with a defined metadata template.
To begin, in process 1010, the rule manager receives a metadata event and, in process 1012, processes the metadata event to identify or capture an associated key-value pair. As discussed above, the metadata event can be an event that is initiated by a metadata service engine that is responsive to monitored changes in metadata pertaining to content items in the collaborative cloud-based environment.
In process 1014, the rule manager scans the metadata rules based on the metadata key and, at decision process 1016, determines if the metadata key matches a metadata rule. In one embodiment, the rule manager can also scan the metadata rules for other conditions or values that are compared to the value of the key-value pair to make a determination about whether a metadata rule is triggered or if a metadata event matches a rule.
In process 1018, the rule manager selects a metadata rule that matches the metadata event, if one exists. Next, in process 1020, the rule manager identifies a job description associated with the selected metadata rule. For example, the job description can indicate the type of job that is to be performed when the rule is triggered. Lastly, in process 1022, the rule manager generates a new job request based on the job description. As discussed herein, the rule manager distributes the batched jobs to the job manager. In some embodiments, load balancers may be used to distribute events to multiple instances of the rule manager and jobs to multiple instances of the job manager, respectively. Additionally, the instances referred to herein are referring to additional distributed hardware resources.
To begin, in process 1110, the rule manager receives an event and, in process 1112, parses the event to identify event criteria. As discussed above, the event can be an ALF event that is initiated by a web application (e.g., front-end system) responsive to an action taken on a content item in the collaborative cloud-based environment.
In process 1112, the rule manager parses the event to identify event criteria. For example, the event criteria can include an action type (i.e., type of action performed that triggered the event, e.g., upload) or an enterprise identifier.
In process 1114, the rule manager scans the rules based on the event criteria and, at decision process 1116, determines if the event matches a rule. In one embodiment, the rule manager can also scan the rules for conditions that are compared to the event criteria to determine if an event matches a rule. In process 1118, the rule manager selects a rule that matches the event criteria, if one exists. Next, in process 1120, the rule manager identifies a job description associated with the selected rule. For example, the job description can indicate the type of job that is to be performed.
In process 1122, the rule manager generates a new job request based on the job description and, in process 1124, waits for additional new jobs to be generated to batch multiple job requests. Lastly, in process 1126, the rule manager distributes the batched jobs to the job manager. As discussed below with reference to
To begin, in process 1210, the rule manager receives information from an administrator for defining a new rule. In one embodiment, the information includes a user defined condition and a corresponding job definition. For example, the condition “on file upload into folder A” can be received from the administrator with a corresponding job “move the file into folder B.” As discussed above, the user-defined (or predefined) rules can be applied to incoming events (e.g., ALF events) to automatically generate jobs to be performed by workers in a computing platform.
In one embodiment, the rule manager can extract various additional conditions and/or job descriptions based on, for example, the type of condition. This is referred to herein as a complex rule. For example, if the condition “on file upload” is received with the job description “scan file,” then the system can extract various jobs to perform in sequence: extract text, scan file for keyword, and quarantine file if keyword found.
In process 1212, the rule manager generates the rule by associating condition(s) with the corresponding job description(s) and, lastly, in process 1214, the rule is stored in a rules database.
To begin, in process 1310, the rule manager receives information from an administrator for defining a new metadata rule. In one embodiment, the information identifies an associated template and/or a key value for metadata. Additionally, the information can also include a threshold value for the key that causes the rule to be triggered. For example, if the metadata template defines a contract, then one metadata attribute or key may be the value of the contract. A rule can be set that triggers a particular action or job in the event that the value of the contract exceeds a particular preset value. For instance, one or more notifications may be sent to particular individuals for review. Similarly, a metadata attribute of a contract template could include a status attribute that causes a particular action or job to be performed when the value of the key-value pair change from ‘PENDING’ to ‘APPROVED’. In this manner, metadata or changes to metadata can trigger job requests (e.g., events or actions).
In process 1312, the rule manager generates the metadata rule by associating the metadata key with additional information (e.g., template and/or threshold value) and with one or more corresponding job description(s) and, lastly, in process 1314, the metadata rule is stored in a rules database.
To begin, in process 1410, the job manager receives a job initiated by the rule manager and, in process 1412, stores the job persistently in one or more data centers. In one embodiment, the job manager stores the job in multiple remote data centers at least one of which is geographically remote.
In process 1413, the job manager generates jobs responsive to the job requests and, in process 1414, the job manager determines an appropriate queue for the job. In one embodiment, the appropriate queues are selected based on the type of job. That is, particular queues can be designed for and serviced by workers that are specifically configured to perform those jobs. By way of example and not limitation, the system can designate dedicated queues for the following jobs: preview jobs, video conversion jobs, text extraction jobs, virus scan jobs, thumbnail creation jobs, data loss prevention (DLP) jobs, etc. Alternatively or additionally, one or more general-purpose queues could be utilized by one or more general-purpose workers (i.e., workers configured to perform a variety of different types of jobs).
In process 1416, a job manager distributes the job to the appropriate queue and, lastly, in process 1418, the job manager maintains the current status of the job. As described in more detail with reference to
The rule manager is responsible for translating events it receives from the action log dispatcher (ALD) (or event manager dispatcher (EMD)) into job requests depending on a set of customer specified rules. For example, if a file is uploaded to a certain folder, a task could be automatically created and assigned to a user for that file. More specifically, the rule manager generates jobs for content workflow based on the ALF stream. Importantly, incoming events are not acknowledged until jobs are persisted to HBase and, thus, the rule matching and job generation step has low latency. In addition, the rules are user-defined and, thus, any number of rules can be defined. The rule manager can scale (i.e., with additional instances) with the increasing number of rules.
In one embodiment, events are distributed from an ALF system via the ALD service. The ALD can send a request containing a set of events to the rule manager. Each event can be described as an action log. Thus, for each action log, the rule manager can parse out the action_type and enterprise_id and then scan for rules matching the action_type and enterprise_id against its local cache.
In one embodiment, the rules are defined using a rule description language (RDL) which can be parsed by the rule manager to extract the filters and job template. For example, rules can have an optional set of simple conditional filters such as, for example, “=” by which to filter out jobs to avoid the need to send no-op jobs to the job manager. The filters work by comparing data extracted from the action log against predefined static values. For job creation, rules can include a template job description that the rule manager can populate using data from the action log. The filled out template is essentially a serialized job body.
Once the events in the current requests from the ALD are evaluated, the rule manager can forward the generated jobs to the job manager. The rule manager will receive an acknowledgement from the job manager and send an acknowledgement back to the ALD. If no jobs are created from a request from the ALD, then the rule manager will simply acknowledge the request immediately.
The job manager is a component of content workflow that receives job requests from the rule manager. In addition to supporting content workflow, the job manager is also intended to be a general-purpose job system that can provide asynchronous job execution for other services. The job manager is generally responsible for creating new jobs and monitoring the status of jobs. The job manager essentially ensures that a job will be executed. As discussed above, new jobs and status updates (e.g., started, completed, failed) can be persisted to the local HBase cluster.
In one embodiment, when the job manager receives a new job request, it first persistently stores the job to HBase. Once the job has been saved to HBase, the job manager will acknowledge the job request and thereby guarantee the execution of the job. After the job manager has acknowledged the job request, the job manager will then queue the job in RabbitMQ for execution. Workers actively pick up jobs off the queue and execute these jobs.
In one embodiment, prior to queuing the job, the job manager can inject callbacks into the job description to be notified by a worker before it begins executing a job, after it finishes executing a job, and/or if an error occurs during execution. To handle temporary errors, the job manager uses an actor to periodically re-queue jobs that have not been started or completed after a configurable amount of time. The job manager also has an actor that is dedicated to replicating to the remote HBase cluster on a configurable interval.
As illustrated in the example of
In one embodiment, each request to the rule manager can contain a batch of requests. The jobs (job requests) sent from the rule manager to the job manager can also be batched. In some embodiments, a single request from the rule manager will contain all the jobs that should be generated for a request from the action log dispatcher (ALD). A single event from the dispatcher can thus spawn a group of jobs (e.g., FILE UPLOAD) and can trigger virus scanning and text extraction jobs. The job manager responds to a request by indicating, for each group of jobs, whether the entire group of jobs is guaranteed to be run. When an incoming job request is written to HBase, it is at that point “guaranteed” by the job manager. This guarantee will be reflected in the response. Additionally, the web interface scales horizontally by deploying additional servers with the job manager service.
In one embodiment, rule updates are performed through the rule manager web application. For example, the web application can perform CRUD operations on rules using the DB_Model framework. For the rule manager to keep its internal cache (or database) of rules in sync with the web application rule changes, the web application can insert an event into the ALF stream for every change to the rules. The rule manager processes all ALF events at least once, and thus, the rule manager identifies the rule update event and can responsively update the version in Zookeeper to notify all subscribing rule manager instances to update their local caches (rule databases).
In one embodiment, the rule manager utilizes RDL to describe rules. The RDL includes syntax for facilitating translation of an action to a job. In one embodiment, each rule has a rule description defined using RDL. The following snippet illustrates the basic structure of an RDL rule:
In one embodiment, rules are stored in a MySQL database. However, an additional index table can allow the rule manager to quickly filter rules by enterprise id and action type. An example rules search index table schema (Table 1) and the associated rules table schema (Table 2) follow.
To prevent conflicts of fields used to filter rules aside from action_type_id, only one field from the set of these “filter fields” (enterprise_id, allEnterprises, allUsers) is used. Examples of valid values for the “filter fields” include, but are not limited to, those shown in Table 3.
In one embodiment, the rule manager also supports a ruleset. For example, rules that form part of a logical workflow can be grouped together into a ruleset. In this case, a ruleset_id is included with the rules template table schema. Users can interact with this feature from the UI.
In one embodiment, rules are cached in-memory for the rule manager instance. As discussed above, these local caches of all rule manager instances are synchronized via versioning in Zookeeper.
In one embodiment, the rule manager supports the following basic analysis of rules:
The service can also be set up with a secondary index that will allow aggregation counts of the kinds of rules or jobs present in the system.
In one embodiment, the rule manager supports templating. Templating includes the process of allowing the rule manager to populate fields from the action log into a given field or position in the job template. The fields can reference any field in the API event object.
In one embodiment, the rule manager supports versioning. Versioning allows the rule manager to check the action log version and the RDL version to determine if an incoming action log data can be successfully applied. For user-defined filters, only fields in the official events API can be referenced. The rule manager is responsible for ensuring fields in the events API are correctly extracted from action log data. This means that the rule manager is responsible for maintaining backwards compatibility.
In one embodiment, the rule manager supports permission control. That is, requests to the rule manager must be authenticated.
Workflows for Managing Flow-Based Interactions with Cloud-Based Shared Content
Any of the heretofore-described systems can include a workflow engine that operates using a cloud-based shared content system. The workflow engine manages workspaces accessed by users to facilitate collaboration (e.g., to perform workflow-specific tasks over shared documents).
As shown, certain users (e.g., collaborators 1603) having various collaboration roles (e.g., creator, editor, administrator, approver, auditor, reviewer, etc.) can use one or more instances of user devices 1602 to interact with one or more workspaces (e.g., workspace 16061, workspace 16062, etc.) facilitated by a cloud-based shared content system 1608 (e.g., comprising a content-based workflow service) in the cloud-based environment 16A00. As an example, collaborator 16031 might be a content creator (e.g., designer) with access to workspace 16061, collaborator 16033 might be an approver with access to workspace 16062, and collaborator 16032 might be an administrator with access to both workspaces. The workspaces can be stored in any location, and can be at least partially maintained by components within the cloud-based shared content system 1608. The cloud-based shared content system 1608 supports any variety of processing elements and/or storage devices 1620 (e.g., a storage filer, a storage facility, etc.) and/or servers 1610 such as a content management server 1612, a host server, a sync server, an application server, a cloud drive server, a content server, and/or other processing elements.
Any of the users can be provisioned authorized access to various portions (e.g., collections of shared content objects 1642) of a set of shared content 1622 stored in the storage devices 1620 without requiring the additional process of manually downloading and storing a file locally on an instance of the user devices 1602 (e.g., a desktop computer, a tablet, a WiFi phone, a workstation, a laptop computer, a smart phone, etc.). For example, one of the shared content objects 1642 (e.g., computer file, text document, audio file, video file, image file, etc.) created by collaborator 16031 might be viewed and/or approved by collaborator 16033 without informing the collaborator 16033 where the file is physically stored in the storage devices 1620. Such a facility streamlines the frequently repeated sharing and/or collaboration processes (e.g., by automating the process of locating the file).
Such sharing and/or collaboration processes can be facilitated at least in part by certain shared content object visualizations presented to the collaborators in the workspaces. Specifically, for example, an object visualization 1617 is presented in workspace 16061 to facilitate management (e.g., navigation, browsing, selection, etc.) of shared content accessible by a given user and/or collaborator. As shown in object visualization 1617, a collection of folders (e.g., fA and fB) and files (e.g., f3 and f5) are logically associated by various object relationships (e.g., object relationship 1616). In some embodiments, the cloud-based shared content system 1608 can use a set of object attributes 1644 in combination with work item attributes 1645 that are codified in a store of metadata 1624 to facilitate presentation of the object visualization 1617 in the workspace 16061. The object attributes 1644 in combination with work item attributes 1645 characterize various aspects pertaining to each object such as object relationships (e.g., parent folder, child items, etc.), user access permissions, object collaborators, object physical location, and/or other aspects. A workflow object can be explicitly associated with any other object, or a workflow object can be implicitly associated with any other object through a relationship or through shared attributes. The cloud-based shared content system 1608 can facilitate the foregoing collaboration processes by delivering object visualization, view data and/or content downloads to the user devices, and/or receiving interaction data and/or content uploads from the user devices.
In some embodiments, the herein disclosed techniques can also implement metadata-based attribute management techniques to facilitate cross-enterprise flow-based shared content collaboration. Specifically, for example, a workflow view 16191 can be presented in workspace 16062 to represent a workflow pertaining to a single task or a sequence of work items (e.g., w1, w2, w3a, and w3b) that are logically interrelated by various work item relationships (e.g., item relationship 1618). In some cases, certain shared content objects (e.g., file f5) can be associated with one or more work items (e.g., work item w2). In certain embodiments, the cloud-based shared content system 1608 can use a set of work item attributes 1645 codified in the metadata 1624 to facilitate presentation of the workflow view 16191 in the workspace 16062 (e.g., to meet the needs of a collaboration team). The work item attributes 1645 can further be used to mark a progress through the workflow depicted in the workflow view 1619k. Specifically, for example, the work item attributes 1645 can characterize various aspects pertaining to each work item comprising the workflow such as the item task (e.g., approve, sign, assign, publish, etc.), item user and/or owner, the item relationships (e.g., parent item, child items, etc.), access and/or view permissions, and/or other aspects. A workflow engine can be situated in this environment anywhere. As shown, the workflow engine facilitates operations performed between cloud-based shared content system components and constituent workspaces.
As earlier mentioned, one enterprise might want to invite users from one or more other external enterprises (or two or more enterprises, etc.) to participate in selected work items comprising a given workflow. For example, an external user might be selected for a reviewing role, an auditing role, a signing role, and/or other roles. Implementation of such cross-enterprise workflow collaboration continues to increase as many of today's business models rely on extensive partnerships. Such cross-enterprise collaboration as facilitated by the herein disclosed techniques is described as pertains to
The embodiment shown in
As shown in the workflow view 16192, the work items can be viewed by user u1 and user u2 of enterprise A. As further shown, a user 16053 (e.g., user u3) from an enterprise 1604B (e.g., enterprise B) can also be selected as a participant on work item w2. For example, the administrator user (e.g., user 16052) might select the user 16053 as the approver for file f5 for the workflow based on certain established business processes, rules, and/or policies. In some cases, participants external to the enterprise invoking the workflow might have a different view of the workflow (e.g., a restricted view). Specifically, for example, and as shown in workflow view 16193 in the workspace 16062, the user 16053 might merely have viewing access to work item w2 and the associated file f5.
In certain embodiments, the foregoing viewing and/or access permissions can be associated with each work item comprising a given workflow. According to the herein disclosed techniques, such fine-grained associations can be codified in metadata as further described pertaining to FIG. 16C1, FIG. 16C2, and FIG. 16C3.
FIG. 16C1, FIG. 16C2, and FIG. 16C3 illustrate a workflow attribute update technique 16C00 facilitated by a metadata-based workflow attribute management platform for cross-enterprise flow-based shared content collaboration. As an option, one or more variations of workflow attribute update technique 16C00 or any aspect thereof may be implemented in the context of the architecture and functionality of the embodiments described herein. The workflow attribute update technique 16C00 or any aspect thereof may be implemented in any environment.
As shown in FIG. 16C1, a workflow view 16194 depicts a workflow comprising three work items (e.g., w7, w8, and w9) associated with a shared content object (e.g., document f3). As an example, the workflow might be invoked by a user u4 from an enterprise C releasing the document f3 for approval (at workflow event 16521). In some cases, the shown workflow might be automatically selected based on the document, the user, the enterprise, and/or other criteria. For example, a document might be assigned a certain document type, which document type can then be matched to a specific workflow, which is in turn automatically triggered.
In other cases, the user u4 and/or a workflow administrator associated with the user u4 might design and/or select the shown workflow. Such an administrator can be associated with enterprise C or a third-party workflow application provider.
According to the herein disclosed techniques, the workflow depicted in workflow view 16194 can be managed using work item attributes captured in a metadata storage facility. Specifically, and as shown, such metadata might comprise various instances of workflow participant metadata and/or various instances of work item metadata. Other attributes and/or metadata are possible. For example, the workflow participant metadata 16321 and the work item metadata 16341 might correspond to the state of the workflow represented in the workflow view 16194. At launch of the workflow, the workflow participant metadata 16321 indicates that a user u3 from enterprise C is identified as the workflow administrator (e.g., type=admin) for work items w7, w8, and w9. Further, the user u4 from enterprise C is identified as a reviewer for work items w7, w8, and w9. The work item metadata 16341 associates various attributes with the work items comprising the workflow. For example, work item w7 might be associated with no parent item (e.g., parent=null, namely the root item in the workflow), document f5, a document release event (e.g., trigger=doc.release), selecting participants (e.g., task=select), a then current active state (e.g., state=active), and/or other attributes. As another example, work item w8 might be associated with a parent item w7, document f5, a trigger responsive to completion of the parent item (e.g., trigger=parent.done), an approver signature task (e.g., task=sign), a then current pending state (e.g., state=pend), and/or other attributes. Further, work item w9 might be associated with a parent item w8, document f5, a trigger responsive to completion of the parent item (e.g., trigger=parent.done), a final document publication (e.g., task=publish), a then current pending state (e.g., state=pend), and/or other attributes.
The admin role provisioned to user u3 in workflow view 16194 indicates that user u3 can take action to complete the active work item w7. Specifically, as an example, user u3 might invite user u5 from enterprise D to participate as an approver for the workflow (at workflow event 16522). Responsive to the workflow event 16522, a workflow view 16195 can be presented with associated instances of metadata (e.g., workflow participant metadata 16322 and work item metadata 16342). As shown, the workflow participant metadata 16322 comprises a metadata update 16361 identifying user u5 as the approver at work item w8. The work item metadata 16342 also comprises a metadata update 16362 indicating a state change for work item w7 from active to done, and a state change for work item w8 from pend to active. The work item w8 can remain in the active state until the task (e.g., sign) associated with work item w8 is executed.
FIG. 16C2 depicts a state transition of the workflow view 16195, the workflow participant metadata 16322, and the work item metadata 16342 earlier described in FIG. 16C1. As shown, the state transition is responsive to the user u5 from enterprise D signing the document f3 (at workflow event 16523). Responsive to the workflow event 16523, a workflow view 16196 can be presented with associated instances of metadata (e.g., workflow participant metadata 16323 and work item metadata 16343). As shown, the workflow participant metadata 16323 comprises a metadata update 16363 updating the role of user u4 to approver and updating the role of user u5 to reviewer. The work item metadata 16343 also comprises a metadata update 16364 indicating a state change for work item w8 from active to done and a state change for work item w9 from pend to active. The work item w9 can remain in the active state until the task (e.g., publish) associated with work item w9 is executed.
Specifically, FIG. 16C3 depicts a state transition of the workflow view 16196, the workflow participant metadata 16323, and the work item metadata 16343 earlier described in FIG. 16C2. As shown, the state transition is responsive to the user u4 from enterprise C publishing the document f3 (at workflow event 16524). For example, the user u4 might click a “Publish” button presented in a user device after reviewing the workflow view 16196 and/or the document f3 to confirm completion of all ancestor work items in the workflow. Responsive to the workflow event 16524, a workflow view 16197 can be presented with associated instances of metadata (e.g., workflow participant metadata 16323 and work item metadata 16344). As shown, the work item metadata 16344 comprises a metadata update 16365 indicating a state change for work item w9 from active to done.
One embodiment of a system for implementing the foregoing workflow attribute update technique 16C00 and/or other herein disclosed techniques is described as pertaining to
The system in
The user 1605N can further participate in flow-based collaboration using a web application 1607N on a user device 1602N to issue instances of a workflow event 1652N to, and receive instances of a workflow response 1654N from, the workflow API 1664. The user 1605M and the user 1605N can use one or more instances of a workflow view 1619M and a workflow view 1619N, respectively, at their respective user devices to further facilitate the flow-based collaboration. In some cases, for example, workflow events can be invoked from the workflow views. For example, a user might click an “Approve” button in a workflow view to create a workflow event that might change the state of the workflow. In other cases, the workflow views can be derived from the workflow responses. For example, a workflow state change might precipitate a workflow response that results in presenting a signature box to an approver in a workflow view.
The workflow API 1664 can process (e.g., parse, translate, etc.) the incoming and outgoing messages (e.g., events, responses, etc.) to facilitate interactions with a workflow engine 1662 operating at the content management server 1612. Specifically, the workflow event 1652M and/or the workflow event 1652N might correspond to at least a portion of the workflow events 1652 processed at the workflow engine 1662. The workflow response 1654M and/or the workflow response 1654N can correspond with at least a portion of the workflow responses 1654 processed at the workflow engine 1662. In certain embodiments, one or more of the users (e.g., user 1605M) participating in the flow-based collaboration can select one or more workflow objects (e.g., workflow object 1656M) to deliver to the workflow API 1664, which workflow objects describe a given workflow (e.g., the work items, etc.). In some cases, a given workflow object might be selected by the workflow engine 1662 based on certain workflow events and/or other information. A set of workflow objects 1656 might be available at the workflow engine 1662 for selection and/or activation.
Each instance of workflow objects 1656 can be characterized by the work item attributes 1645 codified in the metadata 1624 stored in the storage devices 1620. The herein disclosed techniques can be facilitated at least in part by a set of metadata updates 1636 to the metadata 1624 responsive to the workflow events 1652. Specifically, the workflow engine 1662 can generate the workflow responses 1654 based at least in part on detected instances of the workflow events 1652. The workflow responses 1654 can be used to determine the metadata updates 1636. For example, a workflow event corresponding to a “Forward” button click might generate a workflow response comprising an update to metadata describing a work item state (e.g., from state=active to state=done) and a workflow alert sent to the user device of the owner of the next work item in the workflow. In some cases, one or more of the object attributes 1644 characterizing one of the shared content objects 1642 associated with the workflow might be updated in the metadata 1624. In other cases, a given workflow response might precipitate one or more instances of content updates 1638 to the shared content 1622. For example, a signature provided by an approver might be applied in a designated location of a legal agreement without having to download, print, sign, scan, and upload the agreement.
In some embodiments, the workflow engine 1662 might apply a set of workflow rules 1626 to the workflow events 1652 and/or the work item attributes 1645 to determine the workflow responses 1654, the metadata updates 1636, and/or the content updates 1638. Specifically, an event mapping 1647 in the workflow rules 1626 might map a received workflow event to one or more operations (e.g., update metadata, update content, send workflow alert, etc.) executed at the workflow engine 1662. A logic mapping 1646 in the workflow rules 1626 and/or a mapping operation of functions within the rule API 1665 might map a trigger description in the work item attributes 1645 to a set of logic to be executed at the workflow engine 1662. For example, a trigger=parent.done work item attribute might map to a set of conditional logic (e.g., if parent.state==“done” THEN set.metadata.child.state=“active”) comprising inputs extracted from other metadata (e.g., parent attributes, state attributes, etc.).
The system shown in
As earlier described, each instance of the workflow objects 1656 can be characterized by a set of work item attributes 1645. As an example, each work item comprising a workflow defined by a workflow object might be described in a metadata table (e.g., persistent store) having columns corresponding to the attributes shown in
Specifically, the example set of work item attributes 1645 shown in
In some embodiments, at least some of the foregoing attributes and/or other information might be applied to machine learning techniques to select and/or dynamically construct a workflow object for a given scenario. For example, such techniques might facilitate automatically applying a security classification and associated workflow object (e.g., for approval, compliance, etc.) to a document based on its attributes as compared to the attributes of other documents and workflow objects. In such cases, the learning model might be trained by workflow objects manually designed by administrators.
Further details regarding general approaches to providing secure access to shared documents are described in U.S. application Ser. No. 14/838,212 titled, “ACCESSING A CLOUD-BASED SERVICE PLATFORM USING ENTERPRISE APPLICATION AUTHENTICATION” filed on Aug. 27, 2015, which is hereby incorporated by reference in its entirety.
Further details regarding general approaches to machine learning analysis of documents are described in U.S. Application Ser. No. 62/113,288 titled, “METHOD AND SYSTEM FOR IMPLEMENTING MACHINE LEARNING ANALYSIS OF DOCUMENTS” filed on Feb. 6, 2015, which is hereby incorporated by reference in its entirety.
In other embodiments, the workflow object can be selected from a repository of workflows (e.g., workflow templates) for implementation.
As shown in
A selected workflow object 1856 can be selected from the workflow repository 1850 when a user invokes a workflow at the workflow engine 1662 (at operation 1802). Responsive to the configuration of the selected workflow object 1856, the workflow engine 1662 can perform various operations, which operations might generate instances of workflow responses 1654. Specifically, the workflow engine 1662 can begin listening for workflow events 1652 (at operation 1804). Instances of workflow events 1652 and/or other inputs to the workflow engine 1662 can be received from a cloud-based shared content storage service, from external sources (e.g., third-party systems), and/or other sources. The workflow engine 1662 can also create metadata for the selected workflow object 1856 (at operation 1806). For example, the metadata 1624 might be based at least in part on the work item attributes for the selected workflow object 1856 for managing the workflow states 1845 and/or other workflow attributes. In some cases, the metadata can be updated by the workflow engine 1662 based on detected instances of the workflow events 1652 (at operation 1808). The workflow engine 1662 might also update the metadata to identify participants added as collaborators to the workflow (at operation 1810). Various workflow views and/or alerts can be presented to such participants to facilitate the execution of the workflow (at operation 1812).
In some embodiments, the workflow engine 1662 can use the workflow rules 1626 to determine the workflow responses 1654 and/or other outcomes. For example, the workflow rules 1626 can apply to the selected workflow object 1856 and/or to the work items comprising the selected workflow object 1856. As an example, such rules might comprise Boolean and/or conditional logic clauses or statements. In some cases, certain workflow attributes and/or workflow event data might be applied as inputs to such rule-based logic. In certain embodiments, a rules engine 1862 might be implemented to interface between the workflow engine 1662 and the workflow rules 1626. The rules engine 1862 can be implemented as a service. In such cases, the workflow engine 1662 can pass messages and/or data to the rules engine 1862 (e.g., external to the workflow engine environment) for processing and response.
The techniques described as pertaining to subsystem 1800 and/or other embodiments disclosed herein can facilitate cross-enterprise flow-based shared content collaboration for users and/or enterprises (e.g., two or more users that are associated with one or more different enterprises) interacting directly with a cloud-based shared content platform or interacting with the cloud-based shared content platform through a third-party workflow provider (e.g., using an API provided by the cloud-based platform). Embodiments implementing variations of a third-party provider framework are shown and described as pertaining to
The herein disclosed techniques can be implemented in systems comprising various partitions (e.g., layers) such as partitions that can facilitate one or more third-party applications pertaining to workflow management. For example, a third party might provide a framework to provide workflow templates (e.g., for collaboration over a document) to a set of external users. In such cases, the third party can use an API provided by a “back-end”cloud-based workflow management environment implementing the herein disclosed techniques.
Specifically,
The provider event listener 1932 can issue various messages (e.g., action 19721, workflow event, etc.) to the finite state machine 1964 through an API. As an example, the finite state machine 1964 can manage the sequence of steps (e.g., work items, tasks, internal events, etc.) comprising a given workflow instance. The finite state machine 1964 can also evaluate the context of events and/or responses, publish state transition events, and/or perform other operations. Specifically, for example, the finite state machine 1964 can respond to the received messages according to the workflow selected at the action provider framework 1930. In some cases, received actions and/or workflow events can precipitate a change to shared content (e.g., a document to be acted upon) and/or can precipitate a change to workflow states (e.g., workflow state 18451, . . . , workflow state 1845N) pertaining to the selected workflow. Some events might be captured in an event log 1962 to facilitate certain operations such as workflow processing, auditing, and/or other operations. The action evaluator 1966 can interpret the action, the workflow state, and/or other information to determine one or more messages to deliver to the provider worker 1934. For example, multiple operations (e.g., recurrent scheduled jobs) within the cloud-based workflow management platform 1960 in response to a received instance of the action 19721 might result in merely one instance of the action 19722 (e.g., work item is “complete”) delivered to the provider worker 1934.
A sequence of actions 1974 (e.g., continuous incoming and outgoing actions) can comprise the actions for fully executing a given workflow. For example, a multiple user document collaboration workflow might be invoked by a user creating and submitting (e.g., using the provider worker 1934) a document to be acted upon (at step #1). Responsive to detecting the document submission, the provider can select a workflow object and/or template from the provider workflow repository 1950 based on the submitted document (at step #2). In some cases, certain attributes (e.g., work item attributes) pertaining to the selected workflow might be delivered to the workflow engine 1662 to facilitate later processing. In other cases, certain information associated with the work items (e.g., review tasks) of the selected workflow can be stored in the provider workflow states 1945 (at step #3). The provider event listener 1932 can detect the completion of an action over the document by a first user and inform the finite state machine 1964 of the occurrence of action 19721 (at step #4). In some cases, the event can be logged (at step #5). The action evaluator 1966 can interpret the workflow state and/or other information available to the workflow engine 1662 to determine a response to provide to the provider worker 1934. For example, a message might be delivered indicating a next action is called for by the workflow such that the provider worker 1934 can issue an alert to the user responsible for taking the next action. The sequence of actions 1974 can continue until the workflow is complete. In some cases, the sequence of actions 1974 can be logged during processing and/or at completion of the workflow.
Any of the aforementioned operations over work items and their constituent metadata (e.g., work item attributes 1645) and/or operations over shared content (e.g., shared content objects 1642 in
Such metadata can be used in many contexts, including contexts involving applications that interface with a metadata-based workflow management platform to carry out a workflow involving multiple parties, and involving documents that are stored at and accessed through a cloud-based repository. Strictly as one example, a metadata-based workflow management platform can be used to carry out multiple tasks to obtain a signature on a document.
As aforementioned, workflow objects comprise workflow metadata that describes a workflow (e.g., a document signature workflow) as a set of workflow tasks to be carried out in a progression. Processing of a workflow task and/or carrying out a portion of the progression includes modification of shared content objects (e.g., by applying a signature to the document). The processing or modification events are detected through workflow events that occur either in the domain of the action provider framework 1930 or in the domain of the cloud-based workflow management platform 1960. Such events cause one or more workflow responses to be generated. Workflow responses comprise updates to the workflow metadata to record progression through the workflow (e.g., the document has been signed) and/or workflow responses comprise updates to any one or more of the stored objects (e.g., the signature is applied to the document).
The shown flow (e.g., step #1 through step #5) depicts a “Document Signing Workflow”. In this scenario, a document provider such as a bank agent or real estate broker creates a document to be signed. Such a document might be stored in the provider workflow repository 1950 (as shown at step #1). Next (step #2), in this “Document Signing Workflow”, a provider generates a workflow as a series of upload, sharing, review, signature application, possibly as well as further review, and/or further sharing tasks. Availability of the created document and availability of the generated workflow is made known to the provider worker 1934. The act of accessing the created document and generated workflow by the provider worker can themselves be events and/or can precipitate further events that are detected by the provider event listener 1932. Some or all of the generated workflow and some or all of the created document are communicated from the action provider framework 1930 to the cloud-based workflow management platform 1960 (step #4). Some portions or all of the generated workflow and some portions or all of the created document are stored as shared content 1622, which (as shown) is accessible by the workflow engine 1662. The act of the aforementioned storage of shared content can be logged (step #5) in event log 1962. Moreover, the generated workflow and any corresponding metadata is read by the workflow engine.
In some cases, and as shown, the generated workflow and any corresponding metadata is processed by a finite state machine 1964. The action evaluator 1966 determines if there are workflow tasks that are ready to be completed and/or workflow tasks that are ready to be initiated. If so, then the workflow engine might take one or more actions based on the workflow and/or the workflow metadata values. In the specific case of a document signing workflow, the action evaluator will respond by emitting a workflow response (e.g., action 19722) that is to advise the provider worker that the document is in a sharable state and that the workflow indicates that the availability of the document can be promulgated to the users 1605 (step #6). The user or users can receive notification of the availability of the document and request for signature via a push request 1944 (step #7).
At some point, a user will sign the document or otherwise respond to the request (e.g., by following instructions in the request, or by saving the signed document, etc.) which causes the push request to be satisfied. In the situation that the user does not respond to the request within a certain amount of time, the provider worker might issue a further push request to spur the user to follow the instructions or otherwise complete the assigned task. When the user follows the instructions or otherwise completes the assigned task (e.g., signs the file), the provider listener detects the completion event (step #8) and forwards the event to the workflow engine of the cloud-based workflow management platform (step #9). The event (e.g., the signing of the document), possibly including a document or document link or metadata corresponding to the event, is processed by the workflow engine, which in turn can advance the workflow state 1845N (step #10). The next workflow state is entered and considered with respect to its possible completion or need to initiate next actions. In this “Document Signing Workflow”, next actions might involve communications to the users to indicated the advance of the state (e.g., that the document has been signed). In some cases the advance of the state might invoke workflow responses to make updates to the document and/or its metadata and/or to the work item attributes or any other aspects of the workflow metadata and/or to any other shared content objects.
The system 2000 comprises at least one processor and at least one memory, the memory serving to store program instructions corresponding to the operations of the system. As shown, an operation can be implemented in whole or in part using program instructions accessible by a module. The modules are connected to a communication path 2005, and any operation can communicate with other operations over communication path 2005. The modules of the system can, individually or in combination, perform method operations within system 2000. Any operations performed within system 2000 may be performed in any order unless as may be specified in the claims.
The shown embodiment implements a portion of a computer system, presented as system 2000, comprising a computer processor to execute a set of program code instructions (module 2010) and modules for accessing memory to hold program code instructions to perform: accessing, over a network, at least one server in a cloud-based environment to interface with one or more storage devices that store one or more shared content objects accessible by two or more users (module 2020); selecting at least one workflow object, the workflow object describing a workflow comprising one or more work items, the workflow object characterized at least in part by one or more work item attributes (module 2030); codifying the work item attributes in a set of metadata stored in the storage devices (module 2040); detecting one or more workflow events (module 2050); and generating one or more workflow responses based at least in part on the workflow events, the workflow responses comprising at least one metadata update to the metadata (module 2060).
Variations of the foregoing may include more or fewer of the shown modules and variations may perform more or fewer (or different) steps, and/or may use data elements in more, or in fewer (or different) operations.
Some embodiments include variations where the workflow responses further comprise at least one content update to the shared content objects.
Some embodiments include variations where the work item attributes associate at least one of, the users, or the shared content objects, to at least one of the work items.
Some embodiments include variations where the users are associated with two or more enterprises.
Some embodiments include variations that comprise acts for receiving, over the network, at least one of, the work item attributes, or the workflow events, from one or more user devices associated with the users.
Some embodiments include variations that comprise acts for delivery, over the network, at least one of, a workflow alert, or a workflow view, to one or more user devices associated with the users.
Some embodiments include variations where at least one of the workflow responses is generated by applying one or more workflow rules to at least one of, the work item attributes, or the workflow events.
Some embodiments include variations where the workflow rules comprise at least one of, an event mapping, or a logic mapping.
Some embodiments include variations where the workflow object is selected based at least in part on at least one of the workflow events.
Some embodiments include variations that comprise acts for codifying one or more object attributes in the metadata, the object attributes characterizing the shared content objects.
Some embodiments include variations where the work item attributes characterize at least one of, an item, a state, a task, a trigger, a rule, a parent, an object, a user, an enterprise, a type, one or more permissions, one or more constraints, one or more messaging settings, or an environment.
According to an embodiment of the disclosure, computer system 21A00 performs specific operations by data processor 2107 executing one or more sequences of one or more program code instructions contained in a memory. Such instructions (e.g., program instructions 21021, program instructions 21022, program instructions 21023, etc.) can be contained in or can be read into a storage location or memory from any computer readable/usable storage medium such as a static storage device or a disk drive. The sequences can be organized to be accessed by one or more processing entities configured to execute a single process or configured to execute multiple concurrent processes to perform work. A processing entity can be hardware-based (e.g., involving one or more cores) or software-based, and/or can be formed using a combination of hardware and software that implements logic, and/or can carry out computations and/or processing steps using one or more processes and/or one or more tasks and/or one or more threads or any combination thereof.
According to an embodiment of the disclosure, computer system 21A00 performs specific networking operations using one or more instances of communications interface 2114. Instances of the communications interface 2114 may comprise one or more networking ports that are configurable (e.g., pertaining to speed, protocol, physical layer characteristics, media access characteristics, etc.) and any particular instance of the communications interface 2114 or port thereto can be configured differently from any other particular instance. Portions of a communication protocol can be carried out in whole or in part by any instance of the communications interface 2114, and data (e.g., packets, data structures, bit fields, etc.) can be positioned in storage locations within communications interface 2114, or within system memory, and such data can be accessed (e.g., using random access addressing, or using direct memory access DMA, etc.) by devices such as data processor 2107.
The communications link 2115 can be configured to transmit (e.g., send, receive, signal, etc.) any types of communications packets 2138 comprising any organization of data items. The data items can comprise a payload data area 2137, a destination address 2136 (e.g., a destination IP address), a source address 2135 (e.g., a source IP address), and can include various encodings or formatting of bit fields to populate the shown packet characteristics 2134. In some cases the packet characteristics include a version identifier, a packet or payload length, a traffic class, a flow label, etc. In some cases the payload data area 2137 comprises a data structure that is encoded and/or formatted to fit into byte or word boundaries of the packet.
In some embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement aspects of the disclosure. Thus, embodiments of the disclosure are not limited to any specific combination of hardware circuitry and/or software. In embodiments, the term “logic” shall mean any combination of software or hardware that is used to implement all or part of the disclosure.
The term “computer readable medium” or “computer usable medium” as used herein refers to any medium that participates in providing instructions to data processor 2107 for execution. Such a medium may take many forms including, but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks such as disk drives or tape drives. Volatile media includes dynamic memory such as a random access memory.
Common forms of computer readable media includes, for example, floppy disk, flexible disk, hard disk, magnetic tape, or any other magnetic medium; CD-ROM or any other optical medium; punch cards, paper tape, or any other physical medium with patterns of holes; RAM, PROM, EPROM, FLASH-EPROM, or any other memory chip or cartridge, or any other non-transitory computer readable medium. Such data can be stored, for example, in any form of external data repository 2131, which in turn can be formatted into any one or more storage areas, and which can comprise parameterized storage 2139 accessible by a key (e.g., filename, table name, block address, offset address, etc.).
Execution of the sequences of instructions to practice certain embodiments of the disclosure are performed by a single instance of the computer system 21A00. According to certain embodiments of the disclosure, two or more instances of computer system 21A00 coupled by a communications link 2115 (e.g., LAN, PTSN, or wireless network) may perform the sequence of instructions required to practice embodiments of the disclosure using two or more instances of components of computer system 21A00.
The computer system 21A00 may transmit and receive messages such as data and/or instructions organized into a data structure (e.g., communications packets). The data structure can include program instructions (e.g., application code 2103), communicated through communications link 2115 and communications interface 2114. Received program code may be executed by data processor 2107 as it is received and/or stored in the shown storage device or in or upon any other non-volatile storage for later execution. Computer system 21A00 may communicate through a data interface 2133 to a database 2132 on an external data repository 2131. Data items in a database can be accessed using a primary key (e.g., a relational database primary key).
The processing element partition 2101 is merely one sample partition. Other partitions can include multiple data processors, and/or multiple communications interfaces, and/or multiple storage devices, etc. within a partition. For example, a partition can bound a multi-core processor (e.g., possibly including embedded or co-located memory), or a partition can bound a computing cluster having plurality of computing elements, any of which computing elements are connected directly or indirectly to a communications link. A first partition can be configured to communicate to a second partition. A particular first partition and particular second partition can be congruent (e.g., in a processing element array) or can be different (e.g., comprising disjoint sets of components).
A module as used herein can be implemented using any mix of any portions of the system memory and any extent of hard-wired circuitry including hard-wired circuitry embodied as a data processor 2107. Some embodiments include one or more special-purpose hardware components (e.g., power control, logic, sensors, transducers, etc.). A module may include one or more state machines and/or combinational logic used to implement or facilitate the operational and/or performance characteristics of managing flow-based user interactions with shared content in a highly collaborative cloud-based environment.
Various implementations of the database 2132 comprise storage media organized to hold a series of records or files such that individual records or files are accessed using a name or key (e.g., a primary key or a combination of keys and/or query clauses). Such files or records can be organized into one or more data structures (e.g., data structures used to implement or facilitate aspects of managing flow-based user interactions with shared content in a highly collaborative cloud-based environment). Such files or records can be brought into and/or stored in volatile or non-volatile memory.
A portion of workspace access code can reside in and be executed on any access device. Also, a portion of the workspace access code can reside in and be executed on any computing platform 2151, including in a middleware setting. As shown, a portion of the workspace access code resides in and can be executed on one or more processing elements (e.g., processing element 21051). The workspace access code can interface with storage devices such as the shown networked storage 2155. Storage of workspaces and/or any constituent files or objects, and/or any other code or scripts or data can be stored in any one or more storage partitions (e.g., storage partition 21041). In some environments, a processing element includes forms of storage, such as RAM and/or ROM and/or FLASH, and/or other forms of volatile and non-volatile storage.
A stored workspace can be populated via an upload (e.g., an upload from an access device to a processing element over an upload network path 2157). A stored workspace can be delivered to a particular user and/or shared with other particular users via a download (e.g., a download from a processing element to an access device over a download network path 2159).
In the foregoing specification, the disclosure has been described with reference to specific embodiments thereof. It will however be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the disclosure. For example, the above-described process flows are described with reference to a particular ordering of process actions. However, the ordering of many of the described process actions may be changed without affecting the scope or operation of the disclosure. The specification and drawings are to be regarded in an illustrative sense rather than in a restrictive sense.
The present application is a continuation-in-part of co-pending U.S. patent application Ser. No. 14/474,008 titled, “CONFIGURABLE METADATA-BASED AUTOMATION AND CONTENT CLASSIFICATION ARCHITECTURE FOR CLOUD-BASED COLLABORATION PLATFORMS”, filed Aug. 29, 2014, and the present application claims the benefit of priority to U.S. Provisional Application Ser. No. 62/214,176 titled, “RULE-BASED AUTOMATION AND CONTENT CLASSIFICATION ARCHITECTURE FOR CLOUD-BASED COLLABORATION PLATFORMS”, filed Sep. 3, 2015, and the present application claims the benefit of priority to U.S. Provisional Application Ser. No. 62/234,024 titled, “CONFIGURABLE METADATA-BASED AUTOMATION AND CONTENT CLASSIFICATION ARCHITECTURE FOR CLOUD-BASED COLLABORATION PLATFORMS USING TASK-DRIVEN WORKFLOWS” filed Sep. 28, 2015, which are all hereby incorporated by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62214176 | Sep 2015 | US | |
| 62234024 | Sep 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14474008 | Aug 2014 | US |
| Child | 15243695 | US |
