Form - Data Import - Revision history

Philip Lacey at 02:24, 2 January 2016

2016-01-02T02:24:42Z

Philip Lacey at 08:32, 30 September 2015

2015-09-30T08:32:22Z

Philip Lacey at 08:31, 30 September 2015

2015-09-30T08:31:56Z

Patrick Jenkins at 08:15, 16 September 2015

2015-09-16T08:15:23Z

Patrick Jenkins at 08:11, 16 September 2015

2015-09-16T08:11:53Z

Philip Lacey: /* Add Only */

2015-07-01T11:59:29Z

‎Add Only

Philip Lacey at 14:57, 29 June 2015

2015-06-29T14:57:04Z

Philip Lacey: Philip Lacey moved page Database - Data Import to Form - Data Import

2015-06-29T14:22:02Z

Philip Lacey moved page Database - Data Import to Form - Data Import

Philip Lacey at 00:48, 22 March 2014

2014-03-22T00:48:51Z

Louise Ashton at 11:23, 6 November 2013

2013-11-06T11:23:53Z

@@ Line 94: / Line 94: @@
 <syntaxhighlight lang="javascript" line start="1">
-[[--X--]] - This will be replaced by the Pre Update Value
+[ [--X--]] - This will be replaced by the Pre Update Value
-[[--Y--]] - This will be replaced by the Post Update Value
+[ [--Y--]] - This will be replaced by the Post Update Value
-[[--Z--]] - This will be replaced by the Field Question Name
+[ [--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 - 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''

← Older revision		Revision as of 08:32, 30 September 2015
Line 105:		Line 105:


−	~~'''~~WasIs Engine Settings~~'''~~	+	== WasIs Engine Settings ==

@@ Line 62: / Line 62: @@
 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 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.
+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.
-Follow the top add process above.
+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.
-The final screen gives a number of Smart configuration options.
+Following the steps from the process above.  The final screen gives a number of Smart configuration options.

@@ Line 92: / Line 92: @@
-* [[--X--]] - This will be replaced by the ''Pre Update Value''
+<syntaxhighlight lang="javascript" line start="1">
-* [[--Y--]] - This will be replaced by the ''Post Update Value''
+[[--X--]] - This will be replaced by the Pre Update Value
-* [[--Z--]] - This will be replaced by the ''Field Question Name''
+[[--Y--]] - This will be replaced by the Post Update Value

← Older revision		Revision as of 08:11, 16 September 2015
Line 83:		Line 83:
	** 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.		** 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		* 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
		+
		+
		+	* [[--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''
		+
		+
		+	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

← Older revision		Revision as of 11:59, 1 July 2015
Line 59:		Line 59:


		+	'''Note:''' Functionality has recently been added to allow an outcome to be uploaded as part of the file upload process.
		+	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 =

@@ Line 1: / Line 1: @@
-Database - Data Import manages the following functions:
+= Overview =
-# Load Data Records - Quick Upload
+There are a number of ways of loading data into bxp forms.  All these functions are located in the Form Management > Form - Data Import section.
-'''Load Data Records - Quick Upload'''
+There are four primary sources of data import in this section and eight ways of getting data into a form
 Problems can sometimes occur when there is hidden information in cells so try and keep the data (text) as clean as possible
-*Click Load Data Records - Existing Record Update
+bxp can export custom archives that contain CDA and CCL data.  This is the load process for those archives.  For more details please review [[Form_Complete_Archive]]

← Older revision	Revision as of 14:22, 29 June 2015
(No difference)

← Older revision		Revision as of 00:48, 22 March 2014
Line 39:		Line 39:

	Load custom files into a form using Create Form Archive - By Last Contact, in Database Export		Load custom files into a form using Create Form Archive - By Last Contact, in Database Export
		+
		+
		+
		+	[[Category:Module Specific:Form Management]]
		+	[[Category:Topic:Security]]

← Older revision		Revision as of 11:23, 6 November 2013
Line 19:		Line 19:
	*If confirmed, the records will upload successfully, if not, they won’t and you need to check your work		*If confirmed, the records will upload successfully, if not, they won’t and you need to check your work
	*If you are sure the data is correct, there is no need to verify and you can simply upload the file		*If you are sure the data is correct, there is no need to verify and you can simply upload the file
		+
		+
		+	'''Load Data Records - Uploaded File'''
		+
		+	*Click Load Data Records – Use uploaded file
		+	*A list of files will be displayed
		+	*Choose the file you want to upload
		+	*If no files have been added to the system, no files will be displayed
		+
		+
		+	'''Load Data Records - Existing Record Update'''
		+
		+	*Click Load Data Records - Existing Record Update
		+	*Browse for the file
		+	*Upload it to the form
		+
		+
		+	'''Load bxp software Archive - (Data and Contact history)'''
		+
		+	Load custom files into a form using Create Form Archive - By Last Contact, in Database Export