Card planned relations
A planned relation between the dates of two cards: the successor starts after the predecessor finishes. Both cards need planned_start and planned_end, otherwise the package is rejected. gap with gap_type adds a gap between the finish of the predecessor and the start of the successor. Dependencies must not form a cycle, and a chain of more than 255 links is rejected.
A record of this entity needs records of other entities in the package: Cards.
Files in the package
List every file of this entity in resource_files of the manifest, with "resource": "card_planned_relations". An entity can have any number of files. See Bundle format.
[
{
"resource": "card_planned_relations",
"path": "resources/card_planned_relations.json"
}
]Fields
| Field | Type | Required | Description |
|---|---|---|---|
external_id | string (ExternalId) | Yes | Your own identifier of the record, for example k-mrr, unique within the resource across all of its files and case sensitive. Other records refer to this one by it.Constraints: 1–512 characters. |
predecessor_card_ref | Ref<cards> refers to Cards | Yes | The card that comes first. It must have planned_start and planned_end. Give the external_id of a cards record. |
successor_card_ref | Ref<cards> refers to Cards | Yes | The card that depends on the predecessor. It must have planned_start and planned_end. Rule: Differs from predecessor_card_ref. |
gap | integer? | No | Gap between the finish of the predecessor and the start of the successor, in whole units of gap_type; use it with gap_type.Rule: Only together with gap_type. |
gap_type | enum? | No | Unit of gap: hours or days. Use it with gap.Constraints: one of hours, days. Rule: Only together with gap. |
References
Show on the entity map
Example
A record of this entity:
{
"external_id": "pd-cohorts-ltv",
"predecessor_card_ref": "k-cohorts",
"successor_card_ref": "k-ltv",
"gap": 3,
"gap_type": "days"
}Rules
- gap and gap_type are given together.
- Both cards must have planned_start and planned_end in cards; otherwise the error is relation_invalid on the field of the card without a planned period.
- The combination of predecessor_card_ref, successor_card_ref must be unique.
- predecessor_card_ref and successor_card_ref must differ.
- The relations from predecessor_card_ref to successor_card_ref contain no cycle and no chain longer than 255 relations.
Related entities
Card children, Cards
JSON Schema
card_planned_relations.json
