Unexpected behaviour and bulk operations

Developers
1

For the GSID project Nick and I have spent quite a lot of time trying to
remove test data from the system and came across some unexpected results. I
thought I would enumerate them here to see if they are intended or not:

  1. Updating cases via the case importer changes the owner to the web
    user who did the import
  2. Archiving a form that created a case:
    1. If the case had no other changes made to it then the case is
      deleted (expected)
    2. If the case has had changes made to it (i.e. other forms submitted
      for that case) then the case is left in a strange state with the actions
      from the archived form removed (the initial 'create' and 'update' action)
      but the other form action intact.
  3. Archiving a form for a deleted case causes the case to become
    un-deleted
  • The workflow for this is as follows:
    • Re-assign case to another user
      • Delete that user
      • Archive the original form

In light of these issues I wondered if it wouldn't be a good idea to have a
'Bulk Operations' type of UI where an admin user could upload a list of
case or form ID's and perform some operation on them (like archive /
un-archive form, delete / un-delete case, re-assign case - The case
reassignment UI is fine if you are able to filter the correct cases but if
you can't then it isn't very useful).

Keen to hear what people think.
Simon

··· -- Simon Kelly Senior Engineer | Dimagi South Africa
2

One more thing that I noticed, in point 3, after a case is un-deleted by
archiving a form it doesn't appear in the case list even if the archived
form is restored ((possibly because it has a '-deletion_id' property?)

··· On Fri, Nov 1, 2013 at 2:19 PM, Simon Kelly wrote:

For the GSID project Nick and I have spent quite a lot of time trying to
remove test data from the system and came across some unexpected results. I
thought I would enumerate them here to see if they are intended or not:

  1. Updating cases via the case importer changes the owner to the web
    user who did the import
  2. Archiving a form that created a case:
    1. If the case had no other changes made to it then the case is
      deleted (expected)
    2. If the case has had changes made to it (i.e. other forms
      submitted for that case) then the case is left in a strange state with the
      actions from the archived form removed (the initial 'create' and 'update'
      action) but the other form action intact.
  3. Archiving a form for a deleted case causes the case to become
    un-deleted
  • The workflow for this is as follows:
    • Re-assign case to another user
      • Delete that user
      • Archive the original form

In light of these issues I wondered if it wouldn't be a good idea to have
a 'Bulk Operations' type of UI where an admin user could upload a list of
case or form ID's and perform some operation on them (like archive /
un-archive form, delete / un-delete case, re-assign case - The case
reassignment UI is fine if you are able to filter the correct cases but if
you can't then it isn't very useful).

Keen to hear what people think.
Simon

--
Simon Kelly
Senior Engineer | Dimagi South Africa

--
Simon Kelly
Senior Engineer | Dimagi South Africa

3
  1. Updating cases via the case importer changes the owner to the web
    user who did the import

owner_id or user_id? I would think only the latter, the former sounds
like a bug (please submit).

  1. Archiving a form that created a case:
    1. If the case had no other changes made to it then the case is
      deleted (expected)
    2. If the case has had changes made to it (i.e. other forms
      submitted for that case) then the case is left in a strange state with the
      actions from the archived form removed (the initial 'create' and 'update'
      action) but the other form action intact.

I believe this is the expected behavior. See:
Archive Forms - CommCare Public - CommCare Public

  1. Archiving a form for a deleted case causes the case to become
    un-deleted
  • The workflow for this is as follows:
    • Re-assign case to another user
      • Delete that user
      • Archive the original form

This seems like a bug (please submit).

In light of these issues I wondered if it wouldn't be a good idea to have
a 'Bulk Operations' type of UI where an admin user could upload a list of
case or form ID's and perform some operation on them (like archive /
un-archive form, delete / un-delete case, re-assign case - The case
reassignment UI is fine if you are able to filter the correct cases but if
you can't then it isn't very useful).

Definitely sounds useful, though would not make a priority at the moment.

··· > >> Keen to hear what people think. >> Simon >> >> -- >> Simon Kelly >> Senior Engineer | Dimagi South Africa >> > > > > -- > Simon Kelly > Senior Engineer | Dimagi South Africa > > -- > > --- > You received this message because you are subscribed to the Google Groups > "CommCare Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to commcare-developers+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. >