Introduction to records
You can define and structure event data across stories.
Records are captured from the storyboard. You use records to do things like:
Debug a story in a consistent way
Create a system of record
Store and report on data produced by Tines
Structure relevant story run and event data
View data visually through a chart
Reference a filtered view of data from a story using cURL to Tines
Create an “alert” to be further processed or referenced later when creating a case
Record elements
Records are made up of 8 main elements.
Some elements relate to the overall record whereas others are story-specific. When making changes to record-specific elements, it impacts all related stories as well.
Elements | Definition | Story-specific | Record-specific |
Records | The data capture from a specific story run; appears as an individual row on the records table | Yes | Yes |
Capture record | Records data from the story run to the records table | Yes | No |
Record type | The predefined fields across stories within a team | No | Yes |
Record columns | The individual predefined fields within the record type that appear as columns in the records table | No | Yes |
Record inputs | Determines what incoming event data gets captured in the record | Yes | No |
Records table | The summary of all collected records across stories | No | Yes |
Parent record | The source data capture for parent-child relationships. If a parent record is added to a story, all child records will also be added. | No | Yes |
Child record | The downstream records associated with a parent record. | No | Yes |