Ask Eliza Service: | 1. A search field is provided where approved people may enter requests for tasks to be done. | 2. Every search request is recorded as a task for the auther and a list of historical tasks can be viewed and tasks replicated. | 3. Simply enter a phrase into the search field and a new task will be added and done. | 4. Some tasks will show a specified form or will download a specified set of data, but a general output will be a list of the top ten matching results. |
Tasks that people search for: | 1. Please download all contract data. | 2. Please show customer PDM. | 3. Please show service 101234123412. | 4. Please find site EN9. | 5. Please list all customers in Harlow. | 6. Please show person called Gina. | 7. Please show rates for DNO 10 profile 03. |
Behaviour: | 1. Like a child; Eliza has been taught to understand and respond accordingly to good and bad behaviour. | 2. Good behaviour may be rewarded with instant results even when the request is not complete and correct. | 3. Bad behaviour may be rewarded with pedantic correctness checks and lists of potential matches. | 4. Eliza has a finite glossary of terms so customer and client may not always be interchangeable. |
Management Information: | 1. Management information tends to present historical facts as a tabular list. | 2. Where practical, active links are included so a person may drill down into forms and other lists. |
Business Intelligence: | 1. Business Intelligence tends to present projected, consolidated and derived data as a tabular list. Projected data tends to be date and duration oriented, such as monthly totals. | 2. Where practical, active links are included so a person may drill down into forms and other lists. | 3. Business Intelligence is about transforming historical data into valuable information. |
Internals: | 1. The Ask Eliza Service creates three operands as (1) action, (2) object and (3) cause. | 2. Each object is represented as a set of field definitions with cause as (1) sort-hide-show, (2) condition and (3) filter value. | 3. A default object definition is loaded and indexed by record and field number. | 4. The search request is appended to the default array with optional customisable sort, condition and filter. | 3. Every search request (k25) has a name that may be reused by others or may be cloned as a new request that is customised. |
Request Table k25: | 1. 01 to 22 follows the standard table layout that includes author and last change data. | 2. 23 is the search field value of up to 128 characters. | 3. 24 is the derived or selected action such as "123". | 3. 25 is the derived or selected object such as "k14" or "k1326". | 3. 26 is the optional derived cause as sort, condition, filter. |
Document Control. | 1. Document Title: Ask Eliza Service. | 4. Description: Ask Eliza Service. | 3. Keywords: Ask Eliza Service. | 6. Privacy: Shared with approved people for the benefit of humanity. | 7. Edition: 1.1. | 8. Issued: 2 Jan 2018. |
|
|