Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When the features are disabled, incomplete and saved form records are not created, and all of the user interface options pertaining to them will be removed from the CommCare application's home screen.

Incomplete Forms

Warning

Feature Constraints

Please read the Feature Constraints section before using Incomplete Forms for your project workflows.

...

Incomplete forms are forms that have been started but not finished. This could happen, for example, if the client or user is suddenly called away but plans to finish the form later.

...

If you choose to continue an incomplete form, the original incomplete form you saved will remain saved on the phone unless you save it again or complete the form. If a user pressed theĀ back button and chooses to not save their changes, for instance, the original incomplete form remains as it was before form entry. If the user pressesĀ Save Form on the menu, however, it will update the existing saved form with the new version.

Feature Constraints

Info

Feature Constraints

Saved Incomplete Forms have the following 2 major structural constraints that you should be aware of.

  1. Saved Incomplete Forms are not synced with CommCareHQ and are only stored locally on the mobile device

    1. Consequence: If you lose access to your mobile device, say, it breaks or is lost, Incomplete Forms saved on the device will not be recoverable.

    2. Consequence: If you uninstall an application with incomplete forms, Incomplete Forms saved on the device will not be recoverable.

  2. Saved Incomplete Forms are not updated when you make updates to your app or the data the incomplete forms rely on

    1. Consequence #1: If a form is saved as incomplete, and certain app updates like changes to the form's structure or changes to the assets used by the form (say, images or audio) are made, it can prevent mobile workers from resuming the incomplete form.

    2. Consequence #2: If a form is saved as incomplete, and then resumed after data (say, case properties) the form relies on has changed, the form will have undefined/unpredictable behavior

...