New features and improvements included in Dynamicweb 8.5.

Release: 26/8-2014
 
Check 8.5 Important notes before upgrade.

SUMMARY

Dynamicweb 8.5 is now ready for download. The headlines for this release are Quotes, Discount matrix, New assortments, Email personalization, Extensive update of items and more than 150 small additions and improvements to existing functionality. In line with our efforts to constantly improve software quality we have fixed over 50 customer reported issues. Dynamicweb 8.5 also contains some exciting Beta features waiting in the wings: Recommendations and Loyalty points.

Marketing
Email Marketing now includes the possibility to personalize your email content for different smart search segments providing you with a full control over who sees what. You can furthermore construct smart searches with recipients that clicked a specific email link. We have implemented bulk send of selected leads from leads management. Average order value statistics are now part of split test reports.  User statistics has been augmented with visits showing all lead details for the selected user. And try out the new SMS module!

Ecommerce
Dynamicweb 8.5 now supports approvable and editable Quotes as a new flow beside standard orders. Assortments have been entirely remodeled and is now a flexible way to show certain products to selected users only. The Discount matrix has been introduced as a powerful tool to specialize the conditions for obtaining a discount similar to what is known from ERP systems. Adding variants to products has received a makeover and will offer new options to the editor.

Content
As usual we maintain a full focus on items and are continually responding to user feedback. Among the more extensive item improvements are field inheritance, named lists and translations. For a complete list please check the release notes. The template translation system is coming in a brand new version making it much easier to handle translations for implementers and editors.

Platform
With 8.5 we have made it very easy for you to upgrade your solution type. For admins it is now possible to edit the license configuration directly from the backend quickly changing the solution from e.g. standard to enterprise. To get a new solution up and running fast we now sport an Install wizard. Dynamicweb 8.5 will support MSSQL 2014. For large scale solutions we now support Content Delivery Network and Load Balancing for improved scalability.

Integration
The integration framework has been extended to support CRM integration with export of lead data and email marketing activities from Dynamicweb. An Excel provider has been included together with the supported providers.  Active Directory integration is coming in a new disconnected version making it possible to synchronize multiple Active Directories to the user database of Dynamicweb while keeping authentication on the AD.

Online Marketing

  • Email Marketing personalization

    Area: E-mail Marketing
    Description:
    It is now possible to personalize email pages to different smart search segments.

    Version: 8.5.0.0
  • Send list of leads

    Area: Lead management
    Description:
    In the potential leads list you can now multiselect leads and send them as email

    Version: 8.5.0.0
  • SMS module

    Area: SMS
    Description:
    SMS module is now part of Email Marketing in Beta. And can be installed by contacting Service Desk.

    Version: 8.5.0.0
  • Folder structure in message tree

    Area: Social media publishing
    Description:
    Social Media Publishing now uses a folder structure similar to email marketing

    Version: 8.5.0.0
  • Split testing indication in the page tree

    Area: Split testing
    Description:
    To provide a better overview of which pages have active split tests, an overlay icon is now displayed instead of the page icon

    Version: 8.5.0.0

