CCPRDT—Product Detail

Processes associated with this form
Screen flows
  • Submit—Validate and save the changes.
  • Refresh—Reload the original data. Any changes made since the last submit are lost.
  • New—Create a new item related to the application.
  • Save As—Create a new item based on the information provided by an existing item.
  • Delete—Confirm and delete the current item.
  • Open—Display a dialog box to enter an existing item to display its detail.
  • New Search—Return to the Search screen and clear the search results and the search criteria.

  • Activate—Activate the current item making it available for use.

  • Suspend—Suspend the current entity making it unavailable for use.

  • Approve—Approve the product for export so that they can be used globally by all laboratories. This updates a product's Approve Date and user who has approved the entity. This action only applies to org-scope entities and is only valid for entities in the user’s current organisation.

  • Unapprove—Reverse the approval of the product that was previously approved for export. This clears a product's Approved Date and user who previously approved the entity. This action only applies to org-scope entities, and is only valid for entities in the user’s current organisation.

Header
  • Organisation Scope

    Indicates whether this entity is available organisation-wide or laboratory-wide.

    • Checked—The entity is available to users who are logged into any laboratory within the organisation.
    • Unchecked—The entity is only available to users who are logged into the current laboratory.

    Setting the product's scope upon successful creation depends upon the user's security level for the CCPRODUCT:CREATE resource. The possible security levels for the resource, from greater scope to lower scope, are:

    • full—full
    • 3—LAB AND ORG
    • 2—ORG ONLY
    • 1—LAB ONLY

    A user can have multiple roles, and each role can contain different rights. Any of these role-right combinations may contain the resource.

    If the resource does not exist across all role-right combinations for the user, then the user has no access to the resource. Otherwise the user's security level for the resource is determined as the greatest scope across all role-right combinations for the user. For example, if a user has Role1 that contains RightA, and Right A contains security level 2 for the resource, and the same user has Role2 that contains RightB, and RightB contains security level 1 for the resource, then the user has a security level of 2 for the resource.

    The selection in this field can determine the visibility for other fields in this form, and the content of various drop-down selection lists.

  • Organisation Code

    The code of the associated organisation.

  • Product Code

    The unique code assigned to the product.

  • Name

    The name of the entity. Maximum length of 200 characters. Multi-language support.

  • Description

    The description of the entity. Maximum length of 400 characters. Multi-language support.

  • Product Category

    A category assigned to the product. Selected from categories with a Category Type of PRODUCT.

  • Status

    The status of the product. Display only. This can be:

    • Draft—The product is under development.

    • Published—An product is ready for use by the laboratories in scope.

    • Suspended—The product is no longer available for use.

  • User Code

    The code of the user who last changed the status. Display only.

  • Status Changed Date

    The date-time at which the last change was made to the status of the entity. Display only.

  • Report Name

    The reportable name for the product.

  • Status Changed Reason

    The reason for the change in status. Display only.

  • Report Description

    The reportable description for the product.

  • Chemical Name

    The chemical name of the product.

  • Primary Specification Code

    The code of the specification that is flagged as the primary specification of the product. This becomes the default Primary Specification for a sample when it is associated with the product. A product can be associated with multiple specifications with a Specification Type of Product. One of those specifications can be flagged as the primary specification used for QC specification assessment. Each specification contains the expected analytical limits for a sample to be considered conforming to the product.

  • Manufacturer

    The manufacturer of the product.

  • Disposal Sample Handling Code

    The code of the sample handling action associated with the product. A sample handling action may be selected from the drop-down list that contains active sample handling actions in scope, as configured in the CCSHND—Sample Handling application. Click the field hyperlink to display the CCSHND—Search Sample Handling screen, select the appropriate value and click Select and Return to populate the field with the selected value.

  • Script Code

    The code of the script run during a product assessment to perform custom assessment based on the product. A script may be selected from the drop-down list that contains active scripts in scope with a Script Type of Product, as configured in the CCSCRT—Script application. Click the field hyperlink to display the CCSCRT—Search Script screen, select the appropriate value and click Select and Return to populate the field with the selected value.

  • Document

    Documents can be uploaded, downloaded and removed from this entity. The additional documents can be used for a variety of purposes, for example:

    • Linking additional documentation to an entity, such as a client, contact or project.
    • Reporting additional details about the entity.

  • Image

    An image can be uploaded, downloaded or removed from the entity.

  • Line of Business Code

    The line of business associated with an org-scope product. This field is not relevant to lab-scope products. You can only attach an org-scope product to a sample if the product has a line of business matching one of the laboratory's lines of business. A line of business may be selected from the drop-down list that contains active lines of business in scope, as configured in the CCLOFB—Line of Business application. Click the field hyperlink to display the CCLOFB—Search Line of Business screen, select the appropriate value and click Select and Return to populate the field with the selected value.

  • Approved Date

    The date-time at which the org-scope product was approved for export. Only relevant where the Organisation Scope is selected. Display only.

  • Approved By

    The user who approved the org-scope product for export. Only relevant where the Organisation Scope is selected. Display only.

  • Auto-validate

    Indicates whether a sample scheme analyte result that conforms to the product specification limits aree validated automatically as long as there is no composite QC status failure.

Specifications Tab

The specifications associated with the product.

  • Grid flows

    • Create Product Specification—Launch the CCPRDTSPFN—Product Specification Detail screen to create a product specification and associate it with the product..

  • Organisation Scope

    Indicates whether the specification is available organisation-wide or laboratory-wide.

    • Checked—The entity is available to users who are logged into any laboratory within the organisation.

    • Unchecked—The entity is only available to users who are logged into the current laboratory.

    Setting the product specification's scope upon successful creation depends upon the user's security level for the CCPRODUCTSPECIFICATION:CREATE resource. The possible security levels for the resource, from greater scope to lower scope, are:

    • full—full

    • 3—LAB AND ORG

    • 2—ORG ONLY

    • 1—LAB ONLY

    A user can have multiple roles, and each role can contain different rights. Any of these role-right combinations may contain the resource.

    If the resource does not exist across all role-right combinations for the user, then the user has no access to the resource. Otherwise the user's security level for the resource is determined as the greatest scope across all role-right combinations for the user. For example, if a user has Role1 that contains RightA, and Right A contains security level 2 for the resource, and the same user has Role2 that contains RightB, and RightB contains security level 1 for the resource, then the user has a security level of 2 for the resource.

    The selection in this field can determine the visibility for other fields in this form, and the content of various drop-down selection lists.

  • Specification Code

    The code of the associated specification.

  • Name

    The name of the associated specification.

  • Description

    The description of the associated specification in context of the product.

  • Specification Description

    The description of the associated specification.

Product Type Tab

The alternate nomenclatures for the product, for example, other names by which the product is known in the market place.

  • Product Type

    The type of alternate nomenclature for the product:

    • Classification

    • Synonym

    • Other.

  • Description

    The classification, synonym, or other nomenclature for the product.

Hazards Tab

Hazards associated with the product.

  • Hazard Code

    The code of the associated hazard.

  • Description

    The description of the associated hazard in context of the product.

  • Hazard Description

    The description of the associated hazard.

Notes Tab

Notes associated with the product.

  • Notes

    Reportable text for the product. Rich text formatting can be used to control the appearance of the information, with basic formatting ribbon and hyperlink entry field. For example, the name of a product can be entered in bold, the telephone number in italics, and hyperlinks can be used. The formatting is saved along with the actual content.