Dynamic Code Ticket Data Model
The Dynamic Code Ticket data model represents a record that documents the interactions and progress made on a single or group of dynamic code findings. It extends the Ticket data model.
The following table details the default attributes of the Dynamic Code Ticket data model:
Attribute Name | Attribute Type | Relationship Type | Required |
---|---|---|---|
ageInDays | Calculated (Number) | N/A | No |
assigned | Reference (User) | BELONGS_TO | No |
attachments | Attachments | N/A | No |
baseRiskScore | Calculated (Number) | N/A | No |
buid | Text | N/A | No |
categories | Text (Multivalued) | N/A | No |
comments | Comments | N/A | No |
complianceStatus | Calculated (Single Choice) | N/A | No |
connectorCategories | Text (Multivalued) | N/A | No |
connectorNames | Text (Multivalued) | N/A | No |
createdBy | Text | N/A | No |
dataIntegrationTitles | Text (Multivalued) | N/A | No |
dataModelName | Calculated (Text) | N/A | No |
dateClosed | Calculated (Date Time) | N/A | No |
dateCreated | Date Time | N/A | No |
daysToFix | Calculated (Number) | N/A | No |
delegates | Reference (User) | DELEGATED_TO | No |
description | Text Area | N/A | No |
displayName | Calculated (Text) | N/A | Yes |
dueDate | Calculated (Date Time) | N/A | No |
externalUids | Text | N/A | No |
findings | Reference (Dynamic code finding) | HAS | No |
flowState | Text | N/A | No |
lastUpdated | Date Time | N/A | No |
lifecycleInactiveDate | Date Time | N/A | No |
lifecyclePurgeDate | Date Time | N/A | No |
lifecycleStatus | Single Choice | N/A | No |
name | Text | N/A | No |
previousFindings | Reference (Dynamic code finding) | PREVIOUS_HAS | No |
progress | Number | N/A | No |
recommendation | Text | N/A | No |
remediationCampaigns | Reference (Remediation campaign) | HAS | No |
riskFactorOffset | Calculated (Number) | N/A | No |
riskFactors | Risk Factors | N/A | No |
riskRating | Calculated (Single Choice) | N/A | No |
riskScore | Calculated (Number) | N/A | No |
riskScoringModel | Risk Scoring Model | N/A | No |
sla | Calculated (Number) | N/A | No |
slaDefinition | SLA | N/A | No |
slaDefinitionName | Text | N/A | No |
slaLevel | Calculated (Text) | N/A | No |
sourceFirstFound | Date Time | N/A | No |
sourceLastFound | Date Time | N/A | No |
sourceStatus | Text | N/A | No |
sourceUids | Text (Multivalued) | N/A | No |
sources | Reference (Source model) | SOURCED_FROM | No |
sourcesIcons | Source data models icons | N/A | No |
sprint | Reference (Sprint Model) | BELONGS_TO | No |
status | Status | N/A | No |
statusCategory | Calculated (Single Choice) | N/A | No |
summary | Text | N/A | No |
uid | Text | N/A | Yes |
updatedBy | Text | N/A | No |
FOOTNOTES
- The attribute names are used in Brinqa Query Language (BQL) queries and Brinqa Condition Language (BCL) predicates.
- In the Type column, Calculated means that the value of the attribute is computed by executing a script. The text in the parentheses after Calculated denotes the type of the outcome. For additional information, see Calculated attributes.
- In the Type column, Reference means that two data models are related. The name in the parentheses after Reference indicates the other data model.
- The Relationship Type column only applies to the Category and Reference type attributes. You can use the relationship type keyword in BQL queries.