| Multiexcerpt include macro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
You can also choose to display your application as if it were on a phone or a tablet by selecting the image of a device on the app preview. Selecting the device button will toggle between a mobile phone or tablet:
Phone
...
Tablet
...
There are a few things that you should know when using the app preview feature. When testing your application, the app preview will always use the most recent version of your application, regardless of what the latest release version is. Basically, you will always see a version of your application based on the last time you selected the ‘Save’ button in the application manager or form builder.
In order to ensure you are using the latest version of your application, you will need to select the refresh button on the app preview feature. You will need to press this button after you make any changes that you would like to review. Please note that if you select the refresh button while you are in a form in app preview, you will be returned to the home screen and will need to navigate back to the form that you were in:
...
General Tips:
While this feature allows you to test the most recent version of your application without having to deploy any changes, we do recommend deploying new versions of your application occasionally. This will allow you to have checkpoints to revert your application to in case you make a change that you cannot fix or breaks your application.
We recommend using the 1 question per screen setting, as multiple questions per screen can cause some slowness and performance issues. To enable this, select the ‘Settings’ button from the home screen of ‘Live Preview’ and select enable for this setting.
You can view any other languages you might have configured for your application by proceeding the ‘Settings’ page of Live Preview.
Be sure to sync to receive the latest data for your application, especially when using the 'Login As' functionality.
Limitations:
Same limitations as Web Apps..
User-controlled repeat groups (i.e. Repeat groups where the user defines how many repeats to input) do not currently work. Repeat groups where the repeat count is pre-defined should work.
...
CommCare for Web Users
Web Apps
Users can access web apps by clicking on "Web Apps" at the top of the page. Note that the apps that appear here are the latest released version of the application, to ensure that your latest test changes don't affect current web apps users! This allows for more robust testing and use of the application, as it allows you to preview more than just the form as described in the section above.
...
To enable the Login As feature, you need be logged in as a Web User with certain permissions. The user’s Web User Role will need to have permission to do the following in your project space:
...
With these permissions enabled, you should see a 'Login As' button when using App Preview or Web Apps:
...
Limitations:
Any data submitted this way will be done so as if you were that mobile worker. The data will appear in exports and reports as such.
Any limitations that would apply to a mobile worker in Web Apps.
The only way to confirm a form was submitted on behalf of a mobile worker by a Web User, is to find the specific form itself. You can do this by searching for submissions in the Submit History. Once you find the form in the submit history, there will be a note at the top that states 'Submitted by Web User <name> on behalf of Mobile Worker <name>':
...
The table below is true for all projects created after March 2014; for projects before that, the default for Clicking on the Web Apps button and for accessing Web Apps as a mobile worker was always to use the most recent version, regardless of whether it was starred. If you have specific questions please "report an issue" and the support team will follow up with you.
Point of Access | User Type | App Version |
Clicking on Web Apps at top of CommCareHQ page | Web | Most recent starred version |
Live Preview in application/form manager screens | Web | Most recent version of form (ignores app version) |
Using 'Login As' feature in Live Preview | Mobile | Most recent version of form (ignores app version) |
Using 'Login As' feature as a Web User in Web Apps | Mobile | Most recent starred version |
Using a web app as a Mobile Worker | Mobile | Most recent starred version |
New App Version Prompt
For projects that have shortened inactivity timeout functionality, when a new version of an app is released, users will see a pop up message allowing them to either update to the latest version now or later.
...
The screenshot below shows what the pagination would look like if the case list had over 520 cases, with 10 cases to a page.
...
Navigating to all required questions
When a form is long and has multiple required questions or questions with validation errors spread across the form, it is useful to be able to navigate to all these questions one by one to fix them before submitting the form. For this reason, once you click "Submit," a message box with links to any questions with errors, and a handy navigation button is displayed at the bottom of Web Apps. Clicking on the button will scroll to the next required question or question with validated errors. Once all errors are addressed, the button disappears and the Submit button is enabled. Below is a screenshot.
...
Successful form submission messaging
...
If a Web User is using the Login-As feature, a similar message using the localized name of the form will appear at the top of their screen after a form is successfully submitted without any of the form submission, case, or exporting data links.