Is it possible to show a filtered list of forms

We would like our pregnancy module to show a prenatal visit form when the
the delivery date is not known, and a postpartum visit form when the
delivery date is known. In our scenario, the delivery date is stored as a
pregnancy case property. Is it possible to filter the list of forms to
support this use case? (e.g. to hide the postpartum visit form when the
delivery date is null and hide the prenatal visit form when the delivery
date is not null)?

Thanks, Ray

Ray,

Unfortunately, if your app is built in HQ this feature isn’t exposed by the
UI builder yet. It is something we’re hoping to include in the future.

If you’re running a remote application, it’s possible to manually configure
your suite file to filter a form entry option with a relevant="" attribute
on the declaration (details here, for any interested users on the
list https://bitbucket.org/commcare/commcare/wiki/Suite20)

-Clayton

··· On Fri, Nov 16, 2012 at 10:03 AM, Ray Brunsting wrote:

We would like our pregnancy module to show a prenatal visit form when the
the delivery date is not known, and a postpartum visit form when the
delivery date is known. In our scenario, the delivery date is stored as a
pregnancy case property. Is it possible to filter the list of forms to
support this use case? (e.g. to hide the postpartum visit form when the
delivery date is null and hide the prenatal visit form when the delivery
date is not null)?

Thanks, Ray

Hey Clayton,

We're building the app with the HQ UI and prefer to avoid manually
configuring the suite file (we do create the xforms and casexml outside of
the UI).

Given that you are hoping to expose this feature in the HQ UI at some
point, we'll likely wait to see this become available in an upcoming
monthly release. :slight_smile:

Thanks, Ray

··· On Friday, November 16, 2012 11:28:04 AM UTC-5, Clayton Sims wrote: > > Ray, > > Unfortunately, if your app is built in HQ this feature isn't exposed by > the UI builder yet. It is something we're hoping to include in the future. > > If you're running a remote application, it's possible to manually > configure your suite file to filter a form entry option with a relevant="" > attribute on the declaration (details here, for any interested > users on the list https://bitbucket.org/commcare/commcare/wiki/Suite20) > > -Clayton > > On Fri, Nov 16, 2012 at 10:03 AM, Ray Brunsting <r...@tula.org wrote: > >> We would like our pregnancy module to show a prenatal visit form when the >> the delivery date is not known, and a postpartum visit form when the >> delivery date is known. In our scenario, the delivery date is stored as a >> pregnancy case property. Is it possible to filter the list of forms to >> support this use case? (e.g. to hide the postpartum visit form when the >> delivery date is null and hide the prenatal visit form when the delivery >> date is not null)? >> >> Thanks, Ray >> > >

Hi Ray,

Until form filtering comes out on HQ, some other users have opted for the
following workflow, which takes advantage of module-level filters:

If you break apart your maternal health module into a prenatal module and a
postnatal module, you can use the module filters to ensure only postpartum
mothers show up in the postnatal module's case list, and only pre-partum
mothers show up in the prenatal module's case list.

Your application outline would look like this:

Register mother form
Prenatal Module [filtered to prenatal='yes']
Visit form
Outcome form
Postnatal Module [filtered to prenatal='no']
Visit form
Close form

The Outcome form would properly set the prenatal case property from 'yes'
to 'no'.

This ensures CHWs never accidentally submit a prenatal visit form against a
post-partum mother, and vice versa.

Thanks,
Amelia

··· On Fri, Nov 16, 2012 at 12:50 PM, Ray Brunsting wrote:

Hey Clayton,

We're building the app with the HQ UI and prefer to avoid manually
configuring the suite file (we do create the xforms and casexml outside of
the UI).

Given that you are hoping to expose this feature in the HQ UI at some
point, we'll likely wait to see this become available in an upcoming
monthly release. :slight_smile:

Thanks, Ray

On Friday, November 16, 2012 11:28:04 AM UTC-5, Clayton Sims wrote:

Ray,

Unfortunately, if your app is built in HQ this feature isn't exposed by
the UI builder yet. It is something we're hoping to include in the future.

If you're running a remote application, it's possible to manually
configure your suite file to filter a form entry option with a relevant=""
attribute on the declaration (details here, for any interested
users on the list https://bitbucket.org/**commcare/commcare/wiki/Suite20https://bitbucket.org/commcare/commcare/wiki/Suite20
**)

-Clayton

On Fri, Nov 16, 2012 at 10:03 AM, Ray Brunsting r...@tula.org wrote:

We would like our pregnancy module to show a prenatal visit form when
the the delivery date is not known, and a postpartum visit form when the
delivery date is known. In our scenario, the delivery date is stored as a
pregnancy case property. Is it possible to filter the list of forms to
support this use case? (e.g. to hide the postpartum visit form when the
delivery date is null and hide the prenatal visit form when the delivery
date is not null)?

Thanks, Ray

Hi Amelia.

Great to know that module level filtering is feasible (I missed that).
Splitting modules in this way makes good sense and is something we may
want to try elsewhere too. In the meantime, we’ve implemented logic within
these forms to warn the user if they attempt to complete an incorrect form.

Thanks for the great suggestion,
Ray

··· On Friday, November 16, 2012 1:25:16 PM UTC-5, Amelia Sagoff wrote: > > Hi Ray, > > Until form filtering comes out on HQ, some other users have opted for the > following workflow, which takes advantage of module-level filters: > > If you break apart your maternal health module into a prenatal module and > a postnatal module, you can use the module filters to ensure only > postpartum mothers show up in the postnatal module's case list, and only > pre-partum mothers show up in the prenatal module's case list. > > Your application outline would look like this: > > Register mother form > Prenatal Module [filtered to prenatal='yes'] > Visit form > Outcome form > Postnatal Module [filtered to prenatal='no'] > Visit form > Close form > > The Outcome form would properly set the prenatal case property from 'yes' > to 'no'. > > This ensures CHWs never accidentally submit a prenatal visit form against > a post-partum mother, and vice versa. > > Thanks, > Amelia > > > On Fri, Nov 16, 2012 at 12:50 PM, Ray Brunsting <r...@tula.org wrote: > >> Hey Clayton, >> >> We're building the app with the HQ UI and prefer to avoid manually >> configuring the suite file (we do create the xforms and casexml outside of >> the UI). >> >> Given that you are hoping to expose this feature in the HQ UI at some >> point, we'll likely wait to see this become available in an upcoming >> monthly release. :) >> >> Thanks, Ray >> >> >> On Friday, November 16, 2012 11:28:04 AM UTC-5, Clayton Sims wrote: >> >>> Ray, >>> >>> Unfortunately, if your app is built in HQ this feature isn't exposed by >>> the UI builder yet. It is something we're hoping to include in the future. >>> >>> If you're running a remote application, it's possible to manually >>> configure your suite file to filter a form entry option with a relevant="" >>> attribute on the declaration (details here, for any interested >>> users on the list https://bitbucket.org/**commcare/commcare/wiki/Suite20 >>> **) >>> >>> -Clayton >>> >>> >>> On Fri, Nov 16, 2012 at 10:03 AM, Ray Brunsting wrote: >>> >>>> We would like our pregnancy module to show a prenatal visit form when >>>> the the delivery date is not known, and a postpartum visit form when the >>>> delivery date is known. In our scenario, the delivery date is stored as a >>>> pregnancy case property. Is it possible to filter the list of forms to >>>> support this use case? (e.g. to hide the postpartum visit form when the >>>> delivery date is null and hide the prenatal visit form when the delivery >>>> date is not null)? >>>> >>>> Thanks, Ray >>>> >>> >>> >

Hi Ray,

Glad you found that useful!

You can find documentation on how to set up module-level filters here:
https://confluence.dimagi.com/display/commcarepublic/Case+List+and+Case+Detail+View+Configuration

(see #9 in configuring the case list and details view). We're hoping to
improve the way you specify module-level filters and make it more prominent
in the future.

Thanks,
Amelia

··· On Fri, Nov 16, 2012 at 1:47 PM, Ray Brunsting wrote:

Hi Amelia.

Great to know that module level filtering is feasible (I missed that).
Splitting modules in this way makes good sense and is something we may
want to try elsewhere too. In the meantime, we've implemented logic within
these forms to warn the user if they attempt to complete an incorrect form.

Thanks for the great suggestion,
Ray

On Friday, November 16, 2012 1:25:16 PM UTC-5, Amelia Sagoff wrote:

Hi Ray,

Until form filtering comes out on HQ, some other users have opted for the
following workflow, which takes advantage of module-level filters:

If you break apart your maternal health module into a prenatal module and
a postnatal module, you can use the module filters to ensure only
postpartum mothers show up in the postnatal module's case list, and only
pre-partum mothers show up in the prenatal module's case list.

Your application outline would look like this:

Register mother form
Prenatal Module [filtered to prenatal='yes']
Visit form
Outcome form
Postnatal Module [filtered to prenatal='no']
Visit form
Close form

The Outcome form would properly set the prenatal case property from 'yes'
to 'no'.

This ensures CHWs never accidentally submit a prenatal visit form against
a post-partum mother, and vice versa.

Thanks,
Amelia

On Fri, Nov 16, 2012 at 12:50 PM, Ray Brunsting r...@tula.org wrote:

Hey Clayton,

We're building the app with the HQ UI and prefer to avoid manually
configuring the suite file (we do create the xforms and casexml outside of
the UI).

Given that you are hoping to expose this feature in the HQ UI at some
point, we'll likely wait to see this become available in an upcoming
monthly release. :slight_smile:

Thanks, Ray

On Friday, November 16, 2012 11:28:04 AM UTC-5, Clayton Sims wrote:

Ray,

Unfortunately, if your app is built in HQ this feature isn't exposed by
the UI builder yet. It is something we're hoping to include in the future.

If you're running a remote application, it's possible to manually
configure your suite file to filter a form entry option with a relevant=""
attribute on the declaration (details here, for any interested
users on the list https://bitbucket.org/com
mcare/commcare/wiki/Suite20https://bitbucket.org/commcare/commcare/wiki/Suite20
**)

-Clayton

On Fri, Nov 16, 2012 at 10:03 AM, Ray Brunsting r...@tula.org wrote:

We would like our pregnancy module to show a prenatal visit form when
the the delivery date is not known, and a postpartum visit form when the
delivery date is known. In our scenario, the delivery date is stored as a
pregnancy case property. Is it possible to filter the list of forms to
support this use case? (e.g. to hide the postpartum visit form when the
delivery date is null and hide the prenatal visit form when the delivery
date is not null)?

Thanks, Ray