Set Entity relationships and reuse
An Entity stores one item’s name and content.
After this taskSource records match the criteria established for this task.
Starting conditions and inputs
Identify the organization and test record.
Values for this task
entry_url, organization_id, record_id
Command sequence
open "$entry_url" && snapshot -i
click "$entity_row" && snapshot -i
get text body
click "$relationship_field" && snapshot -i
click "$entity_option" && snapshot -i
reload && snapshot -i
get text bodyRef targets and expected results
| # | Command / ref | Target and verification |
|---|---|---|
| 1 | click $entity_row | Entity whose relationships will change |
| 2 | get text | Read source Entity ID and intended target ID. |
| 3 | click $relationship_field | Relationship field to edit |
| 4 | click $entity_option | Entity option matching the target ID |
| 5 | reload | Reload the same Entity record. |
| 6 | get text | Compare saved relationship source, target and direction. |
Check the result
Source records match the criteria established for this task.
Resuming after interruption
Reread the same source IDs and resume at the unfinished check.
Understand nodes and links
An Entity stores one item’s name and content. EntityEdge stores a parent-child link. One Entity can have several parents. Reuse it instead of copying the same fact for another placement.
Edit links and ordering
Choose a child under the parent’s content and set its order. Each link has its own order, so the same child can appear at different positions. Cycles that lead back to the same Entity are rejected.
Check website and AI reuse
Check both the rendered section and AI response when reusing an Entity. A graph link alone does not make every screen display it. Confirm the consumer’s reference settings and AI access scope.
Respect relationship limits
Distinguish content relationships from purchased entitlements. Adding a link does not activate a product or grant access. Removing a link is also different from deleting the Entity itself.