GoZync4

Zync Options

GoZync4.ZyncOptions History

Hide minor edits - Show changes to output

July 01, 2013, at 12:32 AM by 166.147.88.40 -
Changed lines 27-28 from:
-> Because all this happens while you're connected to the remote files, this can be slower than just pushing or just pulling. For that reason, round trip shouldn't simply be your default action. Think about who needs which records and [[scripts in your file | script your sync]] accordingly.
to:
-> Because all this happens while you're connected to the remote files, this can be slower than just pushing or just pulling. For that reason, round trip shouldn't simply be your default action. Think about who needs which records and [[Zync It | script your sync]] accordingly.
June 30, 2013, at 09:19 PM by 50.132.84.245 -
Changed lines 3-4 from:
Zync options are set at the layout level, and thus you can set some options at the layout level as well. From the dashboard in GoZyncHosted, click the name of any entity row and then select the option you want:
to:
Zync options are set at the layout level: from the configuration tab in GoZyncHosted, click the name of any entity row and then select the option you want:
Changed lines 7-8 from:
These options represent the default actions for the file, some like the actions (push, pull, round trip) can be overridden by scripts in your file.
to:
These options represent the default actions for the layout but can be overridden by calling one of the [[Zync It]] scripts in your file.
June 24, 2013, at 04:47 PM by 108.38.141.66 -
June 24, 2013, at 04:45 PM by 108.38.141.66 -
Changed lines 5-6 from:
%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/zyncoptions.png | http://www.seedcode.com/rootimages/stikipad/gozync/zyncoptionssm.png]]
to:
%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/zyncoptions4.png | http://www.seedcode.com/rootimages/stikipad/gozync/zyncoptions4.png]]
June 24, 2013, at 04:43 PM by 108.38.141.66 -
Changed lines 3-4 from:
Zync options are set at the layout level, and thus you can set some options at the layout level as well. Select a layout from the dashboard in GoZyncHosted, click "Integration and Options" and then select the "Zync Options" tab:
to:
Zync options are set at the layout level, and thus you can set some options at the layout level as well. From the dashboard in GoZyncHosted, click the name of any entity row and then select the option you want:
Changed lines 11-12 from:
-> Push is the fastest way to get records from your mobile device to the host or server. When this is selected, GoZync will send changed records up to the inbox in GoZyncHosted then break the connection to the server.
to:
-> Push is the fastest way to get records from your mobile device to the host or server. When this is selected, GoZync will send changed records up to your hosted database then stop.
Deleted lines 14-17:
-> Because GoZync stops when the records are safely in the GoZyncHosted inbox, the mobile device never has to open your hosted solution (which can be the slowest part of a sync).

-> Record left in the GoZyncHosted inbox, can then be processed manually or [[auto processing | with a server side script]] every so often.

Changed lines 21-22 from:
-> Pull is ideal for tables where you're never editing the records on the mobile device, such as price lists. You may also want to pull as part of doing a round-trip (see below) manually. So you might push, then wait a bit, knowing the server-side processing will process the uploaded records faster than your iPhone. You can do something else, before calling a pull thirty minutes later.
to:
-> Pull is ideal for tables where you're never editing the records on the mobile device, such as price lists. You may also want to pull as part of doing a round-trip (see below) manually.
Changed lines 25-37 from:
-> Round trip is definitely the most impressive action in GoZync and if you have a fast connection, it's pretty damn cool. GoZync pushes changed records to the host/server, then processes that device's inbox records on the server. Then it searches for changed records and pulls them down to process them into your mobile file.

-> Because the GoZyncHosted inbox is processed while you're connected to the remote files, this can be much slower than just pushing or just pulling
. For that reason, round trip shouldn't simply be your default action. Think about who needs which records and [[scripts in your file | script your sync]] accordingly.

!! Delete sent data before next Zync.

In many workflows, users receive work orders or tasks from the host, complete those, and then send the completed tasks back to the host before retrieving the next day's set of tasks. In such cases we've found it helpful to leave the "uploaded" records on the iPhone or iPad so users can see what they did that day (and see that their work was "uploaded").

When "delete sent..." is turned on, users' uploaded records will persist on their mobile device after they are uploaded, but will be deleted from the device as soon as users begin their next pull sync (even as part of a round trip) of that table.

! Field Level Merge

(:include FieldLevelMerge:)
to:
-> Round trip is definitely the most impressive action in GoZync and if you have a fast connection, it's pretty damn cool. GoZync pushes changed records to the host/server, then it searches for changed records and pulls them down to process them into your mobile file.

