CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion (Moderator: Donald Lobo) »
  • CiviCase: could case activities be prohibited to use 'move' or 'copy' functions?
Pages: [1]

Author Topic: CiviCase: could case activities be prohibited to use 'move' or 'copy' functions?  (Read 566 times)

nickholden

  • I post occasionally
  • **
  • Posts: 111
  • Karma: 1
  • CiviCRM version: 4.4.1
  • CMS version: Drupal 7
  • MySQL version: 5.5.32
  • PHP version: 5.4
CiviCase: could case activities be prohibited to use 'move' or 'copy' functions?
October 17, 2012, 10:04:29 am
I'm working on our use of CiviCase to represent research studies with each study being represented by a 'Case Type' and each recruitment being a 'Case'. The model works remarkably well, and so far, it has require configuration rather than customisation of the code. A series of API calls and some word replacements and the object model pretty much fits.

However, for each activity within a case there are 2 links : "Move To Case" and "Copy To Case". While I can see how these would be used in the Case context, these present us with problems, as an activity within a research study should not be movable or copyable. It makes no sense in the study context.

Rather than create a webform to manage the Case/Study enrolment activity data entry, I wondered about adding a configuration option within the Case configuration xml which allowed for these links to be turned on or off, with on being default to preserve current behaviour. I read a thread in the forums where an additional functionality to share activity with another case was added, and it seemed to me that a similar approach could work for us - an xml flag for <AllowActivitiesToMove> and one for <AllowActivitiesToCopy> with checks in the template should do the trick.

Does that sound like something worth doing? I realise ours is a pretty specific use case, but I can imagine other places where confidentiality in case processes might make copying or moving case activities an undesirable feature.

Nick

Erik Hommel

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1773
  • Karma: 59
    • EE-atWork
  • CiviCRM version: all sorts
  • CMS version: Drupal
  • MySQL version: Ubuntu's latest LTS version
  • PHP version: Ubuntu's latest LTS version
Re: CiviCase: could case activities be prohibited to use 'move' or 'copy' functions?
October 18, 2012, 12:53:23 am
Hi Nick,
I am sure that could be a possibility and a good solution. I can not judge whether it is 'worth' doing, one of our customers uses CiviCase quite heavily and is quite happy with the current situation. Although your solution would not have a functional impact as they would simply switch the options on, they would not have a need for the mod and I would guess they would not pay for a MIH doing this either?
Consultant/project manager at EEatWork and CiviCooP (http://www.civicoop.org/)

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion (Moderator: Donald Lobo) »
  • CiviCase: could case activities be prohibited to use 'move' or 'copy' functions?

This forum was archived on 2017-11-26.