Targeted Environments

Jan 29, 2021 - MTOA-INT, MTOA-TEST

Feb 4, 2021 - MTOA-ACC (Includes features from releases MTAPI Release Notes 1.3.0 , MTAPI Release Notes 1.4.0 , and MTAPI Release Notes 1.4.1 )

myTC Account documentation now available through TC confluence : myTC Account

Release Notes 1.5.1

• Addressed an issue with the api/v1/users/{id}/organizations api failure to retrieve organization by the user and service where business system information does not exist in database.

  • Fixed an issue with api/v1/users/{id}/organizations for a given user and service - API fails when there is no "business system type" associated for a given organization for a given user and a given service.

Release Notes 1.5.0

• PBI #8848 - Regulated entity enhancement - CRSM would like to use TC226_REGULATED_ENTITY_ID_TYPE.REGULATED_ENTITY_ID_TYPE_CD for regulated entities Post and Put.

• BUG #8881: CRSM setting time back one minute immediately after a status update throws an error.

• BUG #8717: Fix for issue where coordinates were removed when re-generating coordinates with id = 0

• BUG #8750: DbContext threading issue: Error when dbcontext is used by two threads at the same time

• BUG #7946: GET /organizations and GET /organizations/{id} not returning correct value in OrganizationType

• BUG # 8720: PUT /api/v1/organizations - should check DB and include the right ids in response body

• BUG #8743: GET /api/v1/permissions/{permissionId}/services/{serviceId}/users/{userId} - need to change responses for various permutations

• BUG #8741: DELETE /api/v1/notification-template/{templateName} - unexpected change in status code and response when providing a random name

• BUG #6863: POST /api/v1/service-settings can create RTMR settings using SVMMS API key/token

• BUG #7326: SVMMS api key & app jwt can access service settings and service preferences of RTMR

• Technical works

  • Security improvement to the service settings apis to ensure a service can only maintain its own service settings.

Service Regulated Entities (PBI #8848)

Updates January 28 – 2021

GET - /api/v1/services/{id}/regulated-entities

Due to a database update the service regulated entity id has been removed and will no longer be displayed in the response body.

Previously the id was displayed.

Now with the update the id is no longer displayed.

GET - /api/v1/regulated-entities?serviceRequestId={id}

Due to a database update the service regulated entity id has been removed and will no longer be displayed in the response body.

Previously the id was displayed.

Now with the update the id is no longer displayed.

POST - /api/v1/regulated-entities

Due to a database update the service regulated entity id has been removed it will no longer be used to create regulated entity values.

Previously the id which is a number was used.

Now the id used is the regulated entity type code which is now a string and no longer a number.

PUT - /api/v1/regulated-entities

Due to a database update the service regulated entity id has been removed it will no longer be used to create regulated entity values.

Previously the id which is a number was used.

Now the id used is the regulated entity type code which is now a string and no longer a number.

MTOA NuGet packages Release Notes

Version 0.15.20.131 (2021-01-29) (based on the dev branch) 

• Id property has been removed.

• Id has been changed from an int to a string.

Breaking change 
N/A

MTOA Database – Release Note for Version (v1.13.0)

Schema Structure Changes

Data Changes

No data change in this release.