Contactplan Changelog

Version 1.14.1 (2018/08/02)

Main new features

  • no changes

Bug fixes and Enhancements

  • Fixed incorrect behavior that in some scenarios may persisted numeric values in the UI even after deleting them
  • Fixed incorrect behavior related to Digital Message rule. When changing the value in “Action” selection it did not clean correctly previous conditions in the UI
  • Fixed incorrect visualization of date and hour in “Logs” lists
  • Fixed incorrect visualization of tooltips in plan list that could cause problems in using the UI

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.14 (2018/07/24)

Main new features

  • In segment tab, now it is possible to search segment by name. Partial match is supported.
  • Drop-down menu now support search: as you type, only the values containing those text are shown in the drop down. This applies to: configuration selection in user setting; add condition drop-down in segment rule, Timezone selection in Local Settings sub-tab and in Choose field in Field Setting sub-tab

Bug fixes and Enhancements

  • Fixed incorrect behavior when selection options in drop-down multiple selection input preventing “mouse click” to select a value
  • Fixed incorrect behavior in plan creation using Firefox as browser
  • Fixed incorrect UI behavior in opening/editing existing segments with condition on bitmask attributes

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.13 (2018/07/16)

Main new features

  • The Search tab has been added to the plan lists. It is now possible to search all the plans according to the plan name or to the segment name used in the plan. In both cases just a short portion of the name can be ebough for the research
  • GDPR: right to rectification, It has been added in the UI only for those who have a DPO role the possibility to search all the materialized lists containing a customer and eventually remove that customer from one or more lists, without any other impact on plans and target lists.

Bug fixes and Enhancements

  • Fixed incorrect behavior preventing plan target date to be correctly saved
  • Fixed incorrect behavior in visualizing a recurrent plan in UI
  • Fixed incorrect behavior in visualizing the action selected for the plan
  • Fixed incorrect behavior in segments creation

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.12.1 (2018/07/05)

Main new features

  • Availability of the results of the Static eEmail Engagement and the Dynamic Email Engagement algorithm from Data. It can be found in the “Insight Rule” area of Data and used in case of segmentation. 

Bug fixes and Enhancements

  • Fixed incorrect behavior when retrieving information from Contactdata
  • Fixed incorrect UI behavior with Firefox when selection placeholder for email personalization when Flow is selected as target action for a plan

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.6.0 (2018/06/18)

Main new features

  • Contact cancelation from materialized lists in Send
  • Contact cancelation from the selection slot without any change in the materialized lists

Bug fixes and Enhancements

  • no changes

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.5.0-984 (2018/06/07)

Main new features

  • Added DIGITAL-STATS

Bug fixes and Enhancements

  • no changes

API changes (backward compatible)

  • Segments research
  • Plans research
  • Oblivion request management

API changes (not backward compatible)

  • no changes

Version 1.11.00 (2018/05/22)

Main new features

  • It is now possible to manage the combined segments also in the edit phase. It is also possible to display the single segments which compose every combined segment.

Bug fixes and Enhancements

  • no changes

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.9.25 (2018/03/21)

Main new features

  • [UI] Online support chat now available directly in Contactplan UI
  • [UI] As new events serviceSubscribed and serviceUnsubscribed will be exported from Contacthub, it will be possible to use them in Contactplan to create segments

Bug fixes and Enhancements

  • [UI] Fixed uncorrect behaviour related to timeframe condition in event rule
  • [UI] Fixed uncorrect visualization of plans in the calendar view
  • [UI] Fixed uncorrect request to count available contacts for a plans from the list view
  • [API] Contactplan is ready to export the available contacts of a plan into an automation

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.9.7 (2017/12/04)

Main new features

  • New time zone management: The time zone can now be expressed as, for example, ‘Europe/Rome’, a form that includes both the time zone and the geographical region in a single plan setting. This also enables automatic daylight-saving management.
  • Improved Contacthub and Contactplan integration: Product classifications are now shown as multi-selection checkboxes next to the ‘product classification 1’ field. As a result, you can select contacts that have or haven’t purchased a product with any of the chosen product classifications.

Bug fixes and Enhancements

  • Optimization of API calls from the UI to get information about the delivery IDs and filter IDs related to plans. Calls are now only carried out when applicable
  • Loading contact data from Contactsend: Data is read from the master database if the slave has not been aligned for more than a configurable threshold.

