CiviCRM Community Forums (archive)

I have created a Webform so that an Organization Admin can create Relationships with Individuals with several optional roles, without having any CiviCRM Permission.

Can I create a Webform so that he could delete a Relationship (e.g. fix an error) ? How ?

What Coleman said - or maybe add a field to relationships for 'requires deleting' -  adding this on the webform - also let them set the Relationship to expired - then admin can do it as a 'once a week' task - rather than getting an Activity alert for each (which was how I thought Coleman might be implementing it)

JMM - how poor a substitute is letting them set an 'end date' to expire the relationship - and perhaps give them another field on the Relationship so they can check 'was an error', for example

hmm - nice 

Very clever indeed ! I will test that (and come back soon)

Concerning stackexchange (I just heard of), what is the interest, compared to this forum ?

JMM How did it work?

Evening,

I am currently looking at something for our website which would be a natural-ish progression from where JMM was heading.

We have member organisations with a local admin who manages their records. We would prefer to use webforms to allow them to update their "Main Contact" which for legal reasons we are required to have a single named individual in this role. What I was thinking of trying is expiring a relationship with a time of 'now' and starting a relationship with a time of 'now' on the same form.

My logic and understanding of Civi says that I would set the webform up viz:

Contact 1: Individual (the admin)
Existing Contact checked - so that they would need to be permissioned to make the changes

Contact 2: Organisation
Existing Contact checked  - so that we prevent spurious new organisations being created
Relationships enabled and specifies that contact 1 can view and edit the organisation

Contact 3: Individual (existing main contact)
Existing Contact checked
First Name and Last Name visible but disabled so it can not be edited (as the contact would remain)
Relationship end date set to now as per Coleman Watts' thoughts

Contact 4: Individual (new main contact)
They would already be associated with the organisation through a custom volunteer of relationship (we can call it as same principle) so we want the admin to be able to see al those that are volunteers at the organisation
Relationship set for main contact of and a start state set to now using the same steps as Coleman's thoughts again

Would that work?
My thought process is that unless someone goes in as a Civi Administrator and manually adds a second main contact, it would enforce that there is one because the default checkbox would be the only option.....

Afternoon Coleman and collective;

So I have been giving this a shot over the last 24 hours or so; it does not help that my works terminal is XP/IE8 either!
What I might do is use this thread as a bit of a blog or thought mapping process as it might help others in the future.

The first flaw I have come across is before we even look at the relationship management. The filters for the existing and new relationship holders allows the organisation admin to access our entire database of contacts where I would assume that checking the "Enforce Permissions" option would limit the selection.

As there would be one relationship holder I set this up as a static option, however I can only set the relationship automatically either as auto-from filters (which shows an incorrect result) or based on the relationship to the admin (where actually there is not one because the relationship is with the organisation)

So....

I switched the organisation to contact 1 and the admin to contact 2 does not seem to work because it hides all of the webform in place.

So I need to go back and find why the list of existing contacts is not being filtered by the relationship with the organisation....