Now when deploying Connect on Windows with FTP-ES on Filezilla, server manual editing in CRM.ENV is now handled automatically. Previously when performing this type of deployment, manual editing of CRM.ENV was required.
New auditing requirements in Taiwan are required for Connect, such that any customer record viewed in the UI is to be logged. This information is to be logged in a separate new table in the database. The table will include the User ID, name and role, the CSI ID, Module ID, Customer ID and the date viewed. This logging occurs with any display of the customer record, be it viewing an individual record, a list of customers as a result of a query or a drilldown report. Each customer displayed in the query would be logged.
When attempting to provide Connect support to a client or during QA testing, if a screenshot was taken of Connect, there was no way to identify which environment or version the issue was affecting. This became problematic when there was more than one version of Connect on the client site, or when testers were testing multiple environments.
What has been introduced is a string-typed system parameter which displays the environment name detail at the top-right of the screen beside the user security profile name. You can locate the system parameter under Content -> Internal Access -> CT.EnvironmentBannerText. The default value of the environment variable is blank. When its value is blank it will display connect version, and respective value otherwise.
Reversions of the campaign report was able to display results for multiple campaigns. This ability was removed from the report. This feature has been returned to the campaign report.
In prior versions, CONNECT stored numeric and datetime attributes as character data in the CUST_ATTRIBUTES and CUST_PREFERENCES tables. The drawback of this approach is that SQL functions must be used to convert these values from strings to numbers in the targeting queries, which results in the database query optimizer using suboptimal query plans.
The current version adds new tables to store numeric and datetime values in numeric database fields, which eliminates the need for SQL type conversion functions in the targeting queries.
Current numeric and datetime attributes will continue to be stored as character data in the CUST_ATTRIBUTES and CUST_PREFERENCES tables. Contact support if you need to convert existing attributes or preferences to the new typed representation.