Using Forms Offline - Revision history

Philip Lacey at 19:14, 28 November 2015

2015-11-28T19:14:29Z

Philip Lacey at 19:03, 28 November 2015

2015-11-28T19:03:56Z

Philip Lacey at 19:03, 28 November 2015

2015-11-28T19:03:17Z

Philip Lacey at 19:02, 28 November 2015

2015-11-28T19:02:53Z

Philip Lacey at 19:01, 28 November 2015

2015-11-28T19:01:03Z

Philip Lacey at 18:58, 28 November 2015

2015-11-28T18:58:53Z

Philip Lacey at 18:56, 28 November 2015

2015-11-28T18:56:16Z

Philip Lacey at 19:42, 9 November 2014

2014-11-09T19:42:18Z

Philip Lacey at 22:51, 27 October 2014

2014-10-27T22:51:07Z

Philip Lacey: Created page with "== Overview == When data is stored in Business Express (BeX), NOTHING is stored on the device. This provides instant data protection compliance for the device. The con to ..."

2014-10-27T22:50:40Z

Created page with "== Overview == When data is stored in Business Express (BeX), NOTHING is stored on the device. This provides instant data protection compliance for the device. The con to ..."

New page

== Overview ==

When data is stored in bxp software (bxp), NOTHING is stored on the device. This provides instant data protection compliance for the device. The con to that pro, is that it needs to be in coverage.

When agents need to save a form but are not in Internet coverage, the form can be opened on a device and even saved. The form will contain encryption capabilities and generate an encrypted file on the device storing all the data entered into the form. When the user returns to coverage, the created file can be opened and it will repopulate all the fields, allowing an outcome to be chosen and processing will continue as normal.

There are a lot of considerations to offline record creation and processing.

== Device Considerations ==

There could be an option for storing data locally, but can introduce numerous headaches doing so:
# The agents will need formal data protection handling training for offline devices.
# The devices will need to store locally a script which is capable of creating a “data record file”
# That file will be stored on the device until the agent is back in coverage
# When back in coverage the agent will need to upload the file back into BE
# The agent will then need to delete the file from the device

As you can see from this, there are numerous challenges with an “offline” solution:
* Users not uploading files. We can’t force the agents to upload their records
* The device being stolen / forgotten with records on it. We can’t stand over the security or secure use of the device
* bxp can help with the human element of “interference”, i.e. users modifying the generated files to change creation dates and times. There still is a chance a tech savy agent will learn to circumvent the hindrances.
* bxp does work on dialup and most places will have GSM coverage which will be fast enough.
* The device MUST have the capability to store documents. i.e. iPads and iPhones do not allow for storage of documents or files.

== Operation ==

The time and date and the file name are system generated and not to be altered by the user. You perform the saving of the data in bxp in 3 steps.
## Step 1. To gather and encrypt the data.
## Step 2. Save the file to your device.
## Step 3. Blank all the fields and start again.

== Operation Notes ==

# Outcomes can’t work offline. You can’t have a record work offline because with no Internet connectivity there is no ability to do work. This why when the file is reloaded into BE then an outcome can be chosen. Also between using the outcomes in the field and the outcomes when they’re back online, can change. So it is impossible to state which outcome to use when the user is offline.
# The fields you cannot edit when using the offline engine are system based fields.

← Older revision		Revision as of 19:14, 28 November 2015
Line 52:		Line 52:


−	== Operation ==	+	= Considerations =
		+
		+
		+	== Operation Considerations ==


Line 63:		Line 66:


−	= Device Considerations =	+
		+	== Device Considerations ==

@@ Line 14: / Line 14: @@
-[[File:Offline_001.png|400px|Inbound Contact]]
+[[File:Offline_001.png|600px|Inbound Contact]]
@@ Line 26: / Line 26: @@
-[[File:Offline_003.png|400px|Offline options]]
+[[File:Offline_003.png|600px|Offline options]]
@@ Line 48: / Line 48: @@
-[[File:Offline_004.png|400px|Upload Offline File]]
+[[File:Offline_004.png|600px|Upload Offline File]]

@@ Line 12: / Line 12: @@
 = The process =
 [[File:Offline_001.png|400px|Inbound Contact]]
