Configuring QualityOne Mobile (HSE, QMS)

QualityOne Mobile is a complementary mobile application to the full QualityOne Vault application for Apple iOS and Android devices. This application lets users access the QualityOne Vault remotely from their devices to log NCRs (nonconformances) and to log and track health, safety, and environmental (HSE) Incidents.

Users can log NCRs against Purchase Orders, Production Orders, and Processes and log Incidents against Environmental Event, Injury Illness, Property Damage, and Vehicle incident types. Mobile NCR and Incident records are reported through the mobile application and are managed and investigated within your QualityOne Vault once submitted.

QualityOne Mobile Objects

QualityOne uses the following objects and object types to support QualityOne Mobile:

For NCR objects and object types:

• NCR (ncr__v): This object stores nonconformances.
  • Process NCR (process_ncr__v): This NCR object type stores duplicated data from Process object type.
  • Product NCR (product_ncr__v): This NCR object type stores duplicated data from Production Order object type.
  • Supplier NCR (supplier_ncr__v): This NCR object type stores duplicated data from Purchase Order object type.
• NCR Mobile Submission (ncr_mobile_submission__v): This object stores data from the native QualityOne Mobile application.
  • Purchase Order (purchase_order__v): This NCR Mobile Submission object type stores purchase order information. This object type references the Product, Units, and Organization objects.
  • Production Order (production_order__v): This NCR Mobile Submission object type stores production order information. This object type references the Product, Units, Material, and Manufacturing Location objects.
  • Process (process__v): This NCR Mobile Submission object type stores information about processes.
• Purchase Order Line Item (purchase_order_line_item__v): This object stores information about purchase order line items. This object references the Product (Item), Product Version (Item Version), Specific Product, Material, and Organization objects.
• Defect Category (defect_category__v): This object stores information about the category of defect.
• Defect Type (defect_type__v): This object stores information about the type of defect.
• Manufacturing Location (manufacturing_location__v): This object stores information about locations. This object references the Facility object.
• Unit (unit_of_measure__v): This object stores units of measure. This object references the Facility object.
• Material (material__v): This object stores all information about a material.

For Incident objects and object types:

• HSE Event (ehs_event__v): This object represents health, safety, environmental, and vehicle or property damage incidents.
  • Injury Illness (injury_illness__v): This HSE Event object type stores injury illness incident information.
  • Environmental Event (environmental_event__v): This HSE Event object type stores environmental event incident information.
  • Vehicle (vehicle__v): This HSE Event object type stores vehicle incident information.
  • Property Damage (property_damage__v): This HSE Event object type stores property damage incident information.

Contact your Veeva Representative to enable the following objects in your Vault:

• Item Group (Brand) (item_group__v): This object stores information about item groups, product families, or brand names to which product variants or line extensions can be related.
• Item Version (item_version__v): This object stores item version data. This object references the Item, and Item Group (Brand) objects.

Device Support

Before you start to use QualityOne Mobile, review the list of supported mobile versions to ensure your device is compatible.

Azure AD SSO Support

QualityOne Mobile supports Azure AD as a single sign-on authentication method and assumes your organization has completed any required external configuration for iOS devices only; Android devices cannot use Azure AD SSO. See Configuring Single Sign-on for more details.

Ensure that you update the redirect URI in Azure AD to qualityonemobile://authorize. We do not recommend continuing the use of dynamic redirect URIs. Contact your Veeva Representative for more details on updating the redirect URI.

Configuration Overview

You can control how QualityOne Mobile displays for users by making configuration changes. All configuration for QualityOne Mobile is done within Vault. Although QualityOne Mobile is automatically available for all QualityOne Vaults, we recommend you complete all of your configuration before giving users access to connect through the application. If you make any configuration changes after users start working with the application, inform your users to sign out and sign back in again to see the configured changes.

Configuring your Vault to control the user experience of QualityOne Mobile involves the following steps:

1. Enabling visual evidence attachments
2. Modifying object requiredness
3. Displaying custom objects
4. Modifying field visibility
5. Modifying object field labels
6. Defining layouts
7. Configuring NCR Mobile Submission lifecycle
8. Configuring object actions
9. Configuring user permissions

Enabling Visual Evidence Attachments

You can allow users to attach visual evidence when logging their NCR and Incident record in QualityOne Mobile. To do this, select the Allow Attachments checkbox for the NCR Mobile Submission and HSE Event object. If attachments are not allowed for the objects, the plus () icon does not appear in the application for users.

Modifying Object Requiredness

