Note: Do not confuse “scoping” as we use the term in Broadsign Administrator, with “scoping” as we use the term in Broadsign Open.
In Broadsign Administrator, “scoping” describes the limiting of what users can see (see Network Operations – Scoping).
In Broadsign Open, “scoping” describes the narrowing of results of certain “list” operations.
|Parameter||Description||Type||Required (R) or Optional (O)|
|domain_id||The unique ID# of your domain.||bstypes:ResourceId||R|
|parent_container_ids||The unique ID# or #s of folders on your domain, used to scope your results.||bstypes:ResourceId||R|
|Value||Description||Type||Required (R) or Optional (O)|
|id||The unique ID# of the incident.||bstypes:ResourceId||R|
|resource_id||The unique ID# of the resource (player or edge server) related to this incident.||bstypes:ResourceId||R|
|status_code||The status code for this incident:
|type_code||The type code for this incident:
|occurred_on||The date time at which this incident occurred.||bstypes:SimpleDateTime||R|
|reported_on||The date time at which this incident was reported.||bstypes:SimpleDateTime||R|
|resolved_on||The date time at which this incident was resolved.||bstypes:SimpleDateTime||R|
|problem_description||The description of the problem related to this incident.||string||R|
|resolved_description||The description of the resolution related to this incident.||string||R|
|target_resource_id||The unique ID# of the resource targeted by this incident.||bstypes:ResourceId||R|
|last_status_code_change_utc||The last date time in UTC at which the status code for this incident was changed.||bstypes:SimpleDateTime||R|
|escalation_status||The escalation status for this incident:
|domain_id||The unique ID# of the domain.||bstypes:ResourceId||R|
|warning_escalation_tm_utc||The last date time in UTC at which this incident was escalated to warning.||bstypes:SimpleDateTime||R|
|critical_escalation_tm_utc||The last date time in UTC at which this incident was escalated to critical.||bstypes:SimpleDateTime||R|