Ecommerce

  • Assortments (Placeholder)

    Area: Assortments
    Description:
    Assortments have been entirely remodeled and is now a flexible way to show certain products to selected users only. In the Product catalog you now have an Assortments node (when module is installed) where it is possible to create assortments with shops/groups/products and add users and user groups that have access to the selected shops/groups/products. When you have added shops/groups/products to your assortments you need to build the assortment which is done by a scheduled task in Management center - System - Scheduled tasks. The task runs every 5 min. In order to enable the assortment setup in the frontend you need to enable the checkbox in Management center - Ecommerce - Advanced - Assortments. When the checkbox is enabled the selected shops/groups/products in the assortments are only available for the selected users.

    Version: 8.5.0.0
  • WishList: Add Ecom:Product.RemoveProductFromList

    Area: Customer Center
    Description:
    Added the tag Ecom:Product.RemoveProductFromList to the Ecom:CustomerCenter.List.ProductsList loop. This tag removes the product from the list (the other tag Ecom:Product.RemoveFromList removes only one instance of the product at the time).

    Version: 8.5.0.0
  • Sort Product Field filter options in the specified order

    Area: Filters
    Description:
    When creating a product category field of type "List", the options for that field are sorted in a specific order. The filter options is rendered in the same order as their internal sort order.

    Version: 8.5.0.0
  • Stock presence filter should have an option to not apply the filter

    Area: Filters
    Description:
    The stock presence filter has the options: "Yes" and "No" that indicates whether to apply a filter for products in stock or products out of stock. Now you also have an option to turn the filter off, i.e., remove the filter from the list of criterias. The filter now has a "Render 'All' option" checkbox and it is possible to give it a label like the "Yes" and "No" options have.

    Version: 8.5.0.0
  • Default Group pictures

    Area: Management Center
    Description:
    Ecommerce group images now have the same functinality with Default images as for products. Default group images can now be setup in Management center -> eCommerce -> Advanced -> Images.

    Version: 8.5.0.0
  • Edit order: Make it possible to edit parts items in the backend

    Area: Orders\Edit order
    Description:
    It is now possible to edit part items (BOM items) in the ecom order. There is no recalculation of the order if you change the amount of a BOM item and the main product is set to e.g. Fixed price plus changes.

    Version: 8.5.0.0
  • Implement separate Capture functionality in Authorize .NET payment gateway

    Area: Payment\Authorize.Net
    Description:
    Until 8.5 the Authorize.NET payment provider only had the option "Authorize and Capture". From 8.5 it also has the option "Authorize". The order is authorized at Authorize.net and then you can manually capture from ecom backend order list.

    Version: 8.5.0.0
  • Quote Functionality

    Area: Quotes
    Description:
    With the Quotes module it is possible to create and edit quotes before the final order Quick guide: Install quotes module Create two order contexts (checkout and quote) and assign them to separate carts Set up a quote flow with whatever states fit your business (e.g draft, new, waiting, accepted) Setup customer center with quote templates - adjust quotedetail template reorder and checkout links with &OrderContext=ORDERCONTEXT# argument In frontend: Log in to extranet. Add a product to your quotecart and perform checkout In backend: Locate quote in Quotes section and edit it as needed In frontend: Find your quote in customer center -> My Quotes and from detail view add it to your checkout cart

    Version: 8.5.0.0
  • Discount matrix (Placeholder)

    Area: Sales Discounts
    Description:
    The Discount matrix has been introduced as a powerful tool to specialize the conditions for obtaining a discount similar to what is known from ERP systems. You now have the possibility to setup various settings that need to be fullfilled in order to render a discount. Note that the discounts from the Discount matrix should NOT be used together with the discounts from the Sales discount. The sales discounts from the 2 types of discount setup cannot be combined.

    Version: 8.5.0.0
  • Introduce logic and options to control the content of the cart before and after extranet user login

    Area: Shopping Cart v2
    Description:
    New setting in Mgmt -> Ecommerce -> Advanced configuraion -> Shopping Cart -> "Do not replace existing cart when user logs in" Currently if you have something in your cart as an anonymous user and log in you will keep using the cart from anonymous even if a saved cart exists for the logged in user. By enabling this checkbox you will use the saved cart instead

    Version: 8.5.0.0
  • VAT group name as a template tag

    Area: VAT
    Description:
    New tag: Ecom:Product.VATGroup.Name Returns the phone number of a good pizza joint in Viby ... or the localized name of the VAT group

    Version: 8.5.0.0
  • Reverse Charge For VAT (omvendt betalingspligt)

    Area: VAT
    Description:
    You are from version 8.4.1.7 able to disable VAT for specified VAT groups when a context value is set. This is to accommodate a danish law that comes into effect on July 1st 2014. This law specifies that VAT on electronic equipment sold to businesses is not collected (paid to) the seller, but should be handled by the buyer. This concept is the same is EU VAT law in B2B scenarios, and it's called "Reverse Charge". You disable VAT for specified VAT groups in Management Center - Ecommerce - Internationalization - VAT groups - . When "Reversed charge for VAT" is selected then VAT is disabled for the products that use the VAT group. The OrderLine has new property to indicate whether the price is in a reverse charge state. New tag: Ecom:Order:OrderLine.ReverseChargeForVat QueryString parameters: - ReverseChargeForVat=True|False - ReverseChargeForVatToken=<token> The token is calculated dynamically and can be found in the global tag: Global:eCommerce.ReverseChargeForVatToken. This means that you can enable the reverse charge state by a query like this: domain.com/page/product.aspx?ReverseChargeForVat=True&ReverseChargeForVatToken=<!--@Global:eCommerce.ReverseChargeForVatToken-->

    Version: 8.5.0.0
  • Add option to display price without VAT as the default price in frontend based on context value

    Area: VAT
    Description:
    From version 8.4.1.7 all prices with price extension will follow the new QueryString parameter: PricesWithVat=True|False or the new "Price with VAT" setting in Website edit - Ecommerce. If you set PricesWithVat=False in the Querystring or the "Price with VAT" settings is "No", then all prices are displayed with VAT. Basically, it follow the same idea behind the setting Currency on a website, and changing it in frontend. It is important to note that this will only work correctly for orders and orderlines if these tags are used: Ecom:Order.Price(.*) Ecom:Order:OrderLine.Price(.*) When cheking out the VAT is applied as ususal (unless you use Reverse charge for VAT in specific VAT groups).

    Version: 8.5.0.0
  • Handle non-unique (non-personal) vouchers in the same way as unique voucher

    Area: Vouchers
    Description:
    It is now possible to combine vouchers and product field discounts by using the same orderfield for both Note that you can't use validation rules (is voucher valid, is voucher expired) when using the voucher field for Order field discounts. The validation rules are validating against the voucher lists.

    Version: 8.5.0.0

