CiviCRM Community Forums (archive)

A good example is a membership renewal activity - the membership_id will be stored in that field. When you look at the activity list & go to view the activity I think it takes you to the membership. The activity_type_id determines what sort of record will be stored in the record_type_id & I believe is just coded into the codebase ad hoc - as far as I know there is no list / metadata for what activities use record_type_id.

I believe that for your own custom activity types you could use this field to point to the record you see fit

If you are thinking about submitting it as a patch it's the files in the xml dir (in the git checkout) that would have the comments added. Note it's custom activity types not custom fields we are talking about here

More like here

https://github.com/civicrm/civicrm-core/blob/master/xml/schema/Activity/Activity.xml#L53

That then winds up as comments on the sql table field & I think getfields returns it too

I'm not sure this is entirely right.

The xml Eileen linked to gives an option group for this field:    <optionGroupName>activity_contacts</optionGroupName>

And looking at that option group in my system the choices are... Activity Assignees, Activity Sources and Activity Targets. That seems far more specific than the comments in this thread, and suggests that the field should be used to indicate the type of relationship that exists between the activity and the contact being linked. Without that specific functionality for this field, the ability to pinpoint the target of an activity as distinct from the person who created it in the system is lost, no?

The new table doesn't just replace civicrm_activity_target. It replaces civicrm_activity_assignment as well.

Rich Lott (artful robot) has written about the implications on his blog:

http://artfulrobot.com/blog/assignment-activities-just-changed-civicrm

Although it's not an ENUM, it could be. As for wording, how about:

<comment>The record type id for this row. A value of '1' indicates the contact has been assigned the activity ("Activity Assignee"), a value of '2' indicates the contact created the activity ("Activity Source") and a value of '3' indicates the contact is the focus of the activity ("Activity Target").</comment>

Is that too verbose? I tend to be verbose.

I suppose other values could be used, which would extend the behaviour of activities such that you might have additional 'activity roles' not currently envisaged. Maybe the comment should explicitly link to the option group 'activity_contacts' in case people want to define additional record types?

Final point, should the comment reference the legacy tables which have been replaced, just in case someone is looking for them? That would be, erm, thorough.

Just re-reading & I realise I mis-read in the first place - I misread you as referring to civicrm_activity.source_record_id rather than civicrm_activity_contact.record_type_id - sorry to have responded with misleading information - I think I'm just too used to people asking about source_record_id & jumpted the gun.

No - I was definitely in La-la land on that one