...
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:
...
When “Account Settings” is selected, the user is presented with the following page:
...
This functionality can be used to, if applicable, send email notifications to a user from a particular service base on actions within MTOA using the email notification API.
A user is notified about the existing association of the email address with myTC Account and not with a service or program.
Furthermore; the user is also advised to contact a program representative, in order to update an email address associated to a specific subscribed service(s).
Preference Settings vs Service Settings
It must be noted that there is a subtle, yet significant difference between Preference and Service Settings and this can be summarized as follows:
Preferences are settings that can be modified at any time by a regular user i.e. “EnableServiceFeatureXYZ”.
Service settings are internal to the application programming, seldom changed and not designed for user interaction i.e. “GCKeyLogoutUrl”.
1.1.1 myTC Account Recovery
The myTC Account Recovery allows a user who has forgotten their GCKey account credentials, to create a new GCKey account and bind their previous myTC Account to the newly created one.
Steps:
A user creates a new GCKey Account (
https://gart.tc.gc.ca/secure/mtoa-mctcl )
2. Once in the myTC Account “User Registration” page click the “Reconnect your myTC Account to new GC Key” link
...
3. Enter the email address you used to create your previous “myTC Account” user account and click “Send me the recovery link”
...
Once you receive the "myTC Account" Recovery email, click on the link it provides.
Your existing TC Account should now be bound to the new user.
1.1 myTC Account MTAPI
The myTC Account platform provides data services available (exposed) through Web APIs to handle all the database related transactions. The data services are distributed across several areas including:
Ø Accounts;
Ø Application;
Ø Artifacts;
Ø EmailNotification;
Ø Organization;
Ø ServiceRequests;
Ø Services;
Ø Users.
1.2 myTC Account Database
1.2.1 Environments:
Ø Development: MTOAD.WORLD;
Ø Testing: PREACC_CA.WORLD;
Ø Acceptance: MTOAA.WORLD;
Ø Production: MTOAP.WORLD.
1.2.2 Accounts:
Ø Owner: MTOA;
Ø Internal User : MTOA_USER;
Ø MTOA API : MTOA_API;
Ø External Protected ‘A’ : MTOA_EXTA;
Ø External Protected ‘B’ : MTOA_EXTB (not currently used).
1.2.3 Connection to Legacy Application Databases
As per DMI/DBA recommendation, it is advised to create a myTC Account in the legacy database to allow myTC Account interactions, instead of using the generic AAAA_user account.
For example, for the myTC Account ACP/AQPE Monitor Report service which interacts with the FTAE legacy database/application, a MTOA_FTAE account was created to differentiate the access to FTAE between a FTAE application USER and a myTC Account user.