Difference between revisions of "MetaData Queue Management"
From All n One's bxp software Wixi
Philip Lacey (talk | contribs) |
Philip Lacey (talk | contribs) |
||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
| − | Queue Management is the outbound process of stacking up the records to be contacted. | + | Queue Management is the outbound process of stacking up the records to be contacted. |
| + | When there are many combinations of queues to be executed in specific orders a MetaData program allows numerous queue instructions to be lined up with a single button click. | ||
| − | This | + | This use of MetaData allows easy creation of the queue stack. |
| + | |||
| + | |||
| + | == Build Sequence == | ||
| + | |||
| + | Preparation | ||
| + | |||
| + | * Firstly identify the "Outcome" and the "Number of Attempts" that you want executed. We calls these Outcome + Attempt from here out. | ||
| + | * Order them in the sequence you want them performed. | ||
| + | |||
| + | |||
| + | There are a number of steps to building the MetaData Program | ||
| + | |||
| + | # Create a Program | ||
| + | # Create a Sequence | ||
| + | # Create as many rules as Outcome + Attempt rules needed. | ||
| + | |||
| + | |||
| + | == Usage == | ||
| + | |||
| + | |||
| + | Once the program has been built it can be called quickly pointing to the following URL | ||
| + | |||
| + | You must replace client_demo with your system name | ||
| + | |||
| + | You must replace the X at the end of the URL with the Program ID. | ||
| + | |||
| + | |||
| + | * https://ww3.allnone.ie/client/client_demo/metadata/userProgram-execute.asp?ID=X | ||
== Rule Parameters == | == Rule Parameters == | ||
| + | |||
* MetaData Rule -- CrossDatabase_Update_Simple | * MetaData Rule -- CrossDatabase_Update_Simple | ||
| Line 20: | Line 50: | ||
== Full Rule Layout == | == Full Rule Layout == | ||
| + | |||
<syntaxhighlight lang="html4strict"> | <syntaxhighlight lang="html4strict"> | ||
| Line 36: | Line 67: | ||
== Rule Details == | == Rule Details == | ||
| + | |||
When this MetaData rule is executed the current outbound record stack will be removed, this will not affect the data in the records. The Metadata rule will then insert the new call stack(Parameter 5 in the rule). | When this MetaData rule is executed the current outbound record stack will be removed, this will not affect the data in the records. The Metadata rule will then insert the new call stack(Parameter 5 in the rule). | ||
Revision as of 14:26, 15 September 2014
Contents
1 Overview
Queue Management is the outbound process of stacking up the records to be contacted.
When there are many combinations of queues to be executed in specific orders a MetaData program allows numerous queue instructions to be lined up with a single button click.
This use of MetaData allows easy creation of the queue stack.
2 Build Sequence
Preparation
- Firstly identify the "Outcome" and the "Number of Attempts" that you want executed. We calls these Outcome + Attempt from here out.
- Order them in the sequence you want them performed.
There are a number of steps to building the MetaData Program
- Create a Program
- Create a Sequence
- Create as many rules as Outcome + Attempt rules needed.
3 Usage
Once the program has been built it can be called quickly pointing to the following URL
You must replace client_demo with your system name
You must replace the X at the end of the URL with the Program ID.
4 Rule Parameters
- MetaData Rule -- CrossDatabase_Update_Simple
- DB Table Name -- Campaign
- Field To Update -- strCampaign_Outcome
- Value To Insert -- Outcome 1[-X-]Number of attempts[-Y-]Outcome 2[-X-]Number of attempts[-Y-]Outcome 3[-X-]Number of attempts[-Y-]
- Field To Match On -- intCampaign_Id
- Value To Match With -- This is the id of the form that you wish to reset the contact queue for
5 Full Rule Layout
MetaData Rule[[-SEP-]]DB Table Name[[-SEP-]]Field To Update[[-SEP-]]Value To Insert[[-SEP-]]Field To Match On[[-SEP-]]Value To Match With[[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]]
6 Full Example Rule
CrossDatabase_Update_Simple[[-SEP-]]campaign[[-SEP-]]strCampaign_Outcome[[-SEP-]]Outcome 1[-X-]1[-Y-]Outcome 2[-X-]1[-Y-]Outcome 3[-X-]1[-Y-]Outcome 4[-X-]3[-Y-]Outcome 5[-X-]2[-Y-]Outcome 6[-X-]1[-Y-][[-SEP-]]intCampaign_Id[[-SEP-]]1[[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]]
7 Rule Details
When this MetaData rule is executed the current outbound record stack will be removed, this will not affect the data in the records. The Metadata rule will then insert the new call stack(Parameter 5 in the rule).
Parameter 5 is broken down into the following way Outcome 1[-X-]Number of attempts[-Y-]Outcome 2[-X-]Number of attempts[-Y-]. The outcomes that are mentioned in the rule must be exact otherwise bxp will not add the records to the call stack.
The best way to get the exact wording of the outcome is to copy and paste it out of the edit an outcome page in bxp ( Main Menu --> Form Management --> Form - Outbound Manager --> Outcome - Edit ).
Once the MetaData rule has finished executing the outbound record stack will be updated to the new order that MetaData program was instructed to set it to, to view the new outbound record stack navigate to the following system location
Main Menu --> Outbound --> Queue Management --> View Contact Queue.
Any agent that is then performing outbound calls will be presented with records from the database that are a part of the outcome(s) and number of attempts group that is currently been working on