...
The file number on the front-end of the application that the clients refer to, is actually the LICENCE_NUM in the database.
This license number must exist in DAPLS first, and is automatically pushed into CAMIS every hour. You can check if it is in CAMIS by searching in CAMIS → Applicant → Applicant Search. Alternatively, you can check the database itself in MV002_DAPLS_AAPLICANT
which is the materialized view into DAPLS and in YA003_APPLICANT
which is the CAMIS copy once the push is done.
CAMIS Weekly Auto-Accept report steps:
Backing up Production Data:
...
CAMIS / eMER Region Change:
CAMIS / eMER Region Change - BSD - Civil Aviation - Confluence (atlassian.net)
Expand | |||||
---|---|---|---|---|---|
| |||||
The following script is used to fix an ongoing issue with the document naming scheme. The issue is that eMER adds the date of submission in the file name, but CAMIS doesn’t expect it. eMER does: CAMIS expects: Script to run:
|
Expand | ||
---|---|---|
| ||
User must be added into 2FA database before they are able to give eMER access to CAMEs To log in to eMER, the user must have a valid cell-phone number in their CAMIS profile in order to receive the 2FA SMS code.
6. If we can not find any error in above steps, and even if the eMer status is changed from Inactive to active and CAM still does not get the 2FA SMS code: Email to a CAMIS administrator to keep a copy of original number, modify that phone number in CAMIS to the different one (fake ones), with the “active” eMER status, click update, then put back original phone number, click update. CAMIS administrator then will need to generate a new activation code. CAM will sign in eMER using the new activation code and he/she would receive 2FA SMS codes after that. |
Expand | ||
---|---|---|
| ||
Note: The assignor is able to delete any tasks they created. Tasks are saved in |
Expand | |||||
---|---|---|---|---|---|
| |||||
Example: Open CAMIS, enter the file no, get to the specific MER record and “View eMER record”, the “Submit MER Confirmation” will show the Applicant Details' name is different from Applicant (on top of the page). On the same page, go to the “Documents” section, you must see the wronglastname-wrongfirstname--mer.html and wronglastname-wrongfirstname--mer.pdf. How this issue can happen: CAME (doctor) creates a new applicant on EMER application with the right name of applicant He enters medical data, however at Applicant Details section, he enters the wrong given name and wrong last name. He has to view, click the check box before click “Submit MER”. However, he might forget to review the names here After summitting MER, the file has been submitted to CAM (CAMIS client) and there is a wronglastname-wrongfirstname--mer.html which contains all medical data is saved in the UA018_document table with a document_nbr On CAMIS application, CAM is now opening the file, checking the “incoming eMER' and assigning the file to a specific CAM . At this point, I do not know yet that specific CAM has done something on the file (he might confirm it), then there is wronglastname-wrongfirstname--mer.pdf saved in the UA018_document table with the next document_nbr Database Notes We can find licence_nbr and medical_examination_id in UA006_medical_examination WE can find html and pdf file under UA018_document Here is the SQL we can use to check if the person has the right names in the medical files. These info will be shown on the file names This below SQL is from PK_EMER_MEDICAL_EXAMINATION.SP_get_mer_step6
Fix: Using database within CAMISP.WORLD,
|
Expand | ||
---|---|---|
| ||
The clients cannot modify eMer on Camis because submitted date of the eMER is before the medical examination date. This happens when CAM chooses the examination date in the future Fix: Find the medical_examination_id from the client’s information, on UA006_MEDICAL_EXAMINATION, change the medical_examination_dte is before or equal date_emer_submitted_dte |
Expand | ||||
---|---|---|---|---|
| ||||
Required info: The file no. that was incorrectly assigned and the correct file no., applicant id that the eMER should be assigned to.
Required info: The name of the applicant and stamp number of the examiner (or exam date). Within CAMISP.WORLD, in the table
Required info: The license number of the first applicant and of the second. Make sure to first check that both license numbers exist in CAMIS. If not, you will need to wait for it to get populated in DAPLS. The following script merges an applicant into another one (MERs, related activities, assessments, docs, etc.).
Create a related task and include the script you ran. Verify in the application if the changes were successful, you can search the correct file no. and look in the Tests & Docs. and MERs tabs to verify if the files are there. In CAMIS (prod): Enter the file number in the resulting form: |
Expand | ||
---|---|---|
| ||
On CAMIS, entering a file number, at Tombstone tab, click on “Add/Update Indicators”, if there are missing indicators: Check YA003_APPLICANT of that applicant, at date_deleted_dte to see whether the field is empty or not. If that field can be empty, then the missing indicators will appear |
Expand | |||||
---|---|---|---|---|---|
| |||||
When we have a task to delete address associated with stamp number (see bug # 244024 Delete address associated with stamp number) Within CAMISP.WORLD, in the table In the table
|
Expand | ||
---|---|---|
| ||
related DevOps Task: 201977 eMER found in applicant's Test & Docs tab not in MERs Tab If an eMER is not listed under “Incoming eMERs” in CAMIS:
2. If the eMER was deleted by the CAME (or business client) follow-up with the requestor to confirm if the record should be deleted. If the requestor confirms the record should be undeleted, update the DATE_DELETED_DTE to NULL.
|
...