Targeted Environments

29 Sep 2021 - MTOA-INT, KANGA-INT, MTOA-TEST, KANGA-TEST (Version 2.0.0.368)

06 Oct 2021 - MTOA-INT, KANGA-INT, MTOA-TEST, KANGA-TEST, MTOA-UAT, and KANGA-UAT (Version 2.0.2.372)

07 Oct 2021 - MTOA-ACC and KANGA-ACC (Version 2.0.2.372)

SMGS# ticket:
PROD Release:

myTC Account documentation now available through TC confluence : https://tcmarin.atlassian.net/wiki/spaces/MA

Release Notes 2.0.0.368

The MAPI release includes changes to the service artifacts and some major database structure changes. The service artifacts end-points were renamed to maintain consistency with the existing MTAPI end-points.

• PBI #10876 - MTAPI - Service Request Assignments - Support for Multiple Users

• PBI #10885 - MTAPI - Service Request Assignments - Ability to remove assigned Users from SR by providing list of UserID

• PBI #11548 - Investigate and address missing logs when APIs run into exception

• PBI #11652 - Manage Internal and External Users - Support for Admin Console to make use of the AC060 and AC061 application tables.

• PBI #10878 - MTAPI - Service Request - Ability to retrieve collection of SRs given a list of SRs IDs

• PBI #10883 - MTAPI - Service Request History - Ability to include the SR History with the retrieved SRs

  • Retrieve a Service Request List that includes Status History using the "POST /api/v1/servicerequests/query" endpoint

  • Document SR history in SR List

• PBI #11293 - MTOA Portal - Enhance Account Recovery Implementation - GC Key Login Page

• Hide "GET /api/v1/services/base-urls" api from swagger page

• New api GET /api/v1/services/{id}/service-standards

  • This endpoint will be used to retrieve both ServiceStandardId and ServiceCategoryCode  along with the Service Request Status information.

• New api to support multiple user assignments for a service request

  • POST /api/v1/servicerequests/multiple-user-assignments

    • Assign multiple user to a given Service Request

  • DELETE /api/v1/servicerequests/{id}/multiple-user-assignments

    • Un-assign multiple users from a Service Request

• New api end points for the service artifacts

  • POST /api/v1/service-artifacts

    • Creates a new service artifact

  • PUT /api/v1/service-artifacts

    • Updates a service artifact

  • DELETE /api/v1/service-artifacts/{​​​​​id}​​​​​

    • Deletes a service artifact using its ID

  • GET /api/v1/service-artifacts/{​​​​​id}​​​

    • Gets the JSON of an existing service artifact using it ID

  • GET /api/v1/service-artifacts/latest

    • Get the latest JSON of a service using an alias (optionally filter by service ID and version)

  • GET /api/v1/service-artifacts/{​​​​​id}​​​​​/info

    • Get a service artifact's information using its ID

  • GET /api/v1/service-artifacts/info

    • Get a service artifact's information using a service ID (optionally filtered by alias and version)

  • GET /api/v1/service-artifacts/info-by-name

    • Get a service artifact's information using the name (alias) of the artifact (optionally filtered by service Id and version 

• BUG #11910 - AF - GET /api/v1/service-artifact/latest with valid artifact Alias and key returns a 401

• BUG #11683 - MTAPI - GET /api/v1/country-subdivisions - missing data

• Bug #12075 - MTAPI - GET /api/v1/service-artifacts/info - response data not sorted by id

• Bug #12079 - MTAPI - GET /api/v1/service-artifacts/{id} - mtapistatus is -1 for successful requests

• Bug #12080 - MTAPI - GET /api/v1/service-artifacts/latest - mtapistatus is -1 for successful requests

• BUG #11906 - AF - GET /api/v1/service-artifact/artifacts/info filtered with ServiceCode and version returns no Artifacts

• BUG #11903 - AF- serviceId's not updated with PUT /api/v1/service-artifact

• BUG #11494 - QA- ACC Portal My Service cards public services should not display contact services when there are no services

• BUG #11683 - MTAPI - GET /api/v1/country-subdivisions - missing data

• BUG #11319 - MTAPI - GET /api/v1/artifacts/{​​​​​id}​​​​​/info - mtapistatus header should return 4041009,604008 for invalid artifactId

• BUG #11963 - MTAPI - GET /api/v1/file-attachments/{​​​​​id}​​​​​ - missing error message

• BUG #9632 - QA ACC Portal - In progress PFTR reports are not opened after selecting it in the My Services listing Adding service artifact implementation for GetByName to the api client to consume the v1/service-artifact/artifacts/info-by-name api

• BUG #11017 - MTAPI - The ServiceRequest API Page and Page size parameters should have default value

• Implemented the same standard for the page and pagesize for the GET /api/v1/app/servicerequests and GET /api/v1/servicerequests apis

• BUG #11319 - MTAPI - GET /api/v1/artifacts/{​​​​​id}​​​​​/info - mtapistatus header should return 4041009,604008 for invalid artifactId

• Adding deleted_date_dte null check when retrieving service artifacts.

• Added support for the new UAT environment

• TASK #11449 Fixed regenerated EDMX and prerequisite changes to phase 1 Admin console changes.

• TASK #11166 - Add Support for a RevisedDate for UpdateServiceRequestStatus 

Release Notes 2.0.1.370

• BUG #11683 - MTAPI - GET /api/v1/country-subdivisions - missing data & filtering negative codes

• Release Notes 2.0.2.372

  • Added UAT support

  • BUG #12198 - MTAPI - POST /api/v1/notification-template - unable to create new email templates

  • BUG #12198 - MTAPI - GET /api/v1/whoami - unable to get valid response with service keys/tokens

MTOA NuGet packages Draft Release Notes

Version # 1.0.0.179 (2021-09-29)

• Business Layer changes

  • AddressManager - Enhancement to the GetAllSubdivisions method

  • ApplicationCatalog - Enhancement to the GetByApiKey method

  • ServiceManager - New method GetServiceStandards to get service standards by service id

  • ServiceRequestManager - new methods to add/remove multiple user assignments

    • AddMultipleUserAssignments

    • RemoveMultipleUserAssignments

• Domain objects changes

  • New properties added to ApplicationDTO

    • ApplicationCode

    • EnglishName

    • FrenchName

    • Name property became obsolete

  • New dto MultipleServiceRequestUserAssignmentCreationDto to support multiple user assignments

  • Added StatusHistory property to the ServiceRequestDTO

  • New properties added to the ServiceRequestQueryDTO

    • ServiceRequests

    • IncludeStatusHistory

  • New properties added to the Application business object

    • ApplicationCode

    • EnglishName

    • FrenchName

    • Name property became obsolete

  • New DateRange business object

  • Updated the MtapiStatusCode to include new error codes

  • New OrderByType business object

  • Added ApplicationCode property to the ServiceInfo business object

  • Added StatusHistoryproperty to the ServiceRequest business object

  • Added new properties to the ServiceRequestQuery business object

    • ServiceRequests

    • Services

    • IncludeStatusHistory

  • New ServiceStandard business object

• Data Access Layer changes

  • Enhancements to the data repositories

  • Changes to database entities

Breaking change 
N/A

MTOA Database – Release Note for Version (v2.0.0)

Schema Structure Changes

Data Changes