Checking Out Records
GoZync4.CheckingOutRecords History
Hide minor edits - Show changes to output
Added lines 18-19:
-> Todd Geist also demonstrates checkout as part of his %newwin% [[https://www.geistinteractive.com/2014/03/26/filemaker-sync-3-gozync-features/ | "Three Favorite GoZync Features"]].
Changed line 15 from:
Checkout in Action.
to:
'''Checkout in Action.'''
Added lines 14-17:
Checkout in Action.
-> Watch this %newwin% [[http://www.youtube.com/watch?v=c-l_Rxp_wXQ |short video of checkout in action]], along with a walkthrough of how we do it.
Changed line 33 from:
That's it.
to:
That's all. Pretty cool, isn't it?
Changed lines 17-20 from:
Getting this working in your solution is pretty simple. Reading up on [[downloading found sets]] will help give you come context for the changes that follow. You'll also use [[Custom Field Mapping]] to implement this, so read up on that as well (custom field mapping is one of the most powerful features of GoZync).
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncingas there won't be a matching field on he mobile side. Create a branch in the script "Custom Field Mapping: Transformation and Hooks" for your table-- you'll create a branch for both the push and the pull, that is for both "gzm_YourTable" and "gzh_YourTable".
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncing
to:
Getting this working in your solution is pretty simple. Reading up on [[downloading found sets]] will help give you some context for the changes that follow. You'll also use [[Custom Field Mapping]] to implement this, so read up on that as well (custom field mapping is one of the most powerful features of GoZync 4).
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncing in GoZyncMobile as there won't be a matching field on the mobile side. Create a branch in the script "Custom Field Mapping: Transformation and Hooks" for your table-- you'll create a branch for both the push and the pull, that is for both "gzm_YourTable" and "gzh_YourTable".
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncing in GoZyncMobile as there won't be a matching field on the mobile side. Create a branch in the script "Custom Field Mapping: Transformation and Hooks" for your table-- you'll create a branch for both the push and the pull, that is for both "gzm_YourTable" and "gzh_YourTable".
Changed lines 25-26 from:
--> In the "push" branch--the one based on "gzm_YourTable"-- you'd the clear your checked out field or set it to a literal value like "0" like this:
to:
--> In the "push" branch--the one based on "gzm_YourTable"-- you'd then clear your checked out field or set it to a literal value like "0" like this:
Added lines 29-30:
-> Not that in both the push and the pull it is the ''hosted'' record we're editing when it comes to checkout. This may be a little different than other SetField() steps you have going on that script where on the pull you're often setting fields in mobile records.
Changed lines 11-14 from:
-> Then, access privileges in your solution prevent checked out records from being edited. This is great because users on the hosted solution (users "in the office") can edit records up until the moment a mobile user checks them out. Imagine: updating trouble ticket details up until the moment a mobile technician actually begins heading to the customer's location, but being prevented from changing it after that. Users would then know they need to call the mobile technician to communicate any new details about the ticket.
-> Once the ticket is resolved and the mobile user syncs their updated ticket back to the hosted solution, the ticket is "checked back in" and is now editable again.
-> Once
to:
-> You'd then enforce the checkout--and lock the record--by crafting access privileges in your hosted solution that prevent checked out records from being edited. This is great because users on the hosted solution (users "in the office") can edit records up until the moment a mobile user checks them out. Imagine: updating trouble ticket details up until the moment a mobile technician actually begins heading to the customer's location, but being prevented from changing it after that. Users in the office would then know they need to call the mobile technician to communicate any new details about the now checked out ticket.
-> Once the ticket is resolved and the mobile user syncs their updated ticket back to the hosted solution, the ticket is "checked back in" and is now editable again by users in the office.
-> Once the ticket is resolved and the mobile user syncs their updated ticket back to the hosted solution, the ticket is "checked back in" and is now editable again by users in the office.
Changed lines 1-2 from:
!! Can I "check out" records so only the mobile own can edit them?
to:
!! Can I "check out" records so only the mobile user can edit them?
Changed lines 23-24 from:
--->SetField [ gzm_YourTable::checked_out ; 1 ]
to:
--->SetField [ gzh_YourTable::checked_out ; 1 ]
Changed lines 27-28 from:
--->SetField [ gzm_YourTable::checked_out ; 0 ]
to:
--->SetField [ gzh_YourTable::checked_out ; 0 ]
Changed lines 17-24 from:
Getting this working in your solution is pretty simple. Reading up on [[downloading found sets]] will help give you come context for the changes that follow.
->''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncing as there won't be a matching field on he mobile side. Edit the script "Edit Record being Pulled (TOName)" and create a branch (an If statement like the example there) which tests for the Table Occurrence name you're interested in. Then set the checked out field in that table.
-> '''Preventing edits of checked out records.''' In your hosted solution, use FileMaker's built in access privileges to prevent editing of records where "checked out" is not empty. In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
-> '''Checking in.''' Edit the script "After Committing Entity" and you'll see branches similar to those in "Edit Record..." above. Create a branch for your table occurrence and set the "checked out" field to blank (use two quotes without a space between them).
->
-> '''Preventing edits of checked out records.
to:
Getting this working in your solution is pretty simple. Reading up on [[downloading found sets]] will help give you come context for the changes that follow. You'll also use [[Custom Field Mapping]] to implement this, so read up on that as well (custom field mapping is one of the most powerful features of GoZync).
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncing as there won't be a matching field on he mobile side. Create a branch in the script "Custom Field Mapping: Transformation and Hooks" for your table-- you'll create a branch for both the push and the pull, that is for both "gzm_YourTable" and "gzh_YourTable".
--> In the "pull" branch--the one based on "gzh_YourTable"-- set your checked out field to a literal value like "1" like this:
--->SetField [ gzm_YourTable::checked_out ; 1 ]
--> In the "push" branch--the one based on "gzm_YourTable"-- you'd the clear your checked out field or set it to a literal value like "0" like this:
--->SetField [ gzm_YourTable::checked_out ; 0 ]
-> '''Preventing edits of checked out records.''' In your hosted solution, use FileMaker's built-in access privileges to prevent editing of records where "checked out" is not empty (or zero). In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncing as there won't be a matching field on he mobile side. Create a branch in the script "Custom Field Mapping: Transformation and Hooks" for your table-- you'll create a branch for both the push and the pull, that is for both "gzm_YourTable" and "gzh_YourTable".
--> In the "pull" branch--the one based on "gzh_YourTable"-- set your checked out field to a literal value like "1" like this:
--->SetField [ gzm_YourTable::checked_out ; 1 ]
--> In the "push" branch--the one based on "gzm_YourTable"-- you'd the clear your checked out field or set it to a literal value like "0" like this:
--->SetField [ gzm_YourTable::checked_out ; 0 ]
-> '''Preventing edits of checked out records.''' In your hosted solution, use FileMaker's built-in access privileges to prevent editing of records where "checked out" is not empty (or zero). In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
December 17, 2012, at 10:17 PM
by - minor edits and clarifications
Changed lines 9-12 from:
-> (Remember, users can [[downloading found sets | download just their own records]], so it's not like it would be a surprise who downloaded the record, but seeing the name can give you an extra sense of reassurance, and can remind staffers--who may not know all the business rules--who owns which records.)
-> Then, access privileges in your solution prevent checked out records from being edited. This is great because users on the hosted solution (users "in the office") can edit records up until the moment a mobile user checks them out: imagine, updating trouble ticket details up until the moment a mobile technician actually begins heading to the customer's location, but being prevented from changing it after that. Users would then know they need to call the mobile technician to communicate any new details about the ticket.
-> Then, access privileges in your solution prevent checked out records from being edited. This is great because users on the hosted solution (users "in the office") can edit records up until the moment a mobile user checks them out:
to:
-> (Remember, users can [[downloading found sets | download just their own records]], so it's not like it would be a surprise who downloaded the record, but seeing the name can give you an extra sense of reassurance, and can remind staffers – who may not know all the business rules – who owns which records.)
-> Then, access privileges in your solution prevent checked out records from being edited. This is great because users on the hosted solution (users "in the office") can edit records up until the moment a mobile user checks them out. Imagine: updating trouble ticket details up until the moment a mobile technician actually begins heading to the customer's location, but being prevented from changing it after that. Users would then know they need to call the mobile technician to communicate any new details about the ticket.
-> Then, access privileges in your solution prevent checked out records from being edited. This is great because users on the hosted solution (users "in the office") can edit records up until the moment a mobile user checks them out. Imagine: updating trouble ticket details up until the moment a mobile technician actually begins heading to the customer's location, but being prevented from changing it after that. Users would then know they need to call the mobile technician to communicate any new details about the ticket.
Changed lines 17-20 from:
Getting this working in your solution i s pretty simple. Reading up on [[downloading found sets]] will help give you come context for the changes that follow.
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used forzyncing as there won't be a matching field on he mobile side.Edit the script "Edit Record being Pulled (TOName)" and create a branch (an If statement like the example there) which tests for the Table Occurrence name you're interested in: the set the checked out field in that table.
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for
to:
Getting this working in your solution is pretty simple. Reading up on [[downloading found sets]] will help give you come context for the changes that follow.
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncing as there won't be a matching field on he mobile side. Edit the script "Edit Record being Pulled (TOName)" and create a branch (an If statement like the example there) which tests for the Table Occurrence name you're interested in. Then set the checked out field in that table.
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for Zyncing as there won't be a matching field on he mobile side. Edit the script "Edit Record being Pulled (TOName)" and create a branch (an If statement like the example there) which tests for the Table Occurrence name you're interested in. Then set the checked out field in that table.
Changed lines 19-24 from:
-> Checking out. Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for zyncing as there won't be a matching field on he mobile side.Edit the script "Edit Record being Pulled (TOName)" and create a branch (an If statement like the example there) which tests for the Table Occurrence name you're interested in: the set the checked out field in that table.
-> Preventing edits of checked out records. In your hosted solution, use FileMaker's built in access privileges to prevent editing of records where "checked out" is not empty. In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
-> Checking in. Edit the script "After Committing Entity" and you'll see branches similar to those in "Edit Record..." above. Create a branch for your table occurrence and set the "checked out" field to blank (use two quotes without a space between them).
-> Preventing edits of checked out records. In your hosted solution, use FileMaker's built in access privileges to prevent editing of records where "checked out" is not empty. In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
-> Checking in. Edit the script "After Committing Entity" and you'll see branches similar to those in "Edit Record..." above. Create a branch for your table occurrence and set the "checked out" field to blank (use two quotes without a space between them).
to:
-> '''Checking out.''' Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for zyncing as there won't be a matching field on he mobile side.Edit the script "Edit Record being Pulled (TOName)" and create a branch (an If statement like the example there) which tests for the Table Occurrence name you're interested in: the set the checked out field in that table.
-> '''Preventing edits of checked out records.''' In your hosted solution, use FileMaker's built in access privileges to prevent editing of records where "checked out" is not empty. In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
-> '''Checking in.''' Edit the script "After Committing Entity" and you'll see branches similar to those in "Edit Record..." above. Create a branch for your table occurrence and set the "checked out" field to blank (use two quotes without a space between them).
-> '''Preventing edits of checked out records.''' In your hosted solution, use FileMaker's built in access privileges to prevent editing of records where "checked out" is not empty. In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
-> '''Checking in.''' Edit the script "After Committing Entity" and you'll see branches similar to those in "Edit Record..." above. Create a branch for your table occurrence and set the "checked out" field to blank (use two quotes without a space between them).
Changed lines 3-25 from:
to:
Absolutely. In fact, this is one of the most useful workflows GoZync enables. ''Note that checkout is not supported in the free version of GoZync.''
'''What checkout looks like.'''
-> When users pull records down from your hosted solution, the record is marked as "checked out". You can simply set a field called "out" to 1, or record something more elaborate, like the name of the user who downloaded it, and when they did so.
-> (Remember, users can [[downloading found sets | download just their own records]], so it's not like it would be a surprise who downloaded the record, but seeing the name can give you an extra sense of reassurance, and can remind staffers--who may not know all the business rules--who owns which records.)
-> Then, access privileges in your solution prevent checked out records from being edited. This is great because users on the hosted solution (users "in the office") can edit records up until the moment a mobile user checks them out: imagine, updating trouble ticket details up until the moment a mobile technician actually begins heading to the customer's location, but being prevented from changing it after that. Users would then know they need to call the mobile technician to communicate any new details about the ticket.
-> Once the ticket is resolved and the mobile user syncs their updated ticket back to the hosted solution, the ticket is "checked back in" and is now editable again.
'''How to implement it.'''
Getting this working in your solution i s pretty simple. Reading up on [[downloading found sets]] will help give you come context for the changes that follow.
-> Checking out. Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for zyncing as there won't be a matching field on he mobile side.Edit the script "Edit Record being Pulled (TOName)" and create a branch (an If statement like the example there) which tests for the Table Occurrence name you're interested in: the set the checked out field in that table.
-> Preventing edits of checked out records. In your hosted solution, use FileMaker's built in access privileges to prevent editing of records where "checked out" is not empty. In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
-> Checking in. Edit the script "After Committing Entity" and you'll see branches similar to those in "Edit Record..." above. Create a branch for your table occurrence and set the "checked out" field to blank (use two quotes without a space between them).
That's it.
'''What checkout looks like.'''
-> When users pull records down from your hosted solution, the record is marked as "checked out". You can simply set a field called "out" to 1, or record something more elaborate, like the name of the user who downloaded it, and when they did so.
-> (Remember, users can [[downloading found sets | download just their own records]], so it's not like it would be a surprise who downloaded the record, but seeing the name can give you an extra sense of reassurance, and can remind staffers--who may not know all the business rules--who owns which records.)
-> Then, access privileges in your solution prevent checked out records from being edited. This is great because users on the hosted solution (users "in the office") can edit records up until the moment a mobile user checks them out: imagine, updating trouble ticket details up until the moment a mobile technician actually begins heading to the customer's location, but being prevented from changing it after that. Users would then know they need to call the mobile technician to communicate any new details about the ticket.
-> Once the ticket is resolved and the mobile user syncs their updated ticket back to the hosted solution, the ticket is "checked back in" and is now editable again.
'''How to implement it.'''
Getting this working in your solution i s pretty simple. Reading up on [[downloading found sets]] will help give you come context for the changes that follow.
-> Checking out. Create a "checked out" field in your hosted solution. Feel free to add this to layouts, but don't add it to the layout used for zyncing as there won't be a matching field on he mobile side.Edit the script "Edit Record being Pulled (TOName)" and create a branch (an If statement like the example there) which tests for the Table Occurrence name you're interested in: the set the checked out field in that table.
-> Preventing edits of checked out records. In your hosted solution, use FileMaker's built in access privileges to prevent editing of records where "checked out" is not empty. In relational solutions you'll want to apply this restriction to child records as well: one should not be able to edit an invoice line item if the invoice is checked out, for example.
-> Checking in. Edit the script "After Committing Entity" and you'll see branches similar to those in "Edit Record..." above. Create a branch for your table occurrence and set the "checked out" field to blank (use two quotes without a space between them).
That's it.
Added lines 1-3:
!! Can I "check out" records so only the mobile own can edit them?
Yes. Coming soon.
Yes. Coming soon.
