On Jul 15, 2008, at 1:38 PM, Hans Bakker wrote:
Hi Jacopo, this template could be a possibility, you want to create a
new entity for that because it should be stored in the database so the
user can modify it?
I think you could simply store it in as a 'special' CustRequest (and
related enti
Hi Jacopo, this template could be a possibility, you want to create a
new entity for that because it should be stored in the database so the
user can modify it?
however one single partyId would already be enough. We can then use the
partRelationship entity to expand that partyId(=department) into
On Jul 15, 2008, at 10:25 AM, Hans Bakker wrote:
Hi Jacopo,
thank you for your attention but where should i record that a certain
customerrequesttype is handled by which employees?
examples:
customer request type: "request for quote" => sales department.
customer request type: "request for
Hi Jacopo,
thank you for your attention but where should i record that a certain
customerrequesttype is handled by which employees?
examples:
customer request type: "request for quote" => sales department.
customer request type: "request for support" => support department.
etc
Hans
On
On Jul 14, 2008, at 9:53 PM, Hans Bakker wrote:
Yes surebut depending on the type of request I need to
automatically
add records to the CustRequestRole
Yes, and you could use a SECA for this.
at creation time i can add the appropriate roles however when i want
to
change the
Yes surebut depending on the type of request I need to automatically
add records to the CustRequestRole
at creation time i can add the appropriate roles however when i want to
change the allocation i have to go to all the places the request gets
created.
so isn't is better to add a
Hi Hans,
why don't you use the CustRequestRole entity and (if needed) define a
special role for this?
Jacopo
On Jul 14, 2008, at 5:14 AM, Hans Bakker wrote:
I have a customer who wants to allocate an incoming customer request
to
an employee group, to be processed.
Therefore i was thin
I have a customer who wants to allocate an incoming customer request to
an employee group, to be processed.
Therefore i was thinking about to add a partyId field to the
CustomerRequestType entity. This partyId can be a group which can relate
to employees over the partyRelationship entity.
anybo
