• Contents


Interaction Scripter 2018 R5

Updated Example 2 on the IS_Action_Record page for use with snippet recordings by including "IS_Action_Record.callid = IS_Attr_CallId.value;" in the Record() function.

The Sample Interaction Connect scripts now include a new multi-page custom script that demonstrates some of the key actions and events you can use when writing a custom script in Interaction Scripter.

You must now specify a callback function when using IS_Action_PlaceChat, in order to ensure that script execution doesn't proceed until the chat is fully initialized. The second sample script has been updated to reflect this.

Interaction Scripter 2018 R4

Scripter 2018 R3 documentation  incorrectly described a Boolean parameter of the IS_Action_CallComplete action. The name of the parameter is makefollowupcall, not makeadditionalfollowupcall. Documentation was corrected.

Interaction Scripter 2018 R3

  1. Interaction Connect now supports custom outbound scripts. Starting with PureConnect 2018 R3, call center agents can use Interaction Connect to process outbound Dialer calls with custom script screen pops. Previously, Interaction Connect supported base scripts only. Agents were required to use Interaction Scripter .NET client for campaigns with custom scripts. To use Interaction Connect instead, custom scripts must conform with new programming requirements.

    Interaction Connect processes JavaScript asynchronously, breaking tasks into threads that execute independently. Conversely, Interaction Scripter .NET is synchronous. It waits for each script statement to finish before moving to the next. For this reason, Interaction Connect and Scripter .NET have divergent programming requirements.

    • Custom scripts must be written for one client or the other.

    • The same custom script cannot be used in both Scripter .NET and Interaction Connect.

    • Legacy scripts written for Interaction Scripter .NET work as before in that client application.

    • To be compatible with Interaction Connect, scripts must implement callback functions that indicate when asynchronous operations complete.

    • Scripts written for Scripter .NET should not implement callbacks designed for Connect.

    For more information, see Writing custom scripts for Interaction Connect or Scripter .NET, Sample Interaction Connect scripts, and Sample ICWS Dialer Web Application.

  2. IS_Action_CallComplete has a new Boolean parameter named MakeFollowUpCall. It indicates whether the user should be put into "Additional Follow Up status", in support of a feature that allows an agent to dial additional calls while in that status.

  3. The IS_ActioStartReceivingCalls action now accepts an optional new campaign attribute, containing a comma-separated list of campaign names for the Dialer agent to receive calls from.

  4. IS_Event_ManualOutboundCallStatus has updated arguments. Status now returns a code number corresponding to StatusName, a new attribute that returns the status string.

  5. The ConferenceObject.subObjectChangedHandler callback now has two parameters instead of three.

  6. Documented a new event: IS_Event_PreviewCallSkipped is raised when a preview call is successfully skipped.

  7. Added a new standard action: IS_Action_CompleteConsult. This action ends a consult call in scripts for Interaction Connect only.

  8. Updated IS_Action_Transfer to add an "audience" parameter. This new parameter is used only with scripts for Interaction Connect.

  9. Documented capitalization conventions to use when writing scripts.

  10. A new action, IS_Action_QueryContactList queries a specified contact list for records.

  11. Two  conference object callbacks were added for use in scripts for Interaction Connect. ConferenceObject.conferenceObjectInitializedHandler is invoked when the conference object has initialized. ConferenceObject.conferenceStartedHandler is invoked when the conference call has started.

  12. A new ChatObject.messages property returns an array of messages about a chat interaction after the chat object has been initialized.

  13. A new ChatObject.sendChatMessage method sends a chat message to the remote party on behalf of the current user.

  14. A new ChatObject.messages property of a chatObject returns an array of messages of that chat  interaction after the chatObject had been initialized.

  15. The ChatObject.SubObjectChangeHandler can now be an assigned callback that gets alerted with new messages when the chat Interaction receives new messages.

  16. A new CallObject.currentDialerCallId method returns the Id of the current active dialer interaction. This can be used to set a CallObject's id to initialize it with the current active dialer call.

  17. A new dialer.sendCustomHandlerNotification method initiates custom handlers through the custom notification initiator.

  18. A new dialer.subscribeToCustomHandlerNotification method  allows a custom script to asynchronously subscribe and listen to a Send custom notification step in a custom handler.

  19. Fixed a bug that could prevent an agent in Available, Forward status from entering a phone number or optional notes while using a custom script.

  20. Added a note to IS_Action_PlayWav. For custom scripts in Scripter Connect, the wav file specified for the IS_Action_PlayWav action must be located in the Resource Path directory on the CIC server (I3\IC\Resources by default).

  21. Interaction Connect now allows agents executing a base script  to change their user status when  they are not involved in a Dialer interaction. Agents can change their status before logging into a campaign, or while on break.

  22. A new action, IS_Action_PlaceChat initializes a chat between the current user and another user.

  23. A new action, IS_Action_PlaceChat initializes a chat between the current user and another user. When the chat is initialized, a new IS_Event_ChatInitialized event is emitted. Your scripts should listen for this event to ensure that they do not proceed until the chat is fully initialized.

  24. The ConferenceObject.create method now has 1 or 2 input parameters, depending upon whether the script will run in Scripter .NET or Interaction Connect. To create a conference in an Interaction Connect script, two interaction id's must be passed to this method. Scripter .NET requires a single interaction ID to be passed.

  25. The Queue object for custom scripts in Connect now deviates from Scripter.NET in a couple of ways.

  26. Similarly, the User object is programmed differently for Connect scripts:

  27. Noted in the Interaction Scripter Actions topic that a few actions should be used with care, since they potentially affect the performance of a script or server. Actions marked as having scale impact include:

