| Multiexcerpt include macro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Web apps can be used for:
Testing CommCare applications or forms
A data entry person who needs to be able to modify a mobile users case list or add additional data
Cases from mobile applications that are shared with a web app- for example, allowing a nurse at a clinic to update cases when patients visit. A Community Health Worker with a mobile handset is then able to view the updates from the clinic and see what instructions the patient was given.
Using Web Apps: A quick introduction to setting up and using web apps
Web Apps is the web version of CommCare. There are two ways you can use Web Apps:
To test forms (using the “App Preview” feature) - you can preview your form in a virtual device that appears on the right hand side of the screen in App Manager or Form Builder.
To submit data - mobile workers can log into Web Apps on a computer just like they would log into a CommCare mobile application. Web Users can also use Web Apps, but data is treated differently for a web user. More information on this point below.
| Table of Contents |
|---|
...
First, are Web Apps Right For Me?
We recommend you use the Google Chrome web browser.
Other browsers may work, but are not fully supported.
How is Web Apps different than Mobile Apps?
Case sharing as a web user is not supported.
No mobile-specific user interface settings (e.g. Sense mode) are honored.
The time portion of 'format-date' does not work well. Time portion always shows up as 00:00:00 in Web Apps.
The "default language" setting is not honored for applications. User-specific language setting is used instead for both Web and Mobile users.
Groups that contain only hidden values will be shown as empty groups in Web Apps if the display condition of the group is met.
Case List Menu Item setting for a module.
Alternative calendar formats are not supported.
Multimedia upload and capture (Image, Video, Audio) are not supported.
Most advanced Android formatting options are not respected.
Audio files on multiple choice question choices will not show or play.
Images on multiple choice question choices will not show or play.
Images and audio files on buttons will not show or play.
Incomplete Forms are available if at least one application in the project space has them enabled.
Incomplete forms on Web Apps are deleted automatically after 7 days.
User controlled repeat groups don't get rendered when mixed with repeat group of other types in the same form. To work around this issue , it is possible to ask the user how many repeats they require.
Having multiple tabs open on your browser with Web Apps is known to have caused some performance issues in the past. We'd generally recommend not opening Web Apps for data collection in multiple tabs / groups.
'Phone Number' format in case list in not supported on Web Apps. The phone number will not be displayed in the case list as highlighted.
End of Form Navigation using Home screen is not supported on Web Apps. When utilizing End of Form Navigation, Web Apps users wishing to return to the list of menus/modules should use 'First Menu' and not 'Home Screen.'
Web Apps supports the
here()function expression in persistent entity views, which are unsupported on the Android platform
Application Preview
| Warning |
|---|
Live DataPlease note that when using Application Preview, you are submitting live data to your project space. When submitting data as a web user, it will appear as if submitted by an unknown user and will only appear in exports or reports if specified (via filters). |
...
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.
...
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:
...
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>':
...
For more information on the Login As feature, please see this document.
...
CommCare for Mobile Workers
Lastly, you can also use your mobile username to view your case list and fill out forms on the web just as you would on a mobile phone.
...
NOTE: The language will not switch if you use "login as" to log in as the mobile worker. You will have to separately log in using the username and password of the mobile worker to be able to see the app display in the desired language for the mobile worker.
For more information, please see the Login As Feature
Custom Logo
You can upload an image in Application Settings to use as the logo of your app on the main Web Apps page, in place of the CommCare logo.
...
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.