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) »
  • Support »
  • Using CiviCRM »
  • Using CiviCase (Moderator: Dave Greenberg) »
  • Case Status
Pages: [1]

Author Topic: Case Status  (Read 2108 times)

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Case Status
December 28, 2009, 01:17:03 pm
v3.0.3

If I want to create new cases status, there's no direct link to it (there probably should be), though I can access it through the main option lists page. When creating one through the option group list page, I run into a problem that the value field should be a number in order for the rest of case to work correctly. But the value field is manually entered, not autogenerated, so it requires the individual to maintain unique id numbers, which isn't a great idea.

I noticed it when we had some case statuses that had text in the value field and when we created or changed the status on a case, it didn't save the change. The issue could also be addressed by making the FK civicrm_option_value.id rather than .value (which would make more sense anyway).
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Case Status
December 28, 2009, 04:06:00 pm
Brian - We haven't (yet) explicitly exposed adding / changing Case Status values because there are a few hard-coded workflow rules which could break if statuses are modified.

Main examples:
- Open case work flow uses case status option_value.name = 'Open' to determine that it should set civicrm_case.start_date
- Change case status work flow uses option_value.name = 'Closed' to determine that is should set civicrm_case.end_date

Are there workflow implications for the statuses you are adding? Can you describe the req's a bit...
Protect your investment in CiviCRM by  becoming a Member!

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Re: Case Status
December 28, 2009, 04:25:53 pm
This client has created 10 additional statuses that basically fill in gaps between "open" and "close." I guess in ways they serve as passive activities against the case, e.g. Awaiting allocation, Awaiting client acceptance, Awaiting payment.

There are three statuses that are flagged as reserved (open, closed, urgent), though the title/label for each is editable, as is the value -- all of which you would want to lock down.

I suspect it would be useful on a broader basis to allow people to create their own sets of statuses, though I agree you'd want to make sure the hardcoded reserved ones are not editable at all.
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih

davej

  • Ask me questions
  • ****
  • Posts: 404
  • Karma: 21
Re: Case Status
February 01, 2010, 03:23:37 am
Related topic: Case status Closed is hard-coded, consider allowing multiple closed states

Dave

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviCase (Moderator: Dave Greenberg) »
  • Case Status

This forum was archived on 2017-11-26.