Checking out objects

Checking out a form or global object allows you make changes to the object, without having to worry about others overwriting your changes. When you check out an object, Form Control locks the object, so that no one else can make permanent changes to it until you check it back in or unlock it.

You can check out an object only if no one else already has it checked out.

You can check out these objects:

• Forms, with or without their associated templates and/or global objects
• Global objects, regardless of whether they are associated with forms

During a check-out procedure, Form Control performs these tasks:

• Verifies that no one else has the object checked out

  If an object is checked out already, the system displays a message that identifies who has it checked out. You cannot check out the object until the other developer checks it in.

• Warns if device types exist for a form but are not synchronized between databases.

  For more information, see Utilities Tab.

• Copies the object from the master database to the appropriate run-time database and locks it in the master database

  That is, the LockBy column contained in the forms or templates database is set to your user ID, indicating that you have the item checked out. Your Mongoose-based application prevents other developers from checking out or saving changes to any objects that you have checked out.