Internal

  • Added custom header to API calls generated from the UI.

Version 1.9.0 (2017/10/19)

Main new features

  • Admin users can now delete all events stored in Contactplan independently, according to their type or category. For example, Admin users can delete all ‘purchase’ or ‘have an order line’ events. This applies to all events types, except ‘Digital Messages’. This is particularly useful when you need to redo a data ingestion in Contactplan, or in Contacthub with the data synchronized in Contactplan, for whatever reason.
  • For Customers that use Contacthub, all values inserted in the ‘tags-auto’ and ‘tags-manual’ arrays are now available for segmentation in Contactplan individually, instead of being shown as a pipe-separated string of values.

Bug fixes and Enhancements

  • The Calendar view in Contactplan has been improved. Now it loads faster, while all plans with a target date that appears in the Calendar view, are displayed correctly, regardless of their status (Ready, Draft, Error, Archive).
  • Fixed incorrect behavior related to correlation-based queries.
  • Fixed incorrect behavior related to test emails when using the ‘write your own list’ option in the create new delivery wizard. Now all test emails are sent correctly.
  • Fixed incorrect behavior that, in particular scenarios, was preventing correct execution of an Action associated with a given plan. For example, creating a filter in Contactsend.

Internal

  • The Remote-IP has been added to the response log.
  • The error message when FTP credentials are wrong has been improved.
  • The incorrect behavior, when a Web browsing event is configured in Contactplan from Contactlab administrative tool, has been fixed.

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.8.0 (2017/10/04)

Main new features

  • Display the state of the UserDB that is associated with Contactplan. If the DB is locked, it appears orange, if it is unlocked, it is green, if it is unrecoverable, it is black.
  • An ‘Info’ icon has been added to the Plans list. It opens a window that provides the ID and name of the filter created as part of a plan, together with the ID, name and state of deliveries associated with the filter.
  • Information about the ID and name of the filter created as part of a plan, together with the ID and name and state of deliveries associated with the filter are displayed when a plan is opened.
  • A ‘Clone’ action has been added for Archived plans, enabling new, pre-compiled plans to be generated, which use the same data as the parent.
  • Delete or Reopen operations are automatically unavailable, when a plan is associated with an ongoing or completed delivery.

Bug fixes and Enhancements

  • Resolution of the Zendesk 15887 ticket (appropriate management of in-delivery emoticons created from Contactplan).
  • Correct management of special types in the attribute value lists displayed in the UI.
  • Resolution of the Zendesk 15697 ticket (abnormal errors in DND policy creation).
  • Improved uploading and display of test filters within the delivery creation wizard.
  • The inappropriate management of test email deliveries from and existing filter has been resolved.
  • Introduction of displaying information about test deliveries in the UI.
  • Improved management of UI input type definitions, according to attribute cardinality.

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.7.6 (2017/09/27)

Main new features

  • no changes

Bug fixes and Enhancements

  • [UI] Fixed missing creation of a correlation-based query in the UI.

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.7.2 (2017/09/14)

Main new features

  • [UI] When you create or modify a segment rule, a green alert shows the new enhanced conditions.
  • [UI] Upload feedback. In the Logs section of Contactplan, the results of personal data and event uploads are available.
  • [CONTACTHUB INTEGRATION] Integration of Arrangement Web Browsing events from Contacthub. Events will be available once the export to Contactplan is implemented in Contacthub.

Bug fixes and Enhancements

  • [UI] In the Dashboards, the diagrams are uploaded separately as soon as the data is available, reducing the required imaging time.
  • [API] Resolution of the Zendesk 14776 ticket regarding the incorrect upload of “sent email” events when the email is in a “not final” status.
  • [UI] Support for opaque token authentication.
  • [UI] Display lists in the drop-down menu for segment choice in alphabetical order.
  • [API] Metadata update for the new Contacthub field for bought event and Product description.

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.7 (2017/08/02)

Main new features

  • [UI and API] In the segment refinements section, you can now select the Top or Least N contacts, according to the number of purchases.
  • [UI and API] If you delete or reopen a plan, the system will now archive both the filter and any associated campaign that has been created in Contactsend.

