Overview
AAIR backlog item board
https://dev.azure.com/transport-canada/DSD-CIVAV Support/_boards/board/t/AAIR/Backlog items
Related documents regarding AAIR/5008
Backups of development and acceptance code deployed to serversAs agreed by the maintenance team in August 2023 backups are stored on level up from the application folder rather than inside those folders. |
---|
Backups of Production Environments: \\tctestmaster\wwwappsroot\Saf-Sec-Sur\2\_backups\CAWIS-SWIMN\prod_backup |
---|
Publishing to acceptance and production CAWIS External: use the Staging profile to publish to acceptance and production. It does not contain the admin modules. Using the incorrect profile will expose protected B info. CAWIS Internal: use the Acc profile to publish to acceptance and production Refer to the following document: |
---|
AAIR Accounts on development and acceptance:
SCENARIO | USER ID | Mark (tailmark) |
---|---|---|
Password for all accounts is Clark2005! for development and acceptance | ||
005256 | ||
Single Aircraft | 005197 | |
Owner not reported in years | 596873 | |
Regular user | 014885 | |
Fleet | 558885 | FALE |
007278 | ||
Goes directly to Modify mode without having to press a Modify button. | 004084 |
Configuration:
See: CAWIS - configuration settings for Dev and Acc (TR47_CAWIS_GENERAL_PROPS and web.config)
Shared Mailboxes
The following shared accounts are applicable on both development and acceptance. All members of the maintenance team have access:
On development, the email address for these shared accounts is set to our shared CAWIS development mailbox.
On email box address is cawis-dev-swimn@tc.gc.ca
On acceptance the address is: cawis-acc-swimn@tc.gc.ca
On production the address is: tc.aair-raina.tc@tc.gc.ca
See: Shared Mailbox Mapping Procedure
Updated texts for AAIR Owner form with contact info only (short form)
All new messaging that should appear on various AAIR pages is contained within this document - AAIR - November notification to aircraft owners.docx
Updated contact PDFs are posted to dev and acc, were also deployed to Production
See subtask 311255 Replace existing PDF under Contact List menu with new PDF
Document locations on dev and acc
EXTERNAL DEV - \\ncrws499\cawwwappsx\saf-sec-sur\2\AWD-CN\documents
EXTERNAL ACC - \\wwwapps2test\wwwappsroot\Saf-Sec-Sur\2\AWD-CN\documents
INTERNAL DEV - \\ncrws499\catcappsx\Saf-Sec-Sur\2\AWD-CN\documents
INTERNAL ACC - \\tcapps2test\tcappsroot\saf-sec-sur\2\AWD-CN\documents
Business Rules:
see also
AIRCRAFT CANNOT BE SALE REPORTED OR INVALID ADDRESS
THE AIRCRAFT CANNOT BE A MEMBER OF A FLEET
THE AIRCRAFT CANNOT BE LISTED AS OUT-OF-SERVICE
THE AIRCRAFT CANNOT HAVE HOURS ALREADY RECORDED FOR THE REPORTING PERIOD (CURRENT YEAR - 1)
THE AIRCRAFT CANNOT BE LISTED WITH A YEAR OF MANUFACTURE EQUAL TO THE CURRENT YEAR
THE AIRCRAFT CANNOT BE ULTRALIGHT/ADVANCED ULTRALIGHT
THE AIRCRAFT CANNOT BE DEREGISTERED
Creating an AAIR Account:
Login to CAWIS Internal as a TC User.
To obtain current tail marks run the following report: 5008 Files by Owner.
Select 5008 Files from the left-side menu.
Do a quick search by tail mark:
type in 2 letters - for example "FE"
Change email address to one that you can access.
Save.
Logout.
On the external website, Login AAIR
Click forgot user id or password.
It will ask for the tail mark and email address that you changed in the 5008
CAWIS will send you an email with a link and click open link
It will ask to create a password
Save
Take note of the client id in the email.
Login AAIR: client id & password (that you created)
AAIR info from October 2023 discussions onward:
TC login uses the TC login ID but the password is not the same.
For TC Login, the same credential works on both CAWIS internal and external.
I have provided access for the TC Login option on CAWIS development and acceptance to all members of the maintenance team.
Maintenance team have access to CAWIS prod for maintenance purposes only (Only for work related to tasks submitted by the client. No changes can be made without approval from the client)
AAIR does not use our TC Login credentials.
AAIR login is unlocked on CAWIS external for development and acceptance.
The same AAIR credentials work on both CAWIS external and internal
AAIR login is currently purposely locked on prod per work that Hiren and I collaborated on in March 2023
See also https://dev.azure.com/transport-canada/DSD-CIVAV%20Support/_boards/board/t/AAIR/Backlog%20items
AAIR login is locked on all CAWIS internal instances (development, acceptance and production).
See Subtask 301363 https://dev.azure.com/transport-canada/DSD-CIVAV%20Support/_boards/board/t/AAIR/Backlog%20items
Should the option for AAIR login be displayed on CAWIS internal?
0 Comments