ASSIGNED_TO Party Data

Description

The ASSIGNED_TO relationship can be used to either:

1. Connect an Assignment node to a :Representation node; see Client Teams for more information, or
2. Connect a ClientExternalAssignment node to a :Party client node

Label

:ASSIGNED_TO

Valid nodes

From	Relationship	To	Cardinality
Assignment A node with the :Assignment label	ASSIGNED_TO	Representation A node with the :Representation label	1..1
ClientExternalAssignment A node with the :ClientExternalAssignment label	ASSIGNED_TO	Party A node of type :Party with an active HAS_ROLE relationship to a :Role { name: "Contact" } node	1..1

Properties

ASSIGNED_TO uses the standard relationship properties.

CREATE

When Used with Client Teams

Assignment relationships connect UTA agents (employee parties) to clients (client parties) via :Representation nodes. (See Client Teams for more details).

Multiple :Assignment nodes can connect with can connect with a single :Representation node. This captures the scenario where multiple agents work with the same client.

Only one :Assignment node per employee can connect with a :Representation node. If a single agent is assigned to multiple clients, then that agent is connected to multiple :Assignment nodes, each of which would be connected with a :Representation node.

When Used for External Team Roles

The ASSIGNED_TO relationship is used to represent a contact that works on behalf of a client. An example of this would be the personal manager of a client. When used in this context ASSIGNED_TO, a :ClientExternalAssignment node is connected to a speicifc party for their role in working with the client. Expanding on the example, if a client has two personal managers, each would have their own :ClientExternalAssignment node connected to them with their own :ASSIGNED_TO relationship.

UPDATE

Most updates to existing Representation and ClientExternalAssignment nodes should be REJECTED in favor of deactivation and create flow as described above, so as to preserve the history of changes. Instead, the existing relatipnship should be deactivated and a new active relationship with a new Representation or ClientExternalAssignment node should be created.

However, there are some situations where we will need to change information on an existing Representation or ClientExternalAssignment nodes, such as because of typographic error and where holding on to the original information would not be appropriate. In which case the API update operation should be limited to data management (DMO) personnel.

DELETE

For ASSIGNED_TO relationships, the DELETE verb corresponds to deactivating the relationship between the connected nodes. No physical deletes will happen.

Examples