Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

(IT Personal) Using the IATF CARA Tool on thin clients will require to store the users app data storage for the browser. Please check the detailed folder for the used browser.

Saving in internal DB

Using the tool all changes are directly saved to the IndexDB. This happens automatically without delay and can’t be changed. This allows the user to close the browser or leave the tool and reopen it to continue his work on the report.

...

You can configure the auto backup in “Settings->Backup & Database” in the field “Create a backup on close after x days” which allows you to set the amount of days. By standard this is set to every second weeks. This can be changed up to 365 days and down to 0 days, which means on every close. On every close will still allow a time gap of 15 minutes, so if you have created the backup but not left the page directly you won’t be asked yet again within that time.

...

...

Save

All reports and the NC Management reports on their own can be exported apart from the backup. This allows to share or merge reports with other auditors or to save a specific version on your hard disk. Additionally the NC Management can be export for the customer to use the NC-CARA Tool which is a version of the CARA Tool which allows the organization to complete their NC Management report part in CARA as well.

To improve compatibility to other systems reports can be exported in json and xml. A detailed data description is provided in Cara data Data description.

...

...

Load of report or backup

On using import the user can select the file from his storage which he wants to load. Double clicking on IATF CARA files won’t auto start the tool or an import.

The tool recognizes data and report types based on information within the file. So importing of the backups and reports and even NC Management reports will be done automatically using the “Report/Backup import” button. It doesn’t matter if the file is xml or json formatted. All reports have to use unique ids (created automatically on new) so they a recognized on import and the user is warned if he is going to overwrite an existing report.

...

Because the tool can not recognize if reports have to be merged the user has to choose the import report to merge functionality to access the merge functionality using the standard import will ask if the report is going to be overwritten if it already exists. Please check Work on reports by multiple auditors (Load report to merge) on details of merging. This process can be repeated as often as required.

...