This release contains a fix to a database locking problem that could occur if you created a customer BI for a large volume of customers and attempted to update those customers with correspondence codes at the same time. The database locking could result in orders failing to complete.
The fix for this problem moves the solution for extracts with correspondence codes from the Business Intelligence infrastructure into our messaging infrastructure which is designed to support large volume updates to customer records. Because of the urgent need to fix the blocking issue, the user interface updates are incomplete for this release.
If you want to extract customer records from the system and apply correspondence codes to those customers, you will need to create a message under Correspondence application Message pages. It might seem a little alien at this point to create a message for this type of activity; we will address the user experience problems in a later fix.
Create the message as if you are creating an email marketing message, but do not build any email content under on the Message|Build page nor schedule the email message on the Message|Schedule page. Set theMessage|Basic page's 'Send To' field to the name of your source Customer BI and enter a correspondence code to update the customer records with. Select an extract template and save the message.

Once the message is saved you can now choose to extract the BI source. The extract will update the customer records in the source BI with the correspondence code you entered into the message.
Correspondence fields still appear in Customer BIs. Ignore these fields. They will not update the customer record and will be removed in a later release.
In this release it is only possible to set the correspondence code on customers, and not other correspondence detail fields. In a later release it will be possible to set other correspondence detail fields.