英語 での The context correlation engine の使用例とその 日本語 への翻訳
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Programming
In step 324, the context correlation engine 168 determines whether the token or workflow has ended.
The context correlation engine 168 may provide workflow material to newly added members of a work or task class or group.
When a new token 180 is to be created, the context correlation engine 168 creates a new token 180 at step 308.
The context correlation engine 168 monitors user behavior on a variety of different communication devices and computers and correlates these user behaviors with each other.
When the third user requests a draft document, the context correlation engine 168 provides the master draft document rather than the previous version.
The context correlation engine 168 can perform these functions for a communication session, which is particularly advantageous for non-communication workflow sessions.
Another example is when a user is working for aparticular party within a contact management application, and the context correlation engine 168 automatically launches the information referenced for that task To do.
Finally, at step 340, the context correlation engine 168 stores the token 180, and at step 344, the operation ends.
The context correlation engine 168 is applicable to multiple external and internal communication devices and computers when centralized at the communication server 136.
This is done, for example, by the context correlation engine 168 comparing the content, tokens, and versions that each member of the collaborative work flow is using.
The context correlation engine 168 reconciles the changes and creates a new version(or master draft) of the draft document that incorporates the first and second sets of changes.
When the token or workflow ends, the context correlation engine 168 determines at decision diamond 332 whether the token 180 should be routed to another computing device.
At step 406, the context correlation engine 168 converts the token 180 into the user's selected communication node capabilities, provisioning, and/ or preferences.
Furthermore, the context correlation engine 168 within each of the compute nodes can executethe contents of the token 180.
In another example, the context correlation engine 168 automatically performs corrections or updates to draft documents that are being addressed simultaneously or sequentially by multiple users.
Thus, the context correlation engine 168 can ensure that all parties working on a workflow have all of the correct versions of the material needed to contribute to the work.
The context correlation engine 168 uses the token 180 to determine, activate, and/ or otherwise access information that the user needs before for the workflow task event.
The context correlation engine creates and stores a series of tokens 180 at the user's request, each token 180 associated with a specified point in time or cursor position in the workflow session.
In addition, version 228 allows the context correlation engine 168 to determine when one or more users of a document do not have all the information necessary to effectively contribute to the workflow.
The context correlation engine 168 can determine where the additional information is located, seek approval from the owner, and provide the information to another party or transfer a copy after approval.
The context correlation engine 168 identifies keywords such as customer, client, or problem number in the entry description, or instead references the workflow identifier 200 or token identifier 204 directly.
After performing either step 308 or 312, the context correlation engine 168 in step 316 determines user behavior in the workflow and the selected computing device(one or more) to determine associative and/ or contextual information.
The context correlation engine 168 uses rich presence information, activity information, personas, context information, user roles, user levels, user organizations, and various other detection/ class-based indicators to intelligently relate to context associations.
Alternatively, the context correlation engine 168 notifies the user that the draft was previously edited by the first user and the second user when the third user attempts to retrieve the original draft document, and the user One or both of the first and second edited drafts can be allowed to be retrieved.
The context correlation engine 168 uses machine learning algorithms such as via correlation to monitor user behavior and provide the user with context and associative token creation suggestions when various related materials are being used by the user, And/ or simple patterns by the user can be predicted to make the system more robust over time and accurate with less user input.
In step 400, context correlation engine 168 detects a stimulus, such as stimulus 208 in token 180.
Alternatively, the user or context correlation engine 168 can identify or select a particular workflow, which automatically selects the associated token 180 of the workflow.
For example, version 228 allows context correlation engine 168 to determine which of a number of versions must be presented to the user.
In decision diamond 304, context correlation engine 168 determines whether a new token 180 should be created as part of a new or existing workflow.