Maintaining Job Locks

• Maintaining Job Locks
  • Overview
    • Conditions for the System Setting Locks
    • Conditions for the System Releasing Locks
  • Process
  • Related Preferences

Overview

A lock is a protection device to lock a job or job scheme to ensure that only one person works on a job, job scheme, or job scheme rack, at a time, to protect the integrity of the job's structure as it undergoes analysis, reporting and invoicing.

If a job, job scheme or job scheme rack lock is set by the system, then subsequent users have read-only access until the lock is released.

Locks are scoped by organisation, laboratory, job, optionally by scheme, and optionally by scheme rack (from—to) and records the date-time at which the lock was created and a link to the user who caused the lock to be created, and the date-time at which the lock was deactivated.

Sometimes a user wishes to access a job or job scheme but cannot because a lock is left in place that should have been released. Maybe the application shut down outside of normal processes, or perhaps the connection to the application was lost. In this case, a user may wish to manually release or delete a lock.

Conditions for the System Setting Locks

• Conditions for Setting Job Locks from Registration
• Conditions for Setting Job Scheme Locks from Workbook
• Conditions for Setting Job Locks from Invoice or Financial Report

Conditions for the System Releasing Locks

• Conditions for Releasing Job Locks set from Registration

• Conditions for Releasing Job Scheme Locks set from Workbook

  A user with the correct permissions can unlock one or more cells in the following situations:

  • There is a preference that permits the cells to be unlocked

  • The workflow state (for example, cells may not be able to be unlocked once the results are validated)

  • Other locking mechanisms (the user may have locked a column as part of the current workbook session)

    Note: A locked cell is locked for editing only. It is re-calculated whenever a dependent variable is changed.

• Conditions for Releasing Job Locks set from Invoice or Financial Report

Process

The CCLOCK—Lock application is used to maintain job locks. Locks on jobs, job schemes and job scheme racks can be returned from a search so that lockouts can be managed, and locks can be manually released or deleted, if necessary.

Job and job scheme locks should be deleted periodically to remove old locks.

Searched locks can be exported to a report. Available report templates are defined in the SEARCH_REPORT_CCLOCK application preference. Refer to Generating Grid Reports.

If a lock is released, changes can be made to the job by other users.

Note: A job may still be locked based on user permissions or the job's Workflow Status.

Maintain job and job scheme locks

The Job Code and Job Name indicate the related job to which the lock is applied.

The Scheme Code and Scheme Name indicate the related scheme to which the lock is applied, if it is applied at job scheme level.

The From Rack Number and To Rack Number indicate the related racks to which the lock is applied, if the lock is applied on individual racks at job scheme level.

Locked By and Locked Date indicate the user and the date-time at which the lock was applied.

Unlock Date indicates the date-time at which the lock was deactivated, either automatically or manually.

Related Preferences

If a job is locked to the current user (job is opened in Workbook for example), the previous experience is that the same user cannot open the job or sample in CCREGN or CCSAMP. If the REGISTRATION_IGNORE_CURRENT_USER_JOB_LOCKS is set to TRUE, then the same user can now open the job in CCREGN or CCSAMP.

If a job is locked to the current user (job is opened in CCREGN for example), the previous experience is that the same user cannot open the job or sample in CCWKBK. If the WORKBOOK_IGNORE_CURRENT_USER_JOB_LOCKS is set to TRUE, then the same user can now open the job in CCWKBK.