CiviCRM Community Forums (archive)

Hi,

I'm doing it the usual way, clicking here and there without reading the documentation, and trying to report as I walk the way.

Bottom line, RTFM, won't succeed without:
http://wiki.civicrm.org/confluence/display/CRMUPCOMING/CiviCase+Configuration

I suggest to have a default case type for the casual tester, with a simple "Meeting with follows up" (eg. 1 activity meeting, scheduled email in one week). or Anything that let the casual tester "play" with it and hopefully get hooked by the power of this.

I'm not convinced about the web interface to create cases, because it allows you to create a new case and uses it, but never warns you that you need to create xml files here and there, until you try to create a case (live from the sandbox):

unrecoverable error
    Sorry. A non-recoverable error has occurred.

    Configuration file could not be retrieved for case type = 'case2' (learn more...).

    Return to home page.

What's the point of having to create both an entry in the db AND xml files, and being forced to sync them (eg same name, CamelCase...) ?
Wouldn't it be better to either parse the xml files and generate the list of type of cases (shouldn't be that rocket science to generate a cached php config file) or alternatively have the xml configs within the db as blobs ? No matter what, have all the stuff regarding one config case in one place.

At least in the case type list, display some kind of information about if the case type is ready to be used because file /hardtoguess/location/Whatever.xml exists and contains <caseMattersOtherwiseWontWork> in the right place (or offer to generate an xml that contains the right minimal stuff).

Keep digging

X+

We had a very ambitious set of requirements for phase 1 - and the trade-off given time and budget was to NOT focus on UI for the CONFIGURATION process. A second reason for this was that we wanted to have some experience with the overall conceptual model / approach to using the component first, make adjustments based on user feedback over the next few months and then consider "baking the design" with configuration UI.

That said, we hope and intend that the configuration guide is complete and accurate such that a moderately technical person can implement things. I think your idea of having a very simple case type w/ it's configuration file included in the base install is a good idea and I'll try and get that in before the next beta.

Regarding your fatal error - the error is occuring in the createRelationships() function. Looks like you have a relationship type referenced in the configuration (xml) file that is not been inserted in the DB. If you're using the physicianhealthbc configuration files - you need to load their relationship types / activity types etc. from the .mysql file included in that sub-directory. (see http://wiki.civicrm.org/confluence/display/CRMUPCOMING/CiviCase+Configuration#CiviCaseConfiguration-CaseRoles(relationshiptypes) )