-> Because all this happens while you're connected to the remote files, this can be slower than just pushing or just pulling. For that reason, round trip shouldn't simply be your default action
. Think about who needs which records and [[scripts in your file | script your sync]] accordingly.
May 22, 2013, at 03:49 PM by 67.190.87.90 -
Changed lines 7-8 from:
These options represent the default actions for the file, some like the actions (push, pull, round trip) can be overridden by [[scripts in your file]].
to:
These options represent the default actions for the file, some like the actions (push, pull, round trip) can be overridden by scripts in your file.
December 20, 2012, at 05:04 AM by cm - minor edits and clarifications
Changed lines 3-4 from:
Zync options are set at the layout level and thus you can set some options at the layout level as well. Select a layout from the dashboard in GoZyncHosted, click "Integration and Options" and then select the "Zync Options" tab:
to:
Zync options are set at the layout level, and thus you can set some options at the layout level as well. Select a layout from the dashboard in GoZyncHosted, click "Integration and Options" and then select the "Zync Options" tab:
Changed lines 25-26 from:
-> Pull is ideal for tables where you're never editing the records on the mobile device: such a price lists. You may also want to pull as part of doing a round-trip (see below) manually: so you might push, the wait a bit, knowing the server-side processing will process the uploaded records faster than your iPhone--and while you're doing something else, before calling a pull 30 minutes later.
to:
-> Pull is ideal for tables where you're never editing the records on the mobile device, such as price lists. You may also want to pull as part of doing a round-trip (see below) manually. So you might push, then wait a bit, knowing the server-side processing will process the uploaded records faster than your iPhone. You can do something else, before calling a pull thirty minutes later.
Changed lines 29-32 from:
-> Round trip is definitely the most impressive action in GoZync and if you have a fast connection is pretty damn cool. GoZync pushes changed records to the host/server, then processing that device's inbox records on the server, before searching for changed records and pulling them down to process them into your mobile file.

-> Because the GoZyncHosted inbox is processed while you're connected to the remote files, however, this can be much slower than just pushing or just pulling, and for that reason shouldn't just be your default action: think about who needs which records and [[scripts in your file | script your sync]] accordingly.
to:
-> Round trip is definitely the most impressive action in GoZync and if you have a fast connection, it's pretty damn cool. GoZync pushes changed records to the host/server, then processes that device's inbox records on the server. Then it searches for changed records and pulls them down to process them into your mobile file.

-> Because the GoZyncHosted inbox is processed while you're connected to the remote files, this can be much slower than just pushing or just pulling. For that reason, round trip shouldn't simply be your default action. Think about who needs which records and [[scripts in your file | script your sync]] accordingly.
July 06, 2012, at 11:46 PM by 50.132.84.245 -
July 06, 2012, at 11:46 PM by 50.132.84.245 -
Changed lines 39-40 from:
!! Field Level Merge
to:
! Field Level Merge
July 06, 2012, at 11:46 PM by 50.132.84.245 -
Changed lines 25-26 from:
-> Pull is ideal for tables where you're never editing the records on the mobile device: such a price lists. You may also want to pull as part of doing a round-trip (see below) manually: so you might push, the wait a bit, knowing the server-side processing will process the uploaded records faster than your iPhone, before calling a pull a few minutes later.
to:
-> Pull is ideal for tables where you're never editing the records on the mobile device: such a price lists. You may also want to pull as part of doing a round-trip (see below) manually: so you might push, the wait a bit, knowing the server-side processing will process the uploaded records faster than your iPhone--and while you're doing something else, before calling a pull 30 minutes later.
Added lines 29-32:
-> Round trip is definitely the most impressive action in GoZync and if you have a fast connection is pretty damn cool. GoZync pushes changed records to the host/server, then processing that device's inbox records on the server, before searching for changed records and pulling them down to process them into your mobile file.

-> Because the GoZyncHosted inbox is processed while you're connected to the remote files, however, this can be much slower than just pushing or just pulling, and for that reason shouldn't just be your default action: think about who needs which records and [[scripts in your file | script your sync]] accordingly.

Added lines 35-38:
In many workflows, users receive work orders or tasks from the host, complete those, and then send the completed tasks back to the host before retrieving the next day's set of tasks. In such cases we've found it helpful to leave the "uploaded" records on the iPhone or iPad so users can see what they did that day (and see that their work was "uploaded").

When "delete sent..." is turned on, users' uploaded records will persist on their mobile device after they are uploaded, but will be deleted from the device as soon as users begin their next pull sync (even as part of a round trip) of that table.

