Scriptable
GoZync3.Scriptable History
Hide minor edits - Show changes to output
Changed lines 9-10 from:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using its built in [[logs]] you can look inside, see what it's doing, and change it. (%newwin%[[http://seedcodenext.wordpress.com/2013/02/01/tip-debugging-using-gozyncs-logs/ | Searching the scripts]] for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
to:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using its built in [[logs]] you can look inside, see what it's doing, and change it. (%newwin%[[http://www.seedcode.com/tip-debugging-using-gozyncs-logs/ | Searching the scripts]] for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
Changed line 15 from:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see %newwin%[[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | "Modular Sync and the Urgency of Mobile Work"]].)
to:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see %newwin%[[http://www.seedcode.com/modular-sync-and-the-urgency-of-mobile-work/ | "Modular Sync and the Urgency of Mobile Work"]].)
Changed lines 7-8 from:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (%newwin%[[http://seedcodenext.wordpress.com/2013/02/01/tip-debugging-using-gozyncs-logs/ | Searching the scripts]] for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
to:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using its built in [[logs]] you can look inside, see what it's doing, and change it. (%newwin%[[http://seedcodenext.wordpress.com/2013/02/01/tip-debugging-using-gozyncs-logs/ | Searching the scripts]] for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
Changed lines 7-8 from:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (Searching the scripts for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
to:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (%newwin%[[http://seedcodenext.wordpress.com/2013/02/01/tip-debugging-using-gozyncs-logs/ | Searching the scripts]] for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
Changed lines 7-8 from:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (searching the scripts for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
to:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (Searching the scripts for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
Changed lines 3-4 from:
We mean that you can get inside the sync and change the way it works just as you'd change your own FileMaker scripts. This lets you create a sync that matches your workflow.
to:
We mean that you can get inside the sync and change the way it works--just as you'd change your own FileMaker scripts. This lets you create a sync that matches your workflow.
Changed lines 13-14 from:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin%[[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]] ")
to:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see %newwin%[[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | "Modular Sync and the Urgency of Mobile Work"]].)
Changed lines 13-14 from:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin% [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
to:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin%[[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]] ")
Changed lines 13-14 from:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see " %newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
to:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin% [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
Changed lines 13-14 from:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
to:
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see " %newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
Changed lines 7-8 from:
When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (searching the scripts for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
to:
-> When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (searching the scripts for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
Changed lines 11-16 from:
You can tell GoZync what to so: sometimes you may want to sync just one record. Or push new orders up to your hosted system *without* pulling down ''all'' the new product prices. And as a developer you can decide how much of this flexibility to give to your mobile users.
Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
And you get this flexibility without having to dig into scripts: GoZync has a series of simple API scripts whose parameters tell it what kind of sync you'd like to perform. Learn more about these [[Zync It]] scripts.
Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
And you get this flexibility without having to dig into scripts: GoZync has a series of simple API scripts whose parameters tell it what kind of sync you'd like to perform. Learn more about these [[Zync It]] scripts.
to:
-> You can tell GoZync what to so: sometimes you may want to sync just one record. Or push new orders up to your hosted system *without* pulling down ''all'' the new product prices. And as a developer you can decide how much of this flexibility to give to your mobile users.
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
-> And you get this flexibility without having to dig into scripts: GoZync has a series of simple API scripts whose parameters tell it what kind of sync you'd like to perform. Learn more about these [[Zync It]] scripts.
-> Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
-> And you get this flexibility without having to dig into scripts: GoZync has a series of simple API scripts whose parameters tell it what kind of sync you'd like to perform. Learn more about these [[Zync It]] scripts.
Changed lines 19-20 from:
We know you have workflow already in your system--script triggers, conditions, and processes that need to be spawned when a record is edited. GoZync provides hooks for you to call these scripts, both [[BeforeEditingEntity | before]] a record is pulled down to mobile, and [[AfterCommittingEntity | after]] it is pushed back to your hosted files.
to:
-> We know you have workflow already in your system--script triggers, conditions, and processes that need to be spawned when a record is edited. GoZync provides hooks for you to call these scripts, both [[BeforeEditingEntity | before]] a record is pulled down to mobile, and [[AfterCommittingEntity | after]] it is pushed back to your hosted files.
Changed lines 3-20 from:
to:
We mean that you can get inside the sync and change the way it works just as you'd change your own FileMaker scripts. This lets you create a sync that matches your workflow.
'''Built Solely in FileMaker Pro'''
When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (searching the scripts for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
'''Call Different Sync Actions as You Need Them'''
You can tell GoZync what to so: sometimes you may want to sync just one record. Or push new orders up to your hosted system *without* pulling down ''all'' the new product prices. And as a developer you can decide how much of this flexibility to give to your mobile users.
Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
And you get this flexibility without having to dig into scripts: GoZync has a series of simple API scripts whose parameters tell it what kind of sync you'd like to perform. Learn more about these [[Zync It]] scripts.
'''Trigger Your Own Scripted Processes as Part of Sync'''
We know you have workflow already in your system--script triggers, conditions, and processes that need to be spawned when a record is edited. GoZync provides hooks for you to call these scripts, both [[BeforeEditingEntity | before]] a record is pulled down to mobile, and [[AfterCommittingEntity | after]] it is pushed back to your hosted files.
'''Built Solely in FileMaker Pro'''
When we say "scriptable" we mean it: all the work of GoZync is done in FileMaker scripts. There are no plugins or webcode to worry about. GoZync is not a black box, and using it's built in [[logs]] you can look inside, see what it's doing, and change it. (searching the scripts for strings you find in the logs is one of the great ways to find the precise script where GoZync is, for example, building your found set to sync.)
'''Call Different Sync Actions as You Need Them'''
You can tell GoZync what to so: sometimes you may want to sync just one record. Or push new orders up to your hosted system *without* pulling down ''all'' the new product prices. And as a developer you can decide how much of this flexibility to give to your mobile users.
Flexibility like this suits the ''urgency'' of mobile work. (For more, see "%newwin [[http://seedcodenext.wordpress.com/2012/10/09/modular-sync-and-the-urgency-of-mobile-work/ | Modular Sync and the Urgency of Mobile Work]]")
And you get this flexibility without having to dig into scripts: GoZync has a series of simple API scripts whose parameters tell it what kind of sync you'd like to perform. Learn more about these [[Zync It]] scripts.
'''Trigger Your Own Scripted Processes as Part of Sync'''
We know you have workflow already in your system--script triggers, conditions, and processes that need to be spawned when a record is edited. GoZync provides hooks for you to call these scripts, both [[BeforeEditingEntity | before]] a record is pulled down to mobile, and [[AfterCommittingEntity | after]] it is pushed back to your hosted files.
