Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

CommTrack from a CommCare App Designer's Perspective

If you are used to designing a CommCare application, there are many parallels from CommCare that might make you understand CommTrack better:

  1. Unlike CommCare where web users can build forms and configure case management, CommTrack app building will be done by developers until CommTrack becomes fully self-service. FMs would need to setup locations, products, and programs for their supply chain. This can be easily done in the relevant project space on HQ.
  2. Each location or supply point is a case in CommTrack just as each registrant (mother, child, farmer) is a case in CommCare.
  3. Unlike CommCare where cases are registered, updated, and closed by mobile users, locations in CommTrack can only be created by web users. 
  4. Each location / supply point is associated with a set of products. Products are managed through lookup tables ("fixtures"), not cases.

When CommTrack is enabled for a given CommCare domain, you'll notice the following differences. None of these changes should break any pre-existing apps.

  1. A tab labeled 'Setup' appears on the top navigation bar: This is where web users can set up the locations and products for the project's supply chain
  2. In the 'Reports' tab, a set of five CommTrack reports appears. 
  3. Additional CommTrack-specific settings are available when configuring web users, mobile users, and the project settings

 

  • No labels