Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Targeted Environments

...

  •  Service Artifacts

    • This release contains a new set of APIs for adding, updating, retrieving, and deleting Service Artifacts which are JSON-based form contents for Accelerated Forms. Service Artifacts are stored in the TC219_SERVICE_ARTIFACT table. Each Service Artifact has a service ID, alias name, version, and the content of the form in JSON.

  • Addressed an issue when an API call is made for a user and service enrolled in a organization where business system information does not exist in database. Fix api/v1/users/{id}/organizations for a given user and service

  • BUG 8825 - GET /api/v1/organizations - duplicate orgs returned when associated with multiple services

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

  • Bug #8733: GET /api/v1/services/{id}/organizations - orgs not sorted

  • Bug #8327: GET /servicerequests/{id}/invoices - invoices not sorted by Id

  • Bug #8723: GET /api/v1/users/{id}/organizations - orgs not sorted

  • Bug #8902: POST /api/v1/outage-notices - outage notices can be created when start time = end time

  • Bug #8705: GET /api/v1/servicerequests/statuses - items not sorted

  • Bug #8667: POST /api/v1/file-attachments - some edge cases return 500

  • Bug #8342: GET /api/v1/notification-template - templates not sorted

  • Bug #8734: GET /api/v1/services/{id}/activities - activities not sorted

  • Bug #8359: PUT /api/v1/artifacts/{id} - response should throw an error message when serviceRequestId is invalid

  • Bug #8344: GET /api/v1/account/enrollments - enrollments not sorted

  • Bug #8244: DELETE /outage-notices/{id} - a typo in error message/response body

  • Bug #8219: POST /api/v1/account/initiate-recovery - should check for existing mbuns

  • Bug #8703: GET /api/v1/organizations/{id}/users - users not sortedBug #9109: POST /api/v1/servicerequests/query - returns SRs when the filter containing invalid PlaceOfSupply and/or Status
    Bug #8099: GET /api/v1/servicerequests/{id}/user-assignments - should be sorted by UA Id ascendingly
    Bug #7986: GET /api/v1/account/enrollments returns 200 if using SVMMS key to retrieve RTMR user enrollments
    Bug #8933: QA Test- Date and Time Put updates are not reapplied to the Service Request.
    Bug #9091: CRSM SR successive status updates cause a collision and throws an error.
    Bug #9532: CRSM -A system user is returned after a status update and Get /api/v1/servicerequests/{{Id}}/status-history-ex
    Bug #9479: QA Test -Notices don't allow users to make edit changes after the start date/time, prior to the end date/time
    Bug #6310: Outage notice can be created or updated without Service ID using POST and PUT call
    Bug #9697: Portal - updating phone or email of external user with address coordinate causing 503
    Bug #9621: MTOA Portal - ACC/PROD - under "My Services" enrolled services should be grouped if IsLogicalGrouping property is set to false
    Bug #9903: QA Platform test - a Put after new CRSM 236 SR Post throws a 400 and db related errors
    Bug #9931: QA Platform test - GET /api/v1/servicerequests displays 236 service requests as ServiceStandardId "0"
    Bug #9713: GET /api/v1/servicerequests/status-history-ex - extended history of RTMR SR can be retrieved using SVMMS key
    Bug #9714: PUT /api/v1/servicerequests/status-history-ex - extended history of RTMR SR can be retrieved using SVMMS key
    Bug #10014: QA Platform test - Service 239 Put's can be added into a 263 Service Request
    Bug #10019: QA Platform Test - Get Service 230 status history for Activity Planned and and Updated returns nulls for ServiceCategoryCode and ServiceStandardId

MTOA NuGet packages Release Notes

Version ### (DATE0.15.24.164 (2021-06-09) (based on the dev branch

  • PBI 10063 “MTAPI - CRSM/MITRACK - Extend Service Request Queries”

  • PBI 9306 - BusinessSystem API related changes PBI (9568, 9309-  Activate / De-ativate Users 

  • PBI 10061: MTAPI - CRSM/MITRACK - Improve Support for Audit
    the actual back-end implement is still ongoing.  

Breaking change 
N/A

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

...