Anonymous, bureaucrat, administrator
7,528
edits
Changes
no edit summary
A contact history must be added to the record during upload or the custom outcome won't remain on the records if the contact queue is reset in the Outbound module.
If no custom outcome is used the default outcome on the records will be ''Imported'', also if the no contact history is added and the records are reset the outcome will be set to ''Imported''
= Smart Update =
Smart update provides an extension on the Add Only process. In this case, the file you are uploading needs to be compared to the existing records as there may be overlap or records that need updating. Smart update allows you to select a "matching" field. If a record exists (a match has been found) in the spreadsheet and in the form, you can choose which information is to take priority. Then for any record that is not matched a new record is added to the form.
This process is ideal for also performing mass updates to remove "do not call" numbers. You can load a list of "do not call" numbers and where a match is found, the record is removed from the active calling list.
Following the steps from the process above. The final screen gives a number of Smart configuration options.
** Replace all columns. If the file does not contain all the columns, should the fields in the form be blanked. This can be useful for when a validation file is overloaded to confirm that a master external data source is confirming it has the data it needs.
* Add Contact History. This can add an extra CCL to the records to show they were updated / interacted with
While performing the Smart Update function of bxp, it is now possible for a user to enable the bxp WasIs engine, this allows for a log to be kept of all the changes that came about from the Smart Update. This log is created only if there is a difference between the original value (value Pre Update) and the new value (value post update) of a question. This log can be stored in either the CCL of a record or stored in a separate question in the CDA of the record. If you want the log to be stored in a CCL you must set the option "Add Contact History" to be "Add Contact".
When the log is being save it will take the following default format: Field_Question_Name Was [value_Pre_Update] Is [Value_Post_Update]. You are also able to enter is a custom format for this log by simply typing in plain text the wording for the log into the options box "WasIs Engine Custom Layout". in order to get the field name that was updated, the pre update value and the post update value you will need to add the following into your custom layout
<syntaxhighlight lang="javascript" line start="1">
[ [--X--]] - This will be replaced by the Pre Update Value
[ [--Y--]] - This will be replaced by the Post Update Value
[ [--Z--]] - This will be replaced by the Field Question Name
</syntaxhighlight>
Example Custom WasIs Layout - The field [ [--Z--]] before the smart update contained the value [ [--X--]] and after the smart update contained [ [--Y--]]
Example Custom WasIs Layout Output - The field ''Customer Name'' before the smart update contained the value ''Patrick'' and after the smart update contained ''Paddy''
== WasIs Engine Settings ==
* Enable WasIs Engine Tracking - This setting let's the function know if it should perform the WasIs engine tracking
* WasIs Engine Custom Layout - This allows you to enter in a custom log entry for the WasIs engine
* WasIs Engine field to store results - This allows you to select what field in the form to store the WasIs Log