Interaction Scripter 2018 R2

  • A new meta tag allows a script to show or hide the command toolbar. See Why is the META tag used?

  • Revised Example 2 in IS_Action_Transfer to correct a misspelled method name. The line onclick="IS_BlindTransferl(‘101') is now onclick="IS_BlindTransfer(‘101').

  • Revised IS_Action_Listen to state that CallID is a required attribute. Also updated code samples in that topic.

  • Updated the IS_Actions_ClientStatus topic to ensure that only default statuses are listed, and that the case of statuses matches CIC default status names in PureConnect .

Interaction Scripter 2017 R4

  • Improved appearance of code listings and topics in this document.

  • Updated Copyright and Trademark Information.

  • Applied Genesys terminology.

Interaction Scripter 2017 R1

Interaction Scripter 2016 R4

  • The IS_Action_Exit Standard Action has a new attribute that provides you with ability to exit Dialer as well as Scripter.

Interaction Scripter 2016 R3

  • The IS_Action_LogonAll Predictive Action is a new action that can globally log an agent into Dialer as well as all currently running campaigns.

Interaction Scripter 2016 R2

  • The IS_Attr_CampaignGroup Predictive Attribute can now provide the name of the active Campaign Group in the Campaign Sequence that is currently running when using the Advanced Campaign Management feature.

  • You can learn more about this new feature in the Advanced Campaign Management for Interaction Dialer - Overview Guide, which is available in the Interaction Dialer section of the CIC Documentation Library.

Interaction Scripter 2016 R1

  • Updated documentation and screen shots to reflect new logo and color scheme.

Interaction Scripter 2015 R4

  • No revisions were made to this document for R4.

Interaction Scripter 2015 R3

  • Updated various topics with code examples

Interaction Scripter 2015 R2

  1. Added two new methods that can be used to prevent sensitive information from being recorded:

  2. CallObject.pauseSecureRecord - This method can be used to pause recording.

  3. CallObject.resumeSecureRecord - This method resumes recording.

  4. Added information to the PreviewTimeout Events topic that pertains to the new Manual Calling feature.

  5. Added clarification that the IS_Action_CallComplete does not disconnect the call.

  6. Updated the IS_Action_StartReceivingCalls Predictive action topic with information pertaining to the use of the Dialer StartReceivingCalls Per Campaign server parameter.

  7. Added more details about using the Interaction Scripter Debugger.

Interaction Scripter 2015 R1

  1. Updated documentation to reflect changes required in the transition from version 4.0 SU# to Interaction Dialer 2015 R1, such as updates to product version numbers, system requirements, installation procedures, references to Interactive Intelligence Product Information site URLs, and copyright and trademark information.

  2. Added three new PreviewTimeout Events, which are Predictive Events that are specifically designed for use with Preview campaigns that use a preview countdown timer.

Interaction Scripter 4.0 Service Update 3

  1. Added scripterNotiferName property. It returns the machine name of the server that the agent is currently logged into.

  2. Added campaignsChangedHandler callback property, invoked whenever a user is logged into or out of a campaign.

  3. Added a campaign object with properties that encapsulate the Name, ID and Status of a Dialer campaign.

  4. Added User.startAvailableCampaignObjectEnum Property to the User object. This property returns an enumeration of accessible queues that current agent has rights to view and modify.

  5. Added a new element to the Scripter environment called Behaviors. At this time there is only one Predictive Behavior called IS_Bhvr_SuppressToast.

  6. Custom scripts can now stream audio files from the ODS server by specifying http or https URI's.

Interaction Scripter 4.0 Service Update 2

No revisions were made to this document for SU2.

Interaction Scripter 4.0 Service Update 1

The IS_Action_Logon action no longer requires an agent type attribute. Since agent type can only be set for the agent's entire Dialer session and not per campaign, it no longer makes sense to specify it on this action.

Interaction Scripter 4.0

  1. Interaction Scripter's reason code based call completion actions were reworked for Dialer 4.0. The following actions were removed from the documentation because they are now deprecated:


    These actions were replaced by one new action, IS_Action_CallComplete, which should be used to disposition calls. It requires an attribute named wrapupcode that contains the wrap up code to be used when dispositioning the call. It supports a Boolean attribute named abandoned which indicates whether the call should be classified as abandoned. In addition, IS_Action_CallComplete supports all of the schedule-based attributes that the old IS_Action_Schedule action supported.

    The old actions are deprecated, but they are still functional. Existing customer scripts developed for Scripter 3.0 will not be broken. Old actions will generate debug entries when Scripter is run with the /debug flag. Legacy actions must use appropriate system-defined wrap up codes and ignore the wrapupcode attribute on the element (DIALER-6108).

  2. IS_Action_FullScreen was removed because the application framework that Scripter Client now runs in does not support full screen mode at this time (DIALER-4205).

  3. Interaction Dialer no longer supports workflows. Instead, it allows multiple campaigns to run at the same time. For this reason, two workflow-related attributes are no longer supported, even in legacy scripts. The removed attributes are IS_Attr_WorkflowId, which contained the name of the workflow that a campaign object belonged to, and IS_Attr_WorkflowUUID, which contained the id number of the workflow. A third attribute, IS_Attr_CampaignUUID was also deprecated. It contained the campaign ID. It is replaced by a new IS_Attr_CampaignID attribute. In Dialer 4, customers should use these attributes instead of deprecated attributes (DIALER-6214):

    • IS_Attr_CampaignName is a new attribute which contains the campaign name.

    • IS_Attr_CampaignID now contains the campaign ID. In earlier releases, it contained the campaign name.

  4. Two predictive "NonDialerCallScripting" actions are now used to delay closing a script when the agent has logged out of all the campaigns that the script is associated with (DIALER-6594).

    • IS_Action_BeginNonDialerCallScripting prevents the agent from being logged out of one campaign and into another while the agent is on a non-Dialer call. Automatic campaign login will be delayed until the agent ends the non-dialer call.

    • IS_Action_EndNonDialerCallScripting tells Scripter to resume automatic login of an Agent to a new campaign after transitioning was delayed by IS_Action_BeginNonDialerCallScripting.

  5. IS_Action_RequestLogoff now accepts an optional campaigns attribute, which can be used to request a logout for specific campaigns. If that attribute is not populated, then the action requests a logout for all campaigns. The format of the attribute is a list of campaign names separated by commas.