Bug fixes and Enhancements

  • [UI] fixed minor issues related to UI components

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.6 (2017/07/18)

Main new features

  • [UI and API]: Selection of the first or last N contacts, based on purchases made within a given timeframe, or from a certain date, is now available in the segment Refinement conditions. For example, you can select the top 10 contacts who made a purchase last week, or from day ‘X, such as the launch date of a new product or campaign.
  • [API]: Optimization of the Lifecycle Management Mechanism for List Generation, Filter Builder, or Send Campaign plans, as well as FTP File delivery and Error Handling.
  • Improved scheduling of plans with the same execution time, enhanced rollback management in the event of errors, and optimized management of changes during the scheduling phases.
  • [UI and API] The query mechanism for available event condition thresholds (mail, purchases and similar) has been optimized. This query allows you to select contacts for whom a specific event represents more (or less) than a percentage threshold, when compared to any other event in that category. For example, the selection of contacts for whom the purchase of premium products with a value over €100 represents more than 50% of all their purchases.
  • [UI and API] In some scenarios, the segment complexity can reach levels that cause product performance deterioration for all users. To prevent excessive performance degradation, a limit of 10 rules per segment has been introduced.

Bug fixes and Enhancements

  • [UI] The abnormal behavior in counts, which is displayed during timeframe editing within a Refinements rule, has been fixed.
  • [API] The abnormal management of recurring plans, which made it impossible to edit individual instances of a plan, has been fixed.
  • [UI] The incorrect management of user log-in information that is entered while signing in, which in some scenarios, results in user authentication problems, has been fixed.
  • [DATA LOADER] The incorrect generation of a rejected log file, which randomly made the log file unavailable on the ftp server, has been fixed.

API changes (backward compatible)

  • The new metric to select the top (or the lowest) users by purchase date, has been added to the description of segment queries.

API changes (not backward compatible)

  • no changes

Version 1.5 (2017/05/30)

Main new features

  • [HUB INTEGRATION] Retails events loaded in Contacthub are now available in Contactplan for segmentation. Retail events are, e.g., having invited customer to catwalk or cocktail or other show; customers have accepted or declined invitation; customers showed up at the event and so on.
  • [UI and API] new Top / Least N query available. This query type allows to get the Top or Least N contacts (where N is freely configurable) according a predefined metrics. First released metric is overall spending level
  • [UI] Introduced paginated lists for plans and segments. you can select how many elements are shown per single page
  • [PLUGIN] Primary key composed by multiple fields can now be configured for orders and order_lines external files
  • [PLUGIN] New log generated after ingestion with information about lines rejected because duplicated

Bug fixes and Enhancements

  • [API] fixed wrong check between offset for list generation and recurrent startDate and recurrence rule
  • [API] fixed wrong behaviour when a running recurrent plan is stopped, transformer to a one shot plan, saved and then transformed again to a recurrent plan

API changes (backward compatible)

  • [API] call to ask for counting contacts satisfying a given query can now be done using POST and passing the query in the body instead of using GET with query json as query string parameter. This avoids errors due to browser or proxy truncating the query string

API changes (not backward compatible)

  • no changes

Version 1.4.7 (2017/04/20)

Main new features

  • [PLUGIN] Further improvement in loading and processing time for new behavioral data to be loaded in Contactplan such as digital messages and purchases data. Overall ingestion process will now take less time to make new data available.
  • [UI] Now you can modify the label shown in UI for any fields available for segmentation including fields related to events dimensions such as product and store information
  • [UI] Recalling Pagebuilder templates when you are creating your delivery in Contactplan is now faster. Even in case of Pagebuilder with many folders and folders with many templates
  • [CONFIG] When creating a new Contactplan configuration, we automatically provided usable label and field setting to minimize manual configuration effort

Bug fixes and Enhancements

  • [UI] Fixed date handling in Timeframe field of Digital Messages and Purchase Rules
  • [API] Improved internal event handler schedule in case of cuncorrent access
  • [PLUGIN] Fixed issue in Delivery Label loading for Digital Messages events
  • [UI] Fixed start/stop of recurrent plan from UI
  • [UI] Fixed wrong behaviour when showing total number of contacts inside plan’s materialized list

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.4.6 (2017/04/04)