Content

  • Statistics on users

    Area: Content
    Description:
    Statistics on a user can now be accessed from User management

    Version: 8.5.0.0
  • Password security to Extranet

    Area: Extranet
    Description:
    It's now possible to configure Extranet login limitations under Mgmt -> Control Panel -> Modules - User Management When enabled you can configure a blocking period that sets in after a user fails a certain number of login attempts within a specifik period of time

    Version: 8.5.0.0
  • Select an Email address in forms frontend

    Area: Forms (For Data Lists)
    Description:
    It is now possible to get the recipient email from form for the "Send the form via email" formsave event

    Version: 8.5.0.0
  • Make forum thread inactive

    Area: Forum (DW8)
    Description:
    Threads can now be toggled active / inactive from backend edit thread or by moderators in frontend (by using the appropriate template)

    Version: 8.5.0.0
  • Move a forum thread in the backend

    Area: Forum (DW8)
    Description:
    Forum threads can be moved between categories by selecting the category from the dropdown on the backend Edit Thread page

    Version: 8.5.0.0
  • Link selectors in frontend in Item Creator and Item Publisher

    Area: Item Creator
    Description:
    When editing item fields of the type link in frontend with Item publisher and Item creator the fields are rendered as text field and it is not possible to select pages, paragraphs or files with the backend selector from frontend editing.. If the system recognize the text as external link (e.g. dr.dk or www.dr.dk) it adds http:// in front of the link

    Version: 8.5.0.0
  • Item creator extension tag

    Area: Item Creator
    Description:
    Item creator can be inserted in a template Example: Using the Item Creator I build a forum where users can create forum threads as pages. On each page I want to collect comments as either pages or paragraphs. To do this I want to insert an Item Creator directly in the template: @Item.Creator(Itemtype:ForumThreadComment; TargetPage:this; ...)

    Version: 8.5.0.0
  • Folder selector in frontend in Item Publisher and Item Creator

    Area: Item Creator
    Description:
    When editing item fields of the type Folder in frontend with Item publisher and Item creator the fields are rendered as text field and it is not possible to select a folder with the backend selector from frontend editing.

    Version: 8.5.0.0
  • Multi select single items in item publisher

    Area: Item publisher
    Description:
    It is now possible to select a list of items and then they will be rendered as a list of items. Notice the breaking change when you upgrade from 8.4.1 to 8.5. The setting "Select specific item" is changed to handle multiple items and is named "Select specific items" in 8.5.0.0. This means that the setting now use a list template and not a detail template as before 8.5. In 8.4.1 the single item functionality used the detail template. In 8.5 the multi item functionality that replaces the single item uses the list template. This means that if you save your paragraph after upgrade from 8.4 to 8.5 and then save item publisher settings then it changes from detail view to list view in frontend which "breaks" the layout in frontend.

    Version: 8.5.0.0
  • Implementation of Filter in Item publisher extension tag

    Area: Item publisher
    Description:
    You can now use "Filter" as parameter in the Item.RenderList to filter the list of items that are rendered. Available expressions: «numeric field» < «numeric value» «numeric field» <= «numeric value» «numeric field» > «numeric value» «numeric field» >= «numeric value» «numeric field» is between «numeric value» and «numeric value» (is the same as >= and <=) «field» != «value» «field» <> «value» «string field» contains «string value» «string field» does not contain «string value» «string field» starts with «string value» «string field» does not start with value» «string field» ends with «string value» «string field» does not end with value» «date field» is before «date value» (date formatted as a string, e.g. "2014-01-01" or "2014-01-01 12:34:56") «date field» is after «date value» «field» = «value» Expressions can be combined using "or" or "and": Name starts with "M" and Name contains "e" Examples: <!--@Item.RenderList( ItemType: Page; ListSourceType: Area; ListSourceArea: 1; ItemFieldsList: *; ListTemplate: ItemPublisher/List/List.cshtml; ListPageSize: 10; Filter: Name contains "Mikkel" )--> <!--@Item.RenderList( … Filter: Name does not start with "F" or Name contains "a" )--> In Razor we can also use @Code: @RenderItemList(new { ItemType = "Page", ListSourceType = "Area", ListSourceArea = 1, ItemFieldsList = "*", ListTemplate = "ItemPublisher/List/List.cshtml", ListPageSize = 10, // Filter = @"DateAndTime is after @Code(DateTime.Now)", // Filter = @"DateAndTime is before ""2014-01-01""", // Filter = @"DateAndTime is after ""2014-01-01 12:34:56""", // Filter = @"Number is between 2 and 4", // Filter = @"Name does not start with ""F""" // Filter = @"Name does not end with ""e""" // Filter = @"Name contains @Request(q)" // Filter = @"Name contains 'a'" // Filter = @"Name starts with 'F'" // Filter = @"Name does not start with 'F' and Name contains 'a'" // Filter = @"Name does not start with 'F' or Name contains 'a'" Filter = @"Name does not start with 'F' and Name contains 'a'" })

    Version: 8.5.0.0
  • Add query string filters to Item publisher

    Area: Item publisher
    Description:
    Query string filtering has been implemented for ItemPublisher Examples: Name=Razor (exact match) Name=t* (starts with) Name=*t* (contains) Name=*t (ends with) Number=10 (equals) Number=10&Number.op== (equals (operator specified)) Number=10&Number.op=eq (equals (operator specified)) Number=10&Number.op=!= (not equal to) Number=10&Number.op=<> (not equal to) Number=10&Number.op=< (less than) Number=10&Number.op=<= (less than or equal to) Number=10&Number.op=> (greater than) Number=10&Number.op=>= (greater than or equal to) Number.from=10&Number.to=20 (range (explicit)) Number=10-20 (range (implicit)) Double=0&Double.op=lt (less than) Double=0&Double.op=gt (greater than) DateAndTime=2014-08-01 (equal) DateAndTime=2014-08-01&DateAndTime.op=< (before) DateAndTime=2014-08-01&DateAndTime.op=lt (before) DateAndTime=2014-08-01&DateAndTime.op=> (after) DateAndTime=2014-08-01&DateAndTime.op=gt (after)

    Version: 8.5.0.0
  • Extending item types (inheritance)

    Area: Items
    Description:
    It is now possible to inherit fields from other item types. The inherited fields are listed in the item field list and are sortable together with the not-inherited fields in the item type. Example: - Address (fields: address, zip, city, country) -Person (fields: name, birthday) - Student (field: enrollment) - Teacher (field: salary) In the above example the Person item type inherits fields from the Address item type. The Student and Teacher item types are inheriting fields from the item type Person and Address. Student has the fields: address, zip, city, country, name, birthday, enrollment. The item type settings are NOT inherited - only fields are inherited. If you create a page with the Student item type, then it's the settings from the Student item type that is applied (e.g. "Enable item type for", "Allow in websites", "Use field for title").

    Version: 8.5.0.0
  • Make it possible to override rendering of item type fields in frontend

    Area: Items
    Description:
    Currently, the same editor is rendered for an item type field in both frontend and backend. From Dynamicweb 8.5 it now possible to override the frontend rendering of item type fields Example: Public Overridable Function BeginEditFrontend(ByVal context As EditorContext) As Object BeginEdit(context) End Function Public Overridable Function EndEditFrontend() As Object Return EndEdit() End Function If ExecutingContext.IsFrontEnd in the item creator and edit item in item publisher, the frontend editing methods should be used to render the control.

    Version: 8.5.0.0
  • Make it possible to change an Item type in use

    Area: Items
    Description:
    In Page properties - Advanced we have added an "Item type" button that makes it possible to change the item type for a page. All content in the item type that you change from will be lost. The change of item type is not saved before you save the page after changing the item type. You can change from an item based page/paragraph to an ordinary page/paragraph by selecting "Nothing selected" in the Item type dropdown. If "Disable standard paragraph" and/or "Disable standard page" is selected in Management center - Editing - Interface setttings then it is not possible to change from item pages/paragraphs to ordinary. You are always allowed to change from an existing ordinary page/paragraph to item based.

    Version: 8.5.0.0
  • Make it possible to disable standard pages and paragraphs

    Area: Items
    Description:
    It is now possible to disable standard pages and standard paragraph on a solution. Then "Blank" or page templates based on standard pages are not available when creating a new page or paragraph. To disable standard pages and paragraphs go to Management Center > Editing > Interface settings > Paragraph section > Disable standard paragraph and Page section > Disable standard page.

    Version: 8.5.0.0
  • File editor should support upload and selection from dropdown

    Area: Items
    Description:
    When editing item fields of the type File in frontend with Item publisher and Item creator the fields are now rendered as a dropdown with the matching files in the folder specified on the field. No browse or preview buttons are rendered in the frontend. File editor field now supports filtered upload selection Example: Insert an input field in your edit template, e.g. like this: <input type="File" name="FileTester" accept="<!--@ItemPublisher:Edit.Item.FileTester.Extensions-->" style="width:250px;"> In this case the input name is File and the item field system name is File too. If the item field system name were FileUploader then the name of input should be FileUploader" too. So, in input name you write appropriate field system name. And only unique system name, not simple name because you can have several file-fields, and several inputs for them. Each input should correspond to needed file field via systemname.

    Version: 8.5.0.0
  • Checkbox to enable module attachment on item type

    Area: Items
    Description:
    In item type settings we now have a checkbox "allow module attachment" that needs to be checked before a module can be attached to a paragraph item. If this checkbox is not marked, then the "Module" button is hidden when editing the item paragraph.

    Version: 8.5.0.0
  • Small UI changes when item field is used as title

    Area: Items
    Description:
    When "Use field for title" is enabled in the settings for the item type then the paragraph name field is hidden for paragraphs. A label "Used for title" is added behind the field for both item based pages and paragraphs when a field is selected for title in the item type settings.

    Version: 8.5.0.0
  • Show product name instead of product ID in Item list

    Area: Items
    Description:
    We now render the product name(s) instead of raw data (product ID) in the Item list when the item list shows the content from a product field. The product ID is available if you mouse over the product name.

    Version: 8.5.0.0
  • Link tags are not working with Product field

    Area: Items
    Description:
    We have implemented a parameter on the Product item type where you can select a paragraph that contains a product catalog (like in Product catalog paragraph settings). Notice that products that are not active/not in stock/have no price (and in ecom are set to not visible in mgm center) are not hidden in item product page. So when you click a product that are not active/not in stock/have no price you get a blank page.

    Version: 8.5.0.0
  • Translating item field names in backend

    Area: Items
    Description:
    We are now able to localize item field names in the backend, i.e. if an item has a Name field it is called "Navn" when using Danish as backend language and "Name" when using english backend. If the field hasn't a translation key then it use the default text or name from the field settings.

    Version: 8.5.0.0
  • Named Item lists on pages

    Area: Items
    Description:
    Named item lists are used for putting items into named lists on pages. The items in a named item list are not published automatically and is n not rendered in template tags when showing a page, but they must be explicitly published using an item publisher. A named item list is just an Item list connected to a page and having a name. The Item publisher has a new source setting: "Named item list" and the Item creator has the new setting: "Create item in named list ". Example The named item lists can e.g. be used for comments on a page. You can create an item list type that use an item type with a name and e-mail field. This item list is added to the named list and e.g. called "Comments". On the same page you can insert an Item publisher in order to publish the comments from the named list. To create new comments from frontend you can add an Item creator on the page to add the comments to the named list.

    Version: 8.5.0.0
  • Always group paragraphs by container in backend paragraph list

    Area: Paragraphs
    Description:
    Paragraphs are no longer orphaned when their content area is removed or the design template is changed. Instead they are shown in their original content placeholder with an added Not in Template but excluded from frontend rendering

    Version: 8.5.0.0
  • Add pdf option for specifying page size

    Area: Print to PDF
    Description:
    Pdf print default size can be set in Mgmt -> System -> Solution -> Pdf but can still be overridden via query string - e.g ...?pdf=true&pagesize=A4 ...?pdf=true&pagesize=letter

    Version: 8.5.0.0
  • Info bar about index

    Area: Smart Search
    Description:
    When creating a new smartsearch in Ecom you get an infobar showing you when the index was last updated

    Version: 8.5.0.0
  • Smartsearch: New options

    Area: Smart Search
    Description:
    Several new search areas / terms have been added to SmartSearch. They are: User Audit fields User email permissions User links in email marketing Ecom Orders Ecom Product categories

    Version: 8.5.0.0
  • Add template tag with base url of current design

    Area: Templates
    Description:
    Design root folder available as tag, allowing you to e.g load stylesheets relative to design path: @SnippetStart(StyleSheets) <link href="@Template:DesignBaseUrl/stylesheets/ecom.css"/> @SnippetEnd(StyleSheets)

    Version: 8.5.0.0
  • Add "unwrap" setting to content placeholders

    Area: Templates
    Description:
    As a frontend developer using JSON/XML publishing, you would like to be able to get rid of the content placeholder element and only keep the content. To do this you are now able to write <div class="dwcontent" id="content" data-settings="unwrap: true"></div> and have this converted to <!--@DwContent(content)-->

    Version: 8.5.0.0
  • Translations as a replacement/improvement of translate tags in templates

    Area: Templates\Translate
    Description:
    A new Translation system has been implemented and is available from the root of the Management center tree. When you click the Translations node in Management center you find a "shared" node and node for each design in your Designs folder. Now you can have a translations.xml in the root of the Designs folder and used for "shared" (global) translations (all designs) and a translations.xml in each design folder and used for that specific design. You can gather the translations keys from the module folders in one translation file for the design/designs. The languages that are available in Translations are the languages that are used for the websites in the Websites module. Note: The new Translation system takes over when a translation.xml file is created in either the Designs folder or in the designs folders. A translation.xml is created when a key is added through the Translations interface in the Management center. This means that if you create a key in e.g. "shared" then a translations.xml is created in the Designs folder and it overrules the translation files in the module template folders. If a key doesn't exist in the translation.xml file then the translation fall back to the translation in the template. If you have existing translations on live solutions it is recommented to copy them from to Designs/translations.xml before you start to use the new Translations UI.

    Version: 8.5.0.0
  • Limited access to edit users and groups

    Area: User Management
    Description:
    You can now have group administrators in user management. These administrators can edit users in the groups they are admins for.

    Version: 8.5.0.0
  • Import Users should work with standard Excel format

    Area: User Management
    Description:
    User Management user import can now take an Excel (xslsx) file as source with the following limitations: Workssheets must not contains whitespaces No merged cells First row must contain headers Worksheet and file must have the title "AccessUser"

    Version: 8.5.0.0
  • Updated address format on users

    Area: User Management
    Description:
    New User fields in User Management: Title, FirstName, LastName, MiddleName, HouseNumber.

    Version: 8.5.0.0

Platform

  • Group Number in XML

    Area: Platform
    Description:
    Ecom Group number is now included as an attribute in the navigation XML

    Version: 8.5.0.0
  • Dynamicweb install wizard

    Area: Install Wizard
    Description:
    Accessing Dynamicweb application in IIS now starts an installation wizard for easy deployment

    Version: 8.5.0.0

Integration

  • ExcelProvider for Data Integration

    Area: Data Integration
    Description:
    An Excel provider has been added to the DataIntegration module Please note the following limitations: Workssheets must not contains whitespaces Worksheet must be named identically to destination table Do not use merged cells, merged cells becomes null or empty string First row must contain headers Each worksheet is treated as a table Export filetype must be xls or xlsx

    Version: 8.5.0.0
  • Auto "add source tables to destination"

    Area: Data Integration
    Description:
    For ease of use source table is automatically added to destination when destination provider is CSV or XML

    Version: 8.5.0.0
  • Parameters in job execution for use in integration activity filtering

    Area: Data Integration
    Description:
    DataIntegration jobs can now be parameterized. Example: To export only orders from after June 20 2014 set up a condition in your job with "LastExport >= {{LastExportData||"2014-02-20"}}" and call JobRunner.aspx with an extra argument "...&LastExport=2014-06-20". If the LastExport argument is not present the default value will be used instead - here 2014-02-20

    Version: 8.5.0.0
  • User sync & AD integration

    Area: Framework
    Description:
    Dynamicweb now support Active Directory integration through the integration framework

    Version: 8.5.0.0