...
Upon consuming the myTC Account portal, the main landing page will look like the following:
...
The “My Services” functionality is a representation of the services which the user has been enrolled/has access to utilize:
...
The “My Requests” functionality is a representation of what a user is able to see regarding requests to which an association exists:
...
Each of the record in the My Requests grid (table in Figure 2.1‑3) contains information about the service request and related service. The MTOA framework retrieves the information about the service using the service id. It is mandatory for the service to define its base URL in the MTOA database before it goes live.
If the user clicks on the service request record, the MTOA framework will retrieve the information about the service including the base URL, and then, will redirect the user to the service landing page and will embed the service request id, service type, and language (eng or fra) in the querystring parameter of the service url.
Ex: for the iZEV service, the user is sent to the following URL if he clicks on the Service Request #1598
https://gartacc.tc.gc.ca/secure/ZEV-VZE?serviceRequestId=1598&serviceRequestType=zev-rr&_gc_lang=eng
The service is expected to handle two optional parameters: serviceRequestId of type int? and serviceRequestType of type string.
async Task<ActionResult> Index(int? serviceRequestId, string serviceRequestType)
It’s the responsibility of the service to determine which page will be opened based on the current service request status and current page indicator
The user may choose to open, submit or view a request by clicking on it. As an example of a submission, the user will be presented with the screen below as confirmation:
...