Readylog Import Stages

Readylog Import Stages

Purpose and when to use this record

Review a staged ReadyLog import row before it is accepted into Brisk’s law-enforcement records.

At a glance

• Identify it by: Status.

• Why care: Use the agency’s approved terminology and access policy. Preserve dates, responsible personnel, case links, and audit history because these records may support official reporting or custody review.

• Why care: Status communicates workflow progress to other staff. Change it only when the underlying work, approval, payment, or handoff has actually occurred.

Before you begin

You need the Brisk permission for the action you are taking on readylog import stages. If a Create, Edit, or Delete control is absent, do not work around it with another user’s account; ask an administrator to review your role.

Fields and business rules

Brisk stores 6 user-relevant fields for this ReadyLog Import Stage, including 0 linked-record selections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this full reference.

Field	Required	What it controls
Record Type	Yes	The record type recorded for this ready log import stage.
Dedupe Key	Yes	The dedupe key recorded for this ready log import stage.
Source File	No	The source file recorded for this ready log import stage.
Payload Hash	No	The payload hash recorded for this ready log import stage.
Status	No	Current status of this ready log import stage. Available values: Imported, Skipped, Error.
Error Message	No	The error message recorded for this ready log import stage.

What happens next

Use the originating business process to interpret this ReadyLog Import Stage. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Common mistakes and troubleshooting

• The record will not save: Recheck Record Type, and Dedupe Key and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Status, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Compare this ReadyLog Import Stage with the source document or approved setup decision, then check the downstream screen where it is used.