Main new features

  • [UI] now company Id (groupPk) and userdbId are shown in Plan UI.
  • [UI] when creating a Campaign from Contactplan, i.e. at the end of a Plan, the CLAB Campaign Creator action is selected, you can choose whether to remove duplicated email addresses or not. Note that removal of duplicated email address is performed by Contactsend at the time of delivery
  • [UI] French version of UI is now available. To access French version of UI, select FR as language in login page

Bug fixes and Enhancements

  • [PLUGIN] fixed minor issues on automatic detection of modification of data type when importing demographic data from Send userdb
  • [PLUGIN] improved blueprint used when creating a new tenant in Contactplan to minimize further configurations from UI
  • [UI] completed automatic localization of UI components for IT, EN and FR languages
  • [UI] enhancements in API call for counting available contacts when creating/editing complex segments
  • [UI] improved handling of Calendar component
  • [API] fixed issues related to Pause / Re-Start of recurrent plans (avoid to create a new drop of the recurrence with same name of an already performed drop)

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.4 (2017/03/08)

Main new features

  • [CONTACTHUB INTEGRATION] Behavioral events stored in Contacthub related to what your customers have done on your eCommerce are now available in Contactplan for segmentation and targeting purposes. E.g. you can create an audience of all contacts having placed books or dvds in the whishlist in the last week. The new behavioral events are: View product category, View product, wrote product review, placed product in whishlist, removed product from wishlist, placed product in cart, removed product from cart, has abandoned cart, has completed order
  • [PLUGIN] Data loading process for demographic and behavioral data have been improved removing unnecessary idle time and speeding up the whole process
  • [CONSUMER FTP] in case the FTP consumer is selected as the final action of a Plan, now you can select the field separator (comma, semi-colon, pipe and tab) and the field enclosure (quote, double quote, no quote) to be used in the csv file saved in the external FTP.
  • [UI SETTING] from Setting > Field setting is now possible to set the input type (checkbox, multi-option, auto-complete, free-text) that will be used in UI to select value for the given field while creating segment

Bug fixes and Enhancements

  • [API] improved overall performance when several different plans are scheduled for the same target date & hour
  • [UI] - empty string - value is now correctly shown in all input type together with the other values of the field
  • [PLUGIN] added new error case in rejection log of data loading process

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.3 (2017/02/01)

Main new features

  • [UI and API] new attributes available in Digital Messages rule for segmentation. Now you can select contacts that have received / viewed / clicked deliveries with a given delivery Main Sector and/or a delivery Secondary Main Sector. Such sectors can be associated to delivery at the end of the creation wizard in Send. Exmaple given: you can now select contacts having viewed a delivery with Main Sector Finance
  • [PLUGIN] Data loading plugins have been refactored ensuring increased reliability and scalability in loading data and events from Contactsend, Contacthub or other sources. Ground is set for further enhancements aimed to increase overall performance.

Bug fixes and Enhancements

  • [UI] Fixed several minor bugs in Reports and Segment section to ensure better user experience

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.2 (2016/12/21)

Main new features

  • [UI and API] new error notification on UI related to failure in interaction with Send (apply when using CLAB Filter Creator or CLAB Campaign Creator consumer in Plans)
  • [UI] new operator NOT LIKE introduced for string fields (so now you can search for contacts having “email NOT LIKE @gmail.com”)
  • [UI] field with auto-complete input type (e.g. subject), now support LIKE and NOT LIKE (so now you can search for contacts having “opened delivery with subject LIKE Hotel” )
  • [API] bitmask fields (integer and bit string) can now be configured from API
  • [UI+API] when creating a new delivery in Plan, it is now possible to add Alternative Text and Label.

Bug fixes and Enhancements

  • [PLUGIN] Optimized loading data process using cluster
  • [PLUGIN] Optimized configuration process for new tenants
  • [UI] Improved handling of date and timeframe conditions
  • [API] Improved handling of conditions with relative date, now more accurate results are returned
  • [UI and API] improved Single Sign On behavior, if you logout from other CLAB Application such as Send, UI shows correctly the logout in Plan too (just like, e.g. Google eco-system)
  • [UI] solved some glitches in editing existing rules and segments

