Testing A Table
This is a table:
Change Category | CD Disruption | Enablement | Comments | |
|---|---|---|---|---|
Minor | None/Slight | Automatically enabled with no opt-out. | Notice provided in Preview Release Notes with details in Release Notes with GA. | |
Minor | Moderate | Automatically enabled with no opt-out. | Notice provided 60 days in advance. | |
Major | Large/Severe | Opportunity to opt-in for 4 months before automatically enabled with no opt-out. | Notice provided 60 days in advance with 4-month adoption period. | |
Change | Hypothetical Example | Impact | Assumptions | CD Disruption |
Add a new Brightspace Data Set | Intelligent Agents BDS added. | New data set appears in UI and API. | Integrations are designed to ignore new data sets listed in the Data Sets API Route. | Slight |
Add a column to the composite primary key | Primary Key of Quiz Questions BDS updated to include additional columns: one new and one existing. | The combination of columns that functions as Primary Key changes to include one or more additional columns. | Integrations may need to be updated to use new composite Primary Key, but integrations will continue to function using previous composite Primary Key. | Slight |
Remove a column from the composite primary key, but column remains in data set | Primary Key of Quiz Questions BDS updated to no longer require a column, but removed column still exists. | The combination of columns that functions as Primary Key no longer requires one or more columns. | Integrations continue to function using previous composite Primary Key, but integrations may find more value using the new composite Primary Key. | Slight |
Change whether a column can be NULL | Updated a column that previously could be null to not nullable. | No longer need to expect NULL values when processing. | Integrations continue to function when something that could be NULL in the past now has a value for every row. However, there may need to be an update to expect a NULL value where there couldn’t be one before. | Slight |
Append a new column | LastModifiedDate column added to the end of the Grade Objects BDS. | New column appears in data set after existing data elements. | Integrations are designed to ignore new data elements but proceed with other data elements. See a code example that demonstrates one approach to implementing this behavior. | Moderate |
Add new data in the form of additional rows | Soft deletes added to existing BDS. | Additional rows appear in data set. Depending on use, they may need to be filtered out. | Integrations may need to be updated to handle the new rows or filter them out. | Moderate |
Change whether a column can be NULL | Updated a column that previously could not be null to nullable. | Expect NULL values when processing the data set. | Integrations continue to function when something that could be NULL in the past now has a value for every row. However, there may need to be an update to expect a NULL value where there couldn’t be one before. | Moderate |
Change data type of a column | Changed a column's data type from bit to int. | Previous data type is no longer valid. | Integrations may need to be updated to handle the new data type. | Moderate |
Change | Hypothetical Example | Impact | Assumptions | |
Remove a column | Removed ObjectLookupId2 column from Calendar Events BDS. | Column no longer exists in BDS. In cases where the column was part of the composite Primary Key, the combination of columns that functions as composite Primary Key no longer requires the column being removed. | Integrations must be updated to no longer expect the column being removed in the BDS. | |
Rename a column | Renamed ObjectId to QuizId. | The column name previously used no longer exists, with a new name taking its place. | Integrations must be updated to update the name of the existing column. | |
Change character(s) in column name to upper or lower case | Changed HistoryID to HistoryId. | The column name previously used no longer exists, with a new name taking its place. | Integrations must be updated to update the name of the existing column (automatic column detection is case sensitive). | |
Remove a data set | Awards BDS removed. | Data set is no longer available for download. Some data set removals may occur without a major version change. | Integrations must be updated to remove dependencies on the removed data set. |
Comments
-
Change Category
CD Disruption
Enablement
Comments
Minor
None/Slight
Automatically enabled with no opt-out.
Notice provided in Preview Release Notes with details in Release Notes with GA.
Minor
Moderate
Automatically enabled with no opt-out.
Notice provided 60 days in advance.
Major
Large/Severe
Opportunity to opt-in for 4 months before automatically enabled with no opt-out.
Notice provided 60 days in advance with 4-month adoption period.
Change
Hypothetical Example
Impact
Assumptions
CD Disruption
Add a new Brightspace Data Set
Intelligent Agents BDS added.
New data set appears in UI and API.
Integrations are designed to ignore new data sets listed in the Data Sets API Route.
Slight
Add a column to the composite primary key
Primary Key of Quiz Questions BDS updated to include additional columns: one new and one existing.
The combination of columns that functions as Primary Key changes to include one or more additional columns.
Integrations may need to be updated to use new composite Primary Key, but integrations will continue to function using previous composite Primary Key.
Slight
Remove a column from the composite primary key, but column remains in data set
Primary Key of Quiz Questions BDS updated to no longer require a column, but removed column still exists.
The combination of columns that functions as Primary Key no longer requires one or more columns.
Integrations continue to function using previous composite Primary Key, but integrations may find more value using the new composite Primary Key.
Slight
Change whether a column can be NULL
Updated a column that previously could be null to not nullable.
No longer need to expect NULL values when processing.
Integrations continue to function when something that could be NULL in the past now has a value for every row. However, there may need to be an update to expect a NULL value where there couldn’t be one before.
Slight
Append a new column
LastModifiedDate column added to the end of the Grade Objects BDS.
New column appears in data set after existing data elements.
Integrations are designed to ignore new data elements but proceed with other data elements. See a code example that demonstrates one approach to implementing this behavior.
Moderate
Add new data in the form of additional rows
Soft deletes added to existing BDS.
Additional rows appear in data set. Depending on use, they may need to be filtered out.
Integrations may need to be updated to handle the new rows or filter them out.
Moderate
Change whether a column can be NULL
Updated a column that previously could not be null to nullable.
Expect NULL values when processing the data set.
Integrations continue to function when something that could be NULL in the past now has a value for every row. However, there may need to be an update to expect a NULL value where there couldn’t be one before.
Moderate
Change data type of a column
Changed a column's data type from bit to int.
Previous data type is no longer valid.
Integrations may need to be updated to handle the new data type.
Moderate
Change
Hypothetical Example
Impact
Assumptions
Remove a column
Removed ObjectLookupId2 column from Calendar Events BDS.
Column no longer exists in BDS. In cases where the column was part of the composite Primary Key, the combination of columns that functions as composite Primary Key no longer requires the column being removed.
Integrations must be updated to no longer expect the column being removed in the BDS.
Rename a column
Renamed ObjectId to QuizId.
The column name previously used no longer exists, with a new name taking its place.
Integrations must be updated to update the name of the existing column.
Change character(s) in column name to upper or lower case
Changed HistoryID to HistoryId.
The column name previously used no longer exists, with a new name taking its place.
Integrations must be updated to update the name of the existing column (automatic column detection is case sensitive).
Remove a data set
Awards BDS removed.
Data set is no longer available for download. Some data set removals may occur without a major version change.
Integrations must be updated to remove dependencies on the removed data set.
Testing table.
-
Change
Hypothetical Example
Impact
Assumptions