You can change the attribute User must always enter a value (required) for fields for the NCR Mobile Submission and HSE Event object types so that users are always required to enter values for specified fields when creating NCR or Incident records.

Displaying Custom Objects

You can display custom objects in QualityOne Mobile as object reference fields on the NCR Mobile Submission and HSE Event objects. Users must be granted the appropriate permissions for any custom objects.

Modifying Field Visibility

You can hide object fields for the NCR Mobile Submission and HSE Event object types so that users see and interact with only the fields appropriate to your configuration.

Modifying Object Field Labels

You can modify field labels on the NCR Mobile Submission and HSE Event object and its object types. Modifying a field label does not affect a user’s ability to search in QualityOne Mobile when searching the field label content. Custom objects are sorted by the object name regardless of any modifications to display fields.

You can also add custom fields to the NCR Mobile Submission object and the HSE Event object. The following custom field types are supported:

• Text, including Longtext but excluding setting a default value.
• Number, excluding setting a default value.
• Date, excluding setting a default value.
• Yes/No, including the attribute Show as checkbox but excluding setting a default value.
• Picklist, including the attribute Allow user to select multiple values.
• Object, including object references for up to two (2) fields but excluding setting a default value.

If you add any custom fields, ensure you also add them to the appropriate layout.

The following fields defined in Vault are not used within QualityOne Mobile and are hidden in the application:

• Created By
• Created Date
• Global ID
• Last Modified By
• Last Modified Date
• Lifecycle
• Lifecycle Stage
• Lifecycle State Stage ID
• Link
• NCR Mobile Submission Type
• Reported By
• Status
• Name
• Lifecycle State

Defining QualityOne Mobile Layouts

You can modify layouts for the NCR Mobile Submission and HSE Event object types so that users see and interact with fields appropriate to your Vault’s configuration. If you do not define a layout for the object types, the base layout for the NCR Mobile Submission object and HSE Event object displays for users. While NCR object layouts do not affect the NCR Mobile Submission object layouts for QualityOne Mobile, the HSE Event object layout is shared between QualityOne Vault and QualityOne Mobile.

NCR Mobile Submission Lifecycle

NCR object records created from QualityOne Mobile use the NCR Mobile Submission object lifecycle and contain the following states:

• Pending: This is the initial, default state when an NCR is created but does not yet contain all details and attachments (visual evidence).
• Submitted: Records transition from Pending to Submitted when the NCR Mobile Submission object is created including all attachments.
• Error: Records in the Error state encountered errors when transferring data from the NCR Mobile Submission object to the NCR object.

You can add custom lifecycle states to suit your organization’s specific needs.

Configuring QualityOne Mobile Object Actions

You can configure QualityOne Mobile to ask users to run follow-up record actions after successfully submitting their NCR and Incident records from their device.

To do this, you can add the following actions as user actions for the NCR and HSE Event object lifecycles:

• The NCR object lifecycle contains the Workflow: Submit NCR for Verification action for the Initiated state.
• The HSE Event object lifecycle contains the Workflow: Submit HSE Event action for the Draft state.

Configuring User Permissions

You must ensure users have the appropriate read and create permissions to access the appropriate objects and object fields in addition to the permissions outlined below:

• For the HSE Event object and its object types: Read and Create permission.
• For the NCR object and its object types: Read and Create permission.
• For the Process object: Read and Create permission.
• For the Production Order object: Read and Create permission.
• For the Purchase Order object: Read and Create permission.

Application Permissions

You must ensure users have the appropriate application permissions enabled:

Type	Permission	Controls
Permission Set	Application: Client Applications: QualityOne Mobile: Enable	Ability to access QualityOne Mobile.
Permission Set	Application: Client Applications: QualityOne Mobile: Enable NCR	Ability to access QualityOne Mobile NCR.
Permission Set	Application: Client Applications: QualityOne Mobile: Enable Incident Management	Ability to access QualityOne Mobile Incident Management.
Permission Set	Application: Vault Actions: API: Access API	Ability to communicate with Vault.

Related Permissions

You can complete all the steps in this article with the standard System Administrator or Vault Owner security profile. If your Vault uses custom security profiles, your profile must grant the following permissions:

Type	Permission	Controls
Security Profile	Admin: Configuration: Object Workflows: Edit	Ability to modify object workflows.
Security Profile	Admin: Configuration: Objects: Create, Edit	Ability to create and modify Vault objects.
Security Profile	Admin: Security: Permission Sets: Edit	Ability to modify permission sets.