...
Previously, interaction plans in Interaction Plans Architect were associated with a single destination. To use an interaction plan with different destinations, the admin user needed to copy the interaction plan, once for each additional destination. Any time the plan needed to change, the admin user needed to change multiple copies of the plan. In Interaction Plan Mapping, the destination and interaction plan are separate entities; an admin user can map many destinations to one interaction plan.
In Interaction Plan ManagementPlans Manager, an admin user can perform the following tasks:
...
| Panel | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
Destinations
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Using Interaction Plan ManagementPlans Manager, admin users can create, edit, and delete API destinations. Admin users can only edit PSTN destinations; only Vonage can create and delete PSTN destinations.
For information about configuring destinations, see Using Interaction Plan ManagementPlans Manager.
Interaction plans
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Using Interaction Plan ManagementPlans Manager, admin users can create, edit, clone, and delete interaction plans. When an admin user creates an interaction plan in Interaction Plan ManagementPlans Manager, the plan appears also in Interaction Plans Architect. The user can then configure the interaction plan’s applets.
For information about configuring interaction plans in Interaction Plan ManagementPlans Manager, see Using Interaction Plan ManagementPlans Manager.
Mappings
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Using Interaction Plan ManagementPlans Manager, admin users can create, edit, and delete mappings.
For information about configuring mappings, see Using Interaction Plan ManagementPlans Manager.
Data sources
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
In Interaction Plan ManagementPlans Manager, destinations, interaction plans, and mappings can each have up to 20 data sources. The values of the data sources are set on associated interactions before being routed through an interaction plan. Interaction plans can be configured in Interaction Plans Architect to behave differently depending on the values.
...
For information about configuration data sources in destinations, interaction plans, and mappings, see Using Interaction Plan ManagementPlans Manager.
Data source hierarchy
If a single data source is set to different values by a destination and either the mapping, the interaction plan, or both, the value set by the destination takes precedence. If the data source is set to different values by the mapping and interaction plan, the mapping’s value takes precedence.
...
| Note |
|---|
| Applets within an interaction plan can also set data source values. Values set by applets take precedence over values set by the destination, mapping, or interaction plan. |
Example destination, mapping, interaction plans
Production interaction plan
Using the following example:
...
VCC now routes the interaction with four data sources—DS1, DSA, DSM and DSP—through Interaction Plan A’s applets as configured in Interaction Plans Architect.
Testing interaction plan
In this example, the source of the initiated interaction is +449876543210. Interactions from this source are identified as test interactions and therefore go to the testing plan: Interaction Plan B. Interaction Plan B has data sources DS1 and DSP, and sets DSP on the interaction to w.
Migrated interaction plans
If you previously configured interaction plans along with their destinations in Interaction Plans Architect, some of the data from your interaction plans will have been migrated into Interaction Plan Plans Manager. Migration removes destinations from their interaction plans and stores them as separate destination and interaction plan entities. Default mappings are created to reconnect destinations and interaction plans. One interaction plan in Interaction Plans Architect results in one interaction plan, one destination and one mapping in Interaction Plan ManagementPlans Manager.
| Info | ||
|---|---|---|
| ||
Mappings created from migrated interaction plans (known as default mappings) are not visible in Interaction Plan ManagementPlans Manager. Destinations that are associated with a default mapping do not appear to be mapped other than in the list of available destinations when creating or editing a mapping. When creating or editing a mapping, destinations that are mapped by default to the interaction plan it was migrated from are indicated by an icon containing a tilde: Interaction plans that are associated with a default mapping have a status of Mapped. |
Use the following information to identify your migrated interaction plans and destinations. You can still find your interaction plans in Interaction Plan Architect, however, addresses and service names no longer appear.
Entity | Field | Value |
|---|---|---|
Destination | ||
Destination | Line or named route | |
Type | A line in Interaction Plans Architect Line sets Type to “PTSN”. | |
Name | Service name | |
Interaction plan | ||
Reporting group | Service name | |
Name | Line | named route + " - " + service name | |
Mapping | Default mappings created from migrated interaction plans do not appear in Interaction Plan ManagementPlans Manager. | |
| Panel | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
...