<DOCUMENT INCOMPLETE>
Related: PBI-172152 - resource monitor report ; PBI-172153 Documentation required
CAWIS version 1.0 used a table called Z930_COLUMNS to administrate the text of all input fields and error messages.
This was replaced by the DA005_RESOURCE table when CAWIS was made WCAG compliant in 2018.
A copy of the Resource Monitor report can be found in the attachments section of this article. Its simply a dump of the DA005 table. The advantage of the report, is that it allows the system administrator to “globally” look at the contents of the resource table when determining required changes.
Currently contains - 22487 records
ER - The resource monitor report needs to be added to the CAWIS reports menu
( Select * from DA005_RESOURCE )
A significant example of this would be in 2021 when the former generic email addresses for Continuing Airworthiness
needed to be located and altered to meet the new departmental standards in all onscreen messaging.
Maintenance
The resource table can be updated by the CAWIS system admin at any time.
CAWIS-MAIN-MENU → CODE-TABLE-ADMIN → RESOURCE
Note : this option is ONLY available on the CAWIS Internal site.
Fig 1 CAWIS Code table Admin menu
Fig 2 The Resource Monitor page
Options
Reset CACHE - clear browser Cache
Reset APPLICATION DOMAIN - reset all CAWIS Login values (field labels, etc) This need to be done to invoke and review any changes made to the DA005 table using this facility
DAPLS - reset/renew DAPLS password. This taken care of by CAWIS admin.
NOTE the actual link to DAPLS is found under AAIR maintenance shown here
AAIR TC USER SUBMISSIONS INTERNAL - AAIR PAGE
under “STEP 5 APPLICANT LOOKUP“
Resource Statistics - ?? Client does not understand this
Select a page - perform update operations on messages within specified subsystem of CAWIS
Fig 3 - Select a page - Identify the page where you need to make updates
Fig 4 - Select a page - In “value”, enter freeform text of the messages you’d like to review (example : weight - returns all messages related to aircraft weights )
0 Comments