Component scripts no longer customer-specific, and can be accessed from all customers.
4.5.33
Deprecated
Component Scripts Deprecated - scheduled for removal from product
4.5.51
Component Scripts are scripts within scripts. When the component script is changed, the change is reflected in all scripts in which the component is embedded.
There are two main benefits in using Component Scripts:
To minimise the effort in updating scripts with similar content.
Enabling less technical scripters to employ components developed by more technical colleagues.
Features:
The agent will be unaware that they are using a component script. They will simply move on to the next page in a script, which will then display the component script. They then work through the component script and return to the main script page as defined in the advanced properties of the "Button - Component Link"control in the main script.
Multiple component scripts can be used within any master script.
Component scripts can be used in multiple scripts for the same customer (please note - from V4.5.33 they can be accessed across all customers).
For versions pre-4.5.33 component scripts can be copied between customers but will be maintained separately thereafter (please see above bullet point).
Updates to a component script will be reflected in all master scripts that utilise it.
Using fields and variables with the same field name in both the component and the master script will share the data automatically.
Component scripts can be pre-scheduled in the same way as any other script.
Reports can be generated viewing all data in the master and component script (when the master script is selected to generate the report against, all fields from both master and component script appear in the Report Designer).
Limitations
When using data controls in a component script, you can map your returned data to variables and to fields (version 4.5.24+, earlier versions only allow write-back to variables).
You can use more than one component in a master script, but cannot use two consecutively linked components.
If two component scripts are used within the same master script, and both contain an identical field name, the data from the first component will take the value. The second component will not update it.
When a component script is opened it will pre-populate with values of matching fields or variables. When the component is closed the values will update the master script. If a second component script is opened that also shared field/variable names with the master and 1st component, the master script will update with values from the 2nd component, but the 1st component will not update.
Data from component scripts is not available in the Call Manager module - to view this data fields/variables need to be written back to the master script.
Component scripts do not appear in the Outbound Manager (only script types = Outbound do). If an outbound script uses a component script then the fields/values are not visible in the Outbound Manager.
Joined scripts and component scripts cannot be used together. These are separate features, with different functionality. Speak to the Professional Services team for further guidance.
The Shopping Basket control cannot be used in a component script.
There are limitations on SSRS reporting (cannot link from a master to a component script on script ID as a separate ID is created during the component script run). When using multiples components that share the same field name tbl_data can end up with one field name that contains several values. When using component scripts SSRS reports need to be designed accordingly.
Creating Component Scripts
Component scripts are created and built in the same way as any other script. When adding a script, choose Component Script from the script type menu on the script attributes page:
The main difference between component and other script types is that that they do not have wrap and end pages. A component can include as many pages as required.
To include a component script within a main or master script a "Button - Component Link" control is added to the page that you want to jump to your component from.
The contents of Legacy Feature - Component Scripts
