Proposal: changing case ownership to creator instead of last modifier

Hi Users,

An interesting problem came up recently in one of our projects and it’s
made us reconsider how we handle case ownership and whether we should
change it. Before going down that path I wanted to check with you all and
make sure the proposed change wouldn’t break any workflows that you’re
currently relying on.

This only affects apps that are not using case sharing. If your app uses
case sharing you can ignore this.

For apps that don’t use case sharing, the way a case’s owner is determined
is by the last modifier. This is typically fine, since only one user ever
modifies the case. However, we are seeing groups who are starting to want
to do manual edits/fixes to cases via CloudCare. This is problematic
because the case gets assigned to the user making the edit, and then gets
purged from the original worker’s phone who created it.

To fix this we are proposing changing ownership to creator instead of last
modifier, so that even if the cloudcare user edits the case it will still
be owned by the original mobile worker. We’ve thought through the change a
bit and I don’t believe it should break any designed workflows, but wanted
to confirm that the current last modifier behavior wasn’t something that
any project was relying on. If you wanted to change the ownership of a case
moving forward you would have to use “reassign cases” or case sharing.

Let us know if this is something we can move forward with!

thanks,
Cory

Although we have not yet implemented case sharing, we assumed the proposed
behaviour matched the current design.
(ie. case ownership does not change unless explicitly updated)

We’re planning to support multiple editors, and have case ownership remain
at the community (or CHW) level.

So, we think the proposed change makes sense and it will certainly will not
break anything for us.

Ray

··· On Mon, Dec 17, 2012 at 12:27 AM, Cory Zue wrote:

Hi Users,

An interesting problem came up recently in one of our projects and it’s
made us reconsider how we handle case ownership and whether we should
change it. Before going down that path I wanted to check with you all and
make sure the proposed change wouldn’t break any workflows that you’re
currently relying on.

This only affects apps that are not using case sharing. If your app uses
case sharing you can ignore this.

For apps that don’t use case sharing, the way a case’s owner is determined
is by the last modifier. This is typically fine, since only one user ever
modifies the case. However, we are seeing groups who are starting to want
to do manual edits/fixes to cases via CloudCare. This is problematic
because the case gets assigned to the user making the edit, and then gets
purged from the original worker’s phone who created it.

To fix this we are proposing changing ownership to creator instead of last
modifier, so that even if the cloudcare user edits the case it will still
be owned by the original mobile worker. We’ve thought through the change a
bit and I don’t believe it should break any designed workflows, but wanted
to confirm that the current last modifier behavior wasn’t something that
any project was relying on. If you wanted to change the ownership of a case
moving forward you would have to use “reassign cases” or case sharing.

Let us know if this is something we can move forward with!

thanks,
Cory


Ray Brunsting, CTO, Tula Foundation / www.tula.org