@@ Line 22: / Line 24: @@
 When the screen opens it will appear as a normal form but at the bottom.
 [[File:Offline_003.png|400px|Offline options]]
@@ Line 42: / Line 46: @@
 When the user returns to coverage, the created file can be opened and it will repopulate all the fields, allowing an outcome to be chosen and processing will continue as normal.
 ''Main Menu > Inbound Contact > My Data > Process Offline Records > Choose file ''
 [[File:Offline_004.png|400px|Upload Offline File]]

@@ Line 12: / Line 12: @@
 = The process =
-[[File:Offline_001.png|frame|400px|Inbound Contact]]
+[[File:Offline_001.png|400px|Inbound Contact]]
@@ Line 22: / Line 22: @@
 When the screen opens it will appear as a normal form but at the bottom.
-[[File:Offline_003.png|400px|frame|Offline options]]
+[[File:Offline_003.png|400px|Offline options]]
@@ Line 42: / Line 42: @@
 When the user returns to coverage, the created file can be opened and it will repopulate all the fields, allowing an outcome to be chosen and processing will continue as normal.
 ''Main Menu > Inbound Contact > My Data > Process Offline Records > Choose file ''
-[[File:Offline_004.png|400px|frame|Upload Offline File]]
+[[File:Offline_004.png|400px|Upload Offline File]]

← Older revision		Revision as of 19:01, 28 November 2015
Line 12:		Line 12:

	= The process =		= The process =
−	[[File:Offline_001.png\|400px~~\|frame~~\|Inbound Contact]]	+	[[File:Offline_001.png\|frame\|400px\|Inbound Contact]]

@@ Line 1: / Line 1: @@
-== Overview ==
+= Overview =
-When data is stored in bxp software (bxp), NOTHING is stored on the device.  This provides instant data protection compliance for the device.  The con to that pro, is that it needs to be in coverage.
+When data is stored in bxp software (bxp), NOTHING is stored on the device.  This provides instant data protection compliance for the device.  The con to that pro, is that the user needs to be in Internet coverage.
-When agents need to save a form but are not in Internet coverage, the form can be opened on a device and even saved.  The form will contain encryption capabilities and generate an encrypted file on the device storing all the data entered into the form.  When the user returns to coverage, the created file can be opened and it will repopulate all the fields, allowing an outcome to be chosen and processing will continue as normal.
+For many field agents Internet coverage can vary.  So what can be done?  Well, bxp has the capability to be used offline with some considerations.
@@ Line 11: / Line 52: @@
-== Device Considerations ==
+# Outcomes can’t work offline.  You can’t have a record work offline because with no Internet connectivity there is no ability to do work.  This why when the file is reloaded into BE then an outcome can be chosen.  Also between using the outcomes in the field and the outcomes when they’re back online, can change.  So it is impossible to state which outcome to use when the user is offline.
@@ Line 29: / Line 75: @@
 * The device MUST have the capability to store documents.  i.e. iPads and iPhones do not allow for storage of documents or files.

← Older revision		Revision as of 19:42, 9 November 2014
Line 46:		Line 46:
	# Outcomes can’t work offline. You can’t have a record work offline because with no Internet connectivity there is no ability to do work. This why when the file is reloaded into BE then an outcome can be chosen. Also between using the outcomes in the field and the outcomes when they’re back online, can change. So it is impossible to state which outcome to use when the user is offline.		# Outcomes can’t work offline. You can’t have a record work offline because with no Internet connectivity there is no ability to do work. This why when the file is reloaded into BE then an outcome can be chosen. Also between using the outcomes in the field and the outcomes when they’re back online, can change. So it is impossible to state which outcome to use when the user is offline.
	# The fields you cannot edit when using the offline engine are system based fields.		# The fields you cannot edit when using the offline engine are system based fields.
		+
		+
		+
		+	[[Category:Module Specific:Form Management]]
		+	[[Category:Topic:Security]]

@@ Line 35: / Line 35: @@
 The time and date and the file name are system generated and not to be altered by the user. You perform the saving  of the data in bxp in 3 steps.
-## Step 1. To gather and encrypt the data.
+# Step 1. To gather and encrypt the data.
-## Step 2. Save the file to your device.
+# Step 2. Save the file to your device.
-## Step 3. Blank all the fields and start again.
+# Step 3. Blank all the fields and start again.