HAS_ASSIGNMENT Party Data
Description
The HAS_ASSIGNMENT relationship connects Employee parties to a specific Assignment node.
See Client Teams for more information.
Label
:HAS_ASSIGNMENT
Valid nodes
| From | Relationship | To | Cardinality |
|---|---|---|---|
| Employee A node of type :Party with a HAS_ROLE relationship to a Role { name: "Employee"} node | HAS_ASSIGNMENT | Assignment A node with the :Assignment label | 0..n |
Properties
HAS_ASSIGNMENT uses the standard relationship properties.
CREATE
An agent can have multiple assignments roles. For example, they can serve as a Responsible Agent for one client while also serving as part of an Agent Team for another client.
An agent can be a Responsible Agent for multiple clients, however this would be represented as two distinct :Assignment nodes connected via their own ASSIGNED_TO relationship with a :Representation node.
UPDATE
Most updates to existing :Assignment 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 :Assignment node should be created.
However, there are some situations where we will need to change information on an existing :Assignment node, such as because of typographic error and where holding on to the original information would not be appropriate. In which case, only the teamRole property can be updated and the API update operation should be limited to data management (DMO) personnel.
DELETE
For HAS_ASSIGNMENT relationships, the DELETE verb corresponds to deactivating the relationship between the connected nodes. No physical deletes will happen.