July 06, 2012, at 10:42 PM by 50.132.84.245 -
Changed lines 25-26 from:
-> Pull is idead for tables where you're never editing the records on the mobile device: such a price lists. You may also want to pull as part of doing a round-trip (see below) manually: so you might push, the wait a bit, knowing the server-side processing will process the uploaded records faster than your iPhone, before calling a pull a few minutes later.
to:
-> Pull is ideal for tables where you're never editing the records on the mobile device: such a price lists. You may also want to pull as part of doing a round-trip (see below) manually: so you might push, the wait a bit, knowing the server-side processing will process the uploaded records faster than your iPhone, before calling a pull a few minutes later.
July 06, 2012, at 10:42 PM by 50.132.84.245 -
Added lines 21-26:
-> This is the other side of push; GoZync asks for any records that have changed since the last sync and pulls them down. Along with this will come instructions to [[deletes | delete]] any records that were deleted on the host.

-> After records are pulled they are processed into the local mobile file and the connection is broken. Pull will update existing records on the device if the primary ID of the record is already there, otherwise it will make new records.

-> Pull is idead for tables where you're never editing the records on the mobile device: such a price lists. You may also want to pull as part of doing a round-trip (see below) manually: so you might push, the wait a bit, knowing the server-side processing will process the uploaded records faster than your iPhone, before calling a pull a few minutes later.

July 06, 2012, at 10:34 PM by 50.132.84.245 -
Changed lines 11-18 from:
Push is the fastest way to get records from your mobile device to the host or server. When this is selected, GoZync will send changed records up to the inbox in GoZyncHosted then break the connection to the server.

This is what you'd do for anything you don't need to get modified copies back on the mobile device, or don't need them back right away. Thus "push" is ideal for surveys, building inspections, etc.

Because GoZync stops when the records are safely in the GoZyncHosted inbox, the mobile device never has to open your hosted solution (which can be the slowest part of a sync).

Record left in the GoZyncHosted inbox, can then be processed manually or [[auto processing | with a server side script]] every so often.
to:
-> Push is the fastest way to get records from your mobile device to the host or server. When this is selected, GoZync will send changed records up to the inbox in GoZyncHosted then break the connection to the server.

-> This is what you'd do for anything you don't need to get modified copies back on the mobile device, or don't need them back right away. Thus "push" is ideal for surveys, building inspections, etc.

-> Because GoZync stops when the records are safely in the GoZyncHosted inbox, the mobile device never has to open your hosted solution (which can be the slowest part of a sync).

-> Record left in the GoZyncHosted inbox, can then be processed manually or [[auto processing | with a server side script]] every so often.
July 06, 2012, at 10:33 PM by 50.132.84.245 -
Changed lines 11-12 from:
Push is the fastest way to get records from your mobile device to the host or server. When this is selected,
to:
Push is the fastest way to get records from your mobile device to the host or server. When this is selected, GoZync will send changed records up to the inbox in GoZyncHosted then break the connection to the server.

This is what you'd do for anything you don't need to get modified copies back on the mobile device, or don't need them back right away. Thus "push" is ideal for surveys, building inspections, etc.

Because GoZync stops when the records are safely in the GoZyncHosted inbox, the mobile device never has to open your hosted solution (which can be the slowest part of a sync).

Record left in the GoZyncHosted inbox, can then be processed manually or [[auto processing | with a server side script]] every so often.

July 06, 2012, at 10:29 PM by 50.132.84.245 -
Changed lines 7-8 from:
These options represent the default actions for the file, some like the actions (push, pull, round trip) can be overridden by scripts in your file.
to:
These options represent the default actions for the file, some like the actions (push, pull, round trip) can be overridden by [[scripts in your file]].
Added lines 11-12:
Push is the fastest way to get records from your mobile device to the host or server. When this is selected,
July 06, 2012, at 07:38 PM by 71.212.48.84 -
Changed lines 5-7 from:


to:
%width=500 newwin% [[http://www.seedcode.com/rootimages/stikipad/gozync/zyncoptions.png | http://www.seedcode.com/rootimages/stikipad/gozync/zyncoptionssm.png]]

These options represent the default actions for the file, some like the actions (push, pull, round trip) can be overridden by scripts in your file.

July 06, 2012, at 07:35 PM by 71.212.48.84 -
Added lines 1-7:
!! Overview

Zync options are set at the layout level and thus you can set some options at the layout level as well. Select a layout from the dashboard in GoZyncHosted, click "Integration and Options" and then select the "Zync Options" tab:



July 02, 2012, at 04:26 PM by 50.132.84.245 -
Added lines 1-11:
!! Push

!! Pull

!! Round Trip

!! Delete sent data before next Zync.

!! Field Level Merge

(:include FieldLevelMerge:)
(855) SEEDCODE
support@seedcode.com
Follow us: