Thoughts on adding optional attribute roleTypeId to createPerson service

[Vikas Mayur-2]

How about adding an optional attribute roleTypeId to createPerson service to
call createPartyRole on a service eca similar to what is done in for
createPartyContactMech to create the purpose.
This is often used in events and this way there will be no need to
explicitly call createPartyRole service.

Thoughts please.

Vikas

[Anil Patel-3]

+1

Regards
Anil
On May 23, 2008, at 11:00 AM, Vikas Mayur wrote:

> How about adding an optional attribute roleTypeId to createPerson  
> service to
> call createPartyRole on a service eca similar to what is done in for
> createPartyContactMech to create the purpose.
> This is often used in events and this way there will be no need to
> explicitly call createPartyRole service.
>
> Thoughts please.
>
> Vikas

[Jacques Le Roux]

Yes sounds like a good idea and I suppose if roleTypeId is empty the ECA is skipped (did not look at code)

Jacques

From: "Vikas Mayur" <[hidden email]>

> How about adding an optional attribute roleTypeId to createPerson service to
> call createPartyRole on a service eca similar to what is done in for
> createPartyContactMech to create the purpose.
> This is often used in events and this way there will be no need to
> explicitly call createPartyRole service.
>
> Thoughts please.
>
> Vikas
>

[Vikas Mayur-2]

Jacques, you are right indeed.

I think this can also be done for couple of other services:
1) createPersonAndUserLogin
2) createPartyGroup

Vikas

On Sat, May 24, 2008 at 3:02 AM, Jacques Le Roux <
[hidden email]> wrote:

> Yes sounds like a good idea and I suppose if roleTypeId is empty the ECA is
> skipped (did not look at code)
>
> Jacques
>
> From: "Vikas Mayur" <[hidden email]>
>
>  How about adding an optional attribute roleTypeId to createPerson service
>> to
>> call createPartyRole on a service eca similar to what is done in for
>> createPartyContactMech to create the purpose.
>> This is often used in events and this way there will be no need to
>> explicitly call createPartyRole service.
>>
>> Thoughts please.
>>
>> Vikas
>>
>>

[Jacques Le Roux]

Yes the pattern sounds fine to me

Jacques

From: "Vikas Mayur" <[hidden email]>

> Jacques, you are right indeed.
>
> I think this can also be done for couple of other services:
> 1) createPersonAndUserLogin
> 2) createPartyGroup
>
> Vikas
>
> On Sat, May 24, 2008 at 3:02 AM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Yes sounds like a good idea and I suppose if roleTypeId is empty the ECA is
>> skipped (did not look at code)
>>
>> Jacques
>>
>> From: "Vikas Mayur" <[hidden email]>
>>
>>  How about adding an optional attribute roleTypeId to createPerson service
>>> to
>>> call createPartyRole on a service eca similar to what is done in for
>>> createPartyContactMech to create the purpose.
>>> This is often used in events and this way there will be no need to
>>> explicitly call createPartyRole service.
>>>
>>> Thoughts please.
>>>
>>> Vikas
>>>
>>>
>