 |
|
|
|
|
|
|
|
 |
 |
|
|
 |
|
|
| | Veraterm Processes
|
| |
The Veraterm Technology Engine manages a set of processes behind the documents in a host application.
The diagram, below, depicts a series of process categories that represent functions inside the
Veraterm Technology Engine. The process flow is called "MRAA" for the four main process categories.
|
| | 
|
| |
Manage The Veraterm System manages by:
|
|
 |
Monitoring the host application and its collection of documents. |
|
Detecting content changes. |
|
Parsing - Applying text mining processes to identify "interesting" text (ie: names that should be looked up) |
|
Running the "Term Recognizer" (TR) system. TRs are the components which are
configured to make specific links between text and data. |
|
Controlling the security mechanism and the pooled database connections
|
Relate Term Recognizers orchestrate the integration
process. TRs use:
|
|
|
Data Access objects managed by the Veraterm System. |
|
Term Lists for text comparisons and for system metadata |
|
The Search Term buffer for recent query results |
|
Entity Containers for configurable XML data storage |
|
Data Atlases, Data Maps and Data Links (all configurable) which hold metadata about the
structure of entities, their database systems and the relationships between them.
This sub-system is responsible for the updatable composite views involving two-or-more applications
and the integration between them.
|
Analyze Term Recognizers also make use of Veraterm Intelligence tools:
|
|
|
The Veraterm System manages a set of "clues" or "facts" related to a document.
For example, clues can discern that an email is actually a "request for information. |
|
Veraterm Events. An event subsystem exists for the benefit of the Term Recognizers (TRs).
TRs thereby have knowledge of the content and context of the whole document! |
|
A practical example of applying this technology is the resolution of duplicate names.
The Veraterm System continues to look for clues which could be used to tell them apart - even if the clue is typed later.
|
Assist The goal of the Veraterm System is to assist the
user in a significant way to improve workflow efficiency through automation.
The system uses additional tools and processes to do this even after an InfoTerm has been created.
|
|
|
Entity Containers load data in the background and store the data locally for instantaneous access.
This is beneficial when a full view of a customer is comprised of information from multiple systems,
including internet-based data sources. |
|
Entities (such as customers, accounts, orders, call-center tickets, etc) have knowledge of how to display themselves.
This makes the creation of Smart Tag actions much easier. The Veraterm System provides both the data
and an internal display mechanism |
|
Entities know how to update themselves. If permissible, the Entity System can send inserts,
updates and deletes back to the host application, making Veraterm Integration a 2-way link.
The author of a Smart Tag action class does not need to be concerned with this level of infrastructure. |
|
Veraterm Actions. The Veraterm System not only creates Smart Tags but has its own output mechanism.
The system can be configured to initiate any number of processes based on the business logic of the Term Recognizer.
|
|
| |
 System Architecture
|
|
