Versions Compared

Old Version 2

changes.mady.by.user Daniel Gleerup Jakobsen

Saved on

compared with

New Version 3

changes.mady.by.user Daniel Gleerup Jakobsen

Saved on

Key

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

Audit fields

...

Name

Description

Data type

Checkpoint id

The id of the audit’s checkpoint. It's unique to the audit, meaning that the same checkpoint on another audit will have a different Checkpoint id even though the same checklist has been used.

String

Checkpoint type

The type of checkpoint (Multiple choice, Standard, Text, Text Table, Measurements, Production Unit Custom Fields, Supplier Custom Fields)

String

Audit id

Unique id of the audit. Can be used for mapping the Checkpoints-data with the Audits-data

String

Checkpoint header

Name of the checkpoint header

String

Checkpoint

The checkpoint text

String

Status

Status of the checkpoint type “Standard” if the status-buttons was enabled. Status' include the following: “Checked Not OK”, “Checked OK”, “Not Applicable”, and “Pending”.

String

Comment

Comments written on the checkpoint by the Auditor during the audit

 String

Multiple choice

The auditor’s chosen answer on a multiple choice checkpoint. If multi-selection is allowed and the Auditor selected multiple choices, the answers will show as comma-separated strings

String

Score

The score (if applicable) of the auditor’s chosen answer on a multiple choice checkpoint. Note that scores on multiple choice checkpoints is not mandatory and can therefore be blank.

Integer

Max score

The maximum possible score that a multiple choice checkpoint can result in, no matter what the auditor chose.

Integer

Raw data

The raw checkpoint data as JSON format.

JSON

Corrective Actions fields

Name

Description

Data type

Corrective action id

Unique id of the corrective action

String

Audit id

Unique id of the audit. Can be used for mapping the Corrective Actions-data with the Audits-data

String

Status

The status of corrective action. Can be one of the following: “Finding”, “In progress”, “Review”, and “Closed”

String

Finding

The finding of the corrective action

String

Requires evidence from app

Is “true” if evidence is required from the app and “false” if not.

Boolean

Description

The description of the corrective action

String

Approver comment

The comment made by the Approver when setting the status of the corrective action

String

Created

Time of which the corrective action was created

DateTime

Due

The selected due date of the corrective action

Date

Resolved

The time of when the corrective action was resolved

String

Checkpoint id

If the corrective action was created from a checkpoint of an audit this field will show the unique id of the checkpoint. The id is unique to the audit, meaning that the same checkpoint on another audit will have a different Checkpoint id even though the same checklist has been used.

String

Supplier id

The unique id of the supplier

String

Supplier name

The name of the supplier

String

Supplier number

The number of the supplier

String

Production unit id

The unique id of the production unit (if any)

String

Production unit name

The name of the production unit (if any)

String

Production unit number

The number of the production unit (if any)

String

Responsible name

The name of the user responsible for resolving the corrective action

String

Responsible email

The email of the user responsible for resolving the corrective action

String

Approver name

The name of the user responsible for approving the corrective action

String

Approver email

The email of the user responsible for approving the corrective action

String

 

 

...

Users - a list of structs with full name and email, is a contact person

...

Groups - group names as JSON array

...

Custom field definition names (column headers should use the key) - field, keep hierarchical order from custom fields definitions if possible

...

We don’t show custom field definition types

...