API changes (backward compatible)

  • GET /notifications/errors: new endpoint to retrieve errors occured while interacting with Send for filter or delivery creation
  • POST, DELETE, GET, PUT /models/contacts/attributes/{attributeName}/lov: this endpoint allows handling the list of values of the given attribute

API changes (not backward compatible)

  • no changes

Version 1.1 (2016/11/02)

Main new features

  • Purchases events loaded in Contacthub will be available automatically in Contactplan for segmentation within 24h
  • New segmentation field available Link Category Name
  • Archived Plans can now be re-opened or deleted by user with role of ADMIN
  • Retrieve HTML pages created with PageBuilder in case delivery is created in Contactplan
  • Contactlab link tracking for link with no dynamic parameters is automatically enabled when delivery is created in Contactplan

Bug fixes and Enhancements

  • Retry mechanism when creating scheduled delivery in Contactsend in case database is locked
  • UI visualization glitches fixed
  • Contact list download works now normally even for user with more than 20 associated databases
  • URL-Safe Base64 decoding works properly even in case special char are used

API changes (backward compatible)

  • GET /extContents/pagebuilderTemplates: new endpoint to retrieve templates folder created in PageBuilder
  • GET /extContents/pagebuilderTemplates/{templateID}/pages: new endpoint to retrieve html pages associated to a given template
  • POST, PUT, GET /jobs: in case CLAB Campaign Creator consumer is selected, now it is possibile to insert alternative text and notes associated to the campaign

API changes (not backward compatible)

  • no changes

Version 1.0.9 (2016/10/13)

Main new features

  • resource pool configuration to avoid a slow down of the system perfomance while ingesting/updating data
  • custom ingestion plugin for specific migration scenario
  • retry mechanism for authentication/authorization to avoid pending request
  • X-header-id to help tracking of request cross-application
  • optimized calls to retrieve the database on which the user is enabled

Bug fixes and Enhancements

  • Fixing problem when updating consumer from configuration service (internal procedure)
  • Fixing problem when deleting dashboard cache (internal procedure)
  • Fixing handling “Create Plan” procedure in specific scenario for user with “User” role
  • Fixing problem in “bubble maps” graph in UI
  • Fixing missing translation in UI

API changes (backward compatible)

  • no changes

API changes (not backward compatible)

  • no changes

Version 1.0 (2016/09/22)

Main new features

  • Conditions to define the number of contacts selected for a given plan: users can set the exact number of contacts to be selected for a plan, the minimum or maximum number, or a range within which the number of contacts should fall. Users can also define what the system should do if the required number is not reached, for example, execute the plan anyway, flag the plan as an error, or add random contacts to reach the desired number.
  • Recurrences: users can now define whether a given plan is to be executed once, or set as a recurring plan. If set as recurring, users can set the recurrence rule.
  • Dashboards: provide visual feedback of important statistics, both for the whole database and for a single segment.
  • Correlation query: users can now express conditions such as “All contacts who bought a product, after having opened the campaign for that product, within (or after) N days”.
  • Segmentation: users can now create a new segment by combining existing segments.
  • Segmentation setting: admin users can now define the fields in the database that are available for segmentation, which fields have to be shown by default when creating a new rule, the label to be used at UI level, and force a list of values to be refreshed.
  • Reports: provide information about executed plans, including feedback for campaigns delivered through Contactsend.
  • Supported browser: optimised for Chrome

Bug fixes and enhancements

  • Enhanced logging and monitoring when plans create filters or campaigns in Contactsend, or when plans send contact lists to an SFTP server.
  • Revised wizard for creating new plans.
  • Enhanced load procedures for purchase data from external files.

API changes (backward compatible)

  • /plans/recurrences: new endpoint to create a recurrent plan. It supports POST, PUT, GET, delete.
  • POST, PUT, GET /plans: optional information added regarding conditions for exact, minimum or maximum required contacts for a plan.
  • GET /plans: optional information added regarding recurrence rules. If no rule is applied to the plan, an empty object is returned for this part.
  • POST, PUT /segments/combined: new endpoint to create a new segment by combining existing segments. The GET method for a combined segment returns a json with the same syntax as a “normal” segment.

API changes (not backward compatible)

  • All POST methods now return 201 Created. The body contains the json description of the created resource.