...
If you are used to designing a CommCare application, there are many parallels from CommCare that might make you understand CommTrack better:
- Unlike CommCare where FMs web users can build forms and configure case management, CommTrack app building would largely 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.
- Each location or supply point is a case in CommTrack just as each registrant (mother, child, farmer) is a case in CommCare.
- Unlike CommCare where cases are registered, updated, and closed by mobile users, locations in CommTrack can only be created by web users. Cases in CommTrack are updated following certain supply chain actions. Example: Once the requested commodity is delivered, you fulfill the requisition by updating the case.
- Each location / supply point is associated with a set of products. There are fixture itemsProducts are managed through lookup tables ("fixtures"), not cases.
UI Changes in a CommTrack-Enabled Domain
Upon enabling CommTrack under Project Settings -> Feature Previews in HQ, the following UI changes would be observed:
...
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.
- 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
- In the 'Reports' tab, a set of five CommTrack reports appears. The 'Manage Deployments' web reports are hidden in CommTrack
- Additional CommTrack-specific settings are available when configuring web users or , mobile users
...
- , and the project settings