Login Page Editing
In the agent browser, login occurs via a special script called _sysLogin. This page is one of several system scripts that are governed by particular editing rules: generally, the visual appearance of the page may be changed, but not it's structure and identity.
Editing visual appearance
In this category are, for example:
- position
- width / height
- colours
- images
For all system scripts, any visual appearance items can be changed freely, although you must test the changes on a test Scripter tenant, before deploying to a live production tenant. In this case the script writer should ensure that usability is not impaired. e.g. buttons too small, missing image file, button positioned so it is not visible on the page, etc.
Editing structure and identity
In this category are, for example:
- Flow chart
- step usage and flow
- Screen layout
- container element type. e.g. Grid, TextBlock, Button
- element names (IDs). e.g. x:Name="Question" or Name="Question"
- localized text IDs. e.g. loc:Lookup.Uid="AcceptCalls_lblTakeCalls"
- named references to 'master' page (heading page). e.g. sxaml:StepContainer.MasterPage="Screens.Master3"
- XML namespace definitions and references to assemblies (DLLs). e.g. xmlns:sxaml="clr-namespace:ScripterXAML;assembly=ScripterXAML"
The freedom to edit structure and identity varies between system scripts, as follows:
| Script | Comment |
|---|---|
| _sysLogin | The engine has particular dependencies in this areas of structure and identity and so these items may only be changed by Sytel or after consultation with Sytel. If changes are made in these areas, it is likely that either the engine will not start, or the login process is broken and the agent can no longer log in. The _sysLogin script in particular should not be loaded by Scripter Designer because it will modify the flow chart structure in a way that will break the login script. To edit the _sysLogin script screens, you should either
|
| _sysDefaultIvrAgentScript
_sysDefaultLiveAgentScript |
You are free to make changes |
| _sysAdhocCallAgentScript | Please consult Sytel before making any changes |
Other Do's and Don'ts:
- Don't add additional steps to the flow chart
- Don't change the root element of a screen layout
- Additional elements may be added to a screen layout for appearance only
- Don't add any outcome/ image buttons
Using the Scripter Screen Editor
The text displayed on the login page controls can be modified by the localisation if required. If localisation exists for any elements on the page, this will override the text in the XAML file.
For elements that are not localised the easiest way to modify the login script is to use the Scripter Screen Editor directly, but you must run it in a slightly different way. When launched outside of Scripter Designer, it must be run from the same path as where the script resides, otherwise it will not pick up the images.
To launch Scripter Screen Editor in the _sysLogin script directory:
- First create a copy of the Scripter _sysLogin folder to work on. For example:
- Copy from C:\Softdial\Scripter2\Engin e\Scripts\_sysLogin to C:\Softdial\Scripter2\Engine\Scripts\_sysLoginEdit
- Run command prompt; Start> Run> cmd
- Change directory to the copy made in step 1, e.g. C: cd C:\Softdial\Scripter2\Engine\Scripts\_sysLoginEdit
- Run the Screen Editor ..\..\..\Designer\ScripterVisualStepTool.exe
- Open and edit the screen. You must stick to the following rules
- You may
- change colours, sizes and positions
- add new controls
- You may not
- delete any label, text entry, selection or button control
- change the Name of any of the above control types
Localization of labels is already pre-configured and performed via a separate mechanism (refer to online documentation)
- You may
- When happy with your changes, stop the Scripter Engine service for the tenant
- When the Scripter Engine service is stopped, copy the _sysLoginEdit folder to C:\Softdial\Scripter2\Engine\<tenant>\Scripts\_sysLogin
- Restart the Scripter Engine service and test