The following new properties were added to the clientButton data contract, which affects the 200 HTTP status code response to GET /icws/{sessionId}/configuration/client-buttons, as well as the request for POST /icws/{sessionId}/configuration/client-buttons:

• action - This value indicates whether the button will send a custom notification to a handler, launch an application, or whether no button action was specifed.
• availability - This value indicates whether the button should be available always, only with an active interaction, with any interaction, or whether no availability has been specified.
• buttonText - This is the text that appears on the button.
• deactivateAfterUse - Indicates that the button is disabled after the first use.
• description - This is the description of the button
• displayNotification - Display a notification to the user that the button has been clicked.
• Show More
• enabled - Determines if the button is enabled or not.
• iconUri - The download url for the icon associated with the client button. This is a read only property and can not be changed with PUT or POST operations.
• interactionTypes - The collection of interaction type InteractionTypes enumeration values. These values indicate what interaction types this button applies to.
• localApplication - Indicates the application associated with the action. This is the fully qualified local path to an executable, or a path relative to the local Interaction Client workstation (e.g., C:\Program Files\Interactive Intelligence\application.exe), or a UNC path (e.g., \\hydra\icapplications\application.exe).
• locations - This value indicates at what locations the button will appear.
• Show Less

A new POST /icws/{sessionId}/interactions/{interactionId}/wrap-up-assignments method was added to allow adding wrap-up assignments to a segment of the interaction that received the wrap-up required attribute update.

This release of the Interaction Center supports the following ICWS feature versions. See Versioning for more information about ICWS versioning, including how documentation of an API includes its required feature version and how to query the Interaction Center at run time to determine what feature versions it supports.