Automatically closing sub-cases with case

Hi all,

My colleagues and I are designing a household survey instrument with a
structure similar to Use Case 1 described in
https://confluence.dimagi.com/display/commcarepublic/Household+Survey+Workflows

··· -- i.e., household cases and household member sub-cases.

After interviewing all of the members within each household, we would like
the enumerator to close the HH case, so that it’s permanently removed from
the HH case list. Upon doing so, we would like all of the HH member
sub-cases for that HH case to automatically be closed as well. Is this
possible?

We know it would be possible to use either case filtering[1] or multi-level
selection[2] to hide the sub-cases from the sub-case list, but if possible
we’d like to avoid this for the reason noted in Footnote 1 below.

Thanks,
Scott

[1] “You can alter a case property which filters the case out of the user’s
case list. This can be a useful approach when you want someone other than
the mobile user to have control over actually closing out a case. This
solution is only recommended if you have case sharing enabled and therefore
a way to actually close out the cases in a different application. Filtering
the cases without a way to close them would lead to an build up of
non-accessible cases on the phone over time.” (
https://help.commcarehq.org/display/commcarepublic/General+Workflow+Suggestions
)

[2]
https://confluence.dimagi.com/display/commcarepublic/Case+List+and+Case+Detail+View+Configuration#CaseListandCaseDetailViewConfiguration-Multi-LevelSelection

Hi Scott,

Thanks for reaching out to us and laying out the problem so nicely!

We do not currently support closing cases automatically. The automatic
closing subcases when the parent is closed is definitely something we plan
on supporting (though unfortunately not in time to help you now!)

If you let us know a little bit more about the workflow you envision for
when household members get registered, interviewed, and closed, we may be
able to suggest some good workarounds. One workaround based on what you
have written so far might be to close household members in the interview
form, so a household member is closed as soon as he/she is interviewed. You
could then create a separate module of houses that have no more members
registered, which the mobile user can occasionally check and close.

Thanks,
Amelia

··· On Mon, Feb 3, 2014 at 3:34 PM, Scott Lee wrote:

Hi all,

My colleagues and I are designing a household survey instrument with a
structure similar to Use Case 1 described in
https://confluence.dimagi.com/display/commcarepublic/Household+Survey+Workflows
i.e., household cases and household member sub-cases.

After interviewing all of the members within each household, we would like
the enumerator to close the HH case, so that it’s permanently removed from
the HH case list. Upon doing so, we would like all of the HH member
sub-cases for that HH case to automatically be closed as well. Is this
possible?

We know it would be possible to use either case filtering[1] or
multi-level selection[2] to hide the sub-cases from the sub-case list, but
if possible we’d like to avoid this for the reason noted in Footnote 1
below.

Thanks,
Scott

[1] “You can alter a case property which filters the case out of the
user’s case list. This can be a useful approach when you want someone other
than the mobile user to have control over actually closing out a case. This
solution is only recommended if you have case sharing enabled and therefore
a way to actually close out the cases in a different application. Filtering
the cases without a way to close them would lead to an build up of
non-accessible cases on the phone over time.” (
https://help.commcarehq.org/display/commcarepublic/General+Workflow+Suggestions
)

[2]
https://confluence.dimagi.com/display/commcarepublic/Case+List+and+Case+Detail+View+Configuration#CaseListandCaseDetailViewConfiguration-Multi-LevelSelection


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Amelia,

Thanks – that’s a great suggestion; we’ll give it a try.

Warmly,
Scott

··· On Tue, Feb 4, 2014 at 2:59 PM, Amelia Sagoff wrote:

Hi Scott,

Thanks for reaching out to us and laying out the problem so nicely!

We do not currently support closing cases automatically. The automatic
closing subcases when the parent is closed is definitely something we plan
on supporting (though unfortunately not in time to help you now!)

If you let us know a little bit more about the workflow you envision for
when household members get registered, interviewed, and closed, we may be
able to suggest some good workarounds. One workaround based on what you
have written so far might be to close household members in the interview
form, so a household member is closed as soon as he/she is interviewed. You
could then create a separate module of houses that have no more members
registered, which the mobile user can occasionally check and close.

Thanks,
Amelia

On Mon, Feb 3, 2014 at 3:34 PM, Scott Lee scott.s.lee@gmail.com wrote:

Hi all,

My colleagues and I are designing a household survey instrument with a
structure similar to Use Case 1 described in
https://confluence.dimagi.com/display/commcarepublic/Household+Survey+Workflows
i.e., household cases and household member sub-cases.

After interviewing all of the members within each household, we would
like the enumerator to close the HH case, so that it’s permanently removed
from the HH case list. Upon doing so, we would like all of the HH member
sub-cases for that HH case to automatically be closed as well. Is this
possible?

We know it would be possible to use either case filtering[1] or
multi-level selection[2] to hide the sub-cases from the sub-case list, but
if possible we’d like to avoid this for the reason noted in Footnote 1
below.

Thanks,
Scott

[1] “You can alter a case property which filters the case out of the
user’s case list. This can be a useful approach when you want someone other
than the mobile user to have control over actually closing out a case. This
solution is only recommended if you have case sharing enabled and therefore
a way to actually close out the cases in a different application. Filtering
the cases without a way to close them would lead to an build up of
non-accessible cases on the phone over time.” (
https://help.commcarehq.org/display/commcarepublic/General+Workflow+Suggestions
)

[2]
https://confluence.dimagi.com/display/commcarepublic/Case+List+and+Case+Detail+View+Configuration#CaseListandCaseDetailViewConfiguration-Multi-LevelSelection


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.