39 posts tagged with "➕ Added"

• • Added a new protocol called Handover. With this you can have multiple Services connected to 1 Parley account (for example; a Bot Service and an Agent Service).
    More info: https://developers.parley.nu/docs/handover-protocol

• Added the possibility to send "rich" messages, but for this to be used on the Client side we are waiting on the next release for the Client API.
  So Clients can not yet receive these rich messages. However, you can still use this endpoint to send normal messages/images.
  More info: https://api.parley.nu/serviceApi/v2.1/doc/#operation/PostMessages

• Added various Security headers to our responses

Added a setting to enable/disable the "typing" events.​

These events are send to Parley whenever a Client starts typing in the chat window. This way Agents on the other end can see when this Client is typing. The setting is called isTypingEnabled and it's default value is true (so enabled) More info here: https://developers.parley.nu/docs/settings#runoptions

• Added support for OAuth 2.0 authorization for Services
• Added support for custom headers to get send to the Services
• Added a new endpoint to get user information GET /user

• Added new setting, apiVersion, which controls what version of the Client API you are communicating with

Added a new feature which allows you to specify whether these "business hours" are open hours or closed hours.

• Added support for timestamps in the weekdays setting.
• Fixed an issue where "inactive" clients where still making a lot of polling (polling info) requests for new messages.

Timestamps in weekdays​

You can now define your business hours for specific dates using the following format:

window.parleySettings = {
	"weekdays": [
		["Sunday"]
		["Monday", 8.00, 22.00],
		["Tuesday", 8.00, 22.00],
		["Wednesday", 8.00, 22.00],
		["Thursday", 8.00, 22.00],
		["Friday", 8.00, 22.00],
		["Saturday"],
		[1603177200, 1603188000] // Tue Oct 20 2020 09:00:00 - 12:00:00 (GMT+0200)
	]
};

Fixed polling​

The way this worked was, whenever your document has focus (document.hasFocus()), it wil never go past the 30 second rule in the polling rules. This was made so any new messages for an "active" conversation would be retrieved faster. This rule now has been extended to also check if you are within the defined business hours; if you are not, the rule will go past 30 seconds (because the chances you get a response from an Agent is rather small here).

• Added new IP restriction options
• Added api version to api docs

• Changes for the upcoming change in Chrome's REFERER Header. It's now possible to set your own referer value by using the referer param in the PostMessages api call.
• PostDevices now returns a warning when the account, for which this devices get's registered, has no or not working push settings.
• We now return an error when the API has no connection to the Database. Before we only showed a white screen without any information on it.
• We now support CIDR ip ranges and ipv6 in the IP restriction configuration
• Added the following security headers
  • X-XSS-Protection: 1; mode=block Enables XSS filtering. Rather than sanitizing the page, the browser will prevent rendering of the page if an attack is detected.
  • X-Content-Type-Options: nosniff Prevents MIME-sniffing
  • X-Frame-Options: SAMEORIGIN The page can only be displayed in a frame on the same origin as the page itself
• Added the no_access error to the documentation
• Added the api base url to the documentation

• Added a new param when doing POST /messages calls to the API that contains the full url of the current page. Normally this information is found in the referer header, but Chrome is changing the content of this header to contain only the domain of the website you are on. (the API doesn't do anything with this new param yet, we are working on this)
• Fixed a problem where the focus would not automatically go into the chat when reloading the page
• Fixed a problem where the send button was not showing in the chat conversation screen, even though the inviteNotificationSendButton setting was true (due to the naming of the setting this was expected behaviour, but it wasn't very practical to only allow turning this feature on in the inviteNotification screen)

Added

• The notificationLink setting.

Fixed

• Issue where the same notification would show more than 1x
• Issue where sometimes the client window won't open when clicking on a notification
• Issue in IE11 that prevented the chat from starting (document.contains() doesn't exists in IE11, document.body.contains() does)
• Another issue in IE11; Array.from() doesn't exists so i added the core-js es.array.from module polyfill