Release Notes Tripolis Dialogue

Transcription

1 Release Notes Tripolis Dialogue Version 3.23 September

2 TABLE OF CONTENTS Improvements and features 3 REST API API TImezone support for campaigns 4 Campaign node details in preview 5 Changes to Audit Logs 5 Bug fixes & small improvements 6 Contacts 6 Content 6 Publishing 6 Reports 6 SMS 6 Campaigns 6 2

3 IMPROVEMENTS AND FEATURES REST API API 3.0 In addition to our existing SOAP API service (API 2.0) we have created a Restful API (API 3.0). The schemas for this are available in YAML (for use in swagger compatible code generators such as - highly recommended), JSON and XML (for use in SoapUI for example). Documentation Documentation and examples for debugging and coding for the API 3.0 can be found here: Links to the schema s and the documentation page can be found here: (replace tdxx with the correct instance). Available Methods The following operations are available: - ContactDatabases: GET - Contacts: DELETE - Subscriptions: POST / GET / PATCH ContactDatabases : GET <endpoint url>/contactdatabases - Returns a list of available contact databases, including the contactdatabaseid. GET <endpoint url>/contactdatabases/{contactdatabaseid} - Returns a single contact database record. Contacts: delete <endpoint url>/contactdatabases/{contactdatabaseid}/contacts/{contactid} - Deletes a contact from the database. Subscriptions: POST <endpoint url>/contactdatabases/{contactdatabaseid}/subscriptions - Creates a new contact with field values and group memberships. Optionally updates an existing contact based on key field values by setting updateexisting to true. GET <endpoint url>/contactdatabases/{contactdatabaseid}/subscriptions/{contactid} - Returns subscription details of a contact with field values and contact group memberships, including group membership status (confirmed/unconfirmed). PATCH <endpoint url>/contactdatabases/{contactdatabaseid}/subscriptions/{contactid} - Updates the subscription details (field values, contact group memberships and group membership status) of a contact. 3

4 Authentication Authentication for uses a username + key. The authentication key is user and Client specific and can be generated by assigning an API role to that user and saving it. For users that already have an API role but no key yet, a message Not available yet. Save form to generate a key will show and saving the form will generate the key. A key can be invalidated and then re-generated by checking the appropriate box for it and saving the form: Encrypted ID s visible in the application On the details or edit pages of objects that are often used in API integration we have added a field API id that shows the encrypted ID of the object. This ID can also still be found in the object URL. Timezone support for campaigns It is now possible to create campaigns in a specific timezone. When creating the campaign the user can choose a timezone that will be used for this campaign. The default will be chosen from the user s settings. All timer settings in campaign nodes will be in the selected timezone. We have fixed the bug that existed for every X at HH:MM settings where the user had to recalculate the time to Amsterdam time. All campaign jobs will be published using the timezone of the Campaign. 4

5 Display node details when clicking on a campaign node in the preview Clicking on a node in preview mode of a Campaign definition or run will show a popup with node details. In this way all campaign details can be seen without starting the Java web app. Changes to Audit Logs The Audit logs page in Setup was redesigned to make it easier to extend audit logging in future releases. Additionally, we have added logging for the following operations on Dialogue users: reset password, edit, create and assign. Filters have been added for Field type and Object type. In the audit logs we added columns for Database and Workspace that display the label and show the name on mouse over. Likewise, the Object column shows the labels of the object path (now without the workspace) and a mouse over reveals the names. Old log entries still show the old style Object paths and don t have separate entries for Database and Workspace. 5

6 BUG FIXES AND SMALL IMPROVEMENTS CONTACTS - Contact groups can now be filtered on Group type on the groups list page. - Contact fields are now displayed in the correct order in the list view. CONTENT - The TinyMCE content editor was updated to the latest version. - Changing an article condition for profile to group now works as expected. - The order of picklist items in article fields can now be changed. - Editing a field group doesn t cause an error. PUBLISHING - An alt attribute has been added to the open tracker image ( tracking pixel ) for better delivery and to keep this from coming up when checking an HTML for errors. - Users without publishing rights can now send a Quick Test again. REPORTS - Clicks on links from the trackingxmlimporter are now included in the Summary Report. SMS - We now allow spaces in the SMS originator field. - The link for content preview for SMS communication history was removed. - The default SMS gateway was updates to use the new version of the provider s API. CAMPAIGNS - Campaign timers with every X at Y syntax now correctly use the timezone of the campaign. 6