sale_receipt_validation_queue

This table tracks the validation status of sales receipts within a queue system. It's likely part of a larger sale receipt processing workflow.

Model

Field	Type	Nullable	Default value
id	int4
current_validation_queue	varchar
sale_receipt_id	json
user_A_validation_status	int4		not done
user_B_validation_status	bool		not done
created_at	timestamp
updated_at	timestamp
team_member_validation_status	varchar(50)		not all
team_member_validation	json

Description of fields

id

Unique identifier for each entry in the queue.

current_validation_queue

Name of the current queue the sales receipt is in. This likely reflects different validation stages.

1. user

2. team member

sale_receipt_id

Foreign key referencing the ID of the associated sales receipt in a separate table.

user_A_validation_status

This column represents the validation status of the allocated user A. These 4 values are coming in this column.

1. not done

2. pending

3. done

4. not allocated

user_B_validation_status

This column same as the `user_A_validation_status` column. But this status represents the validation status of the allocated user B. These are 4 values coming in this column.

1. not done

2. pending

3. done

4. not allocated

team_member_validation_status

This column represents the validation status of a team member. These are below-mentioned values are coming in this column.

1. not allocated

2. done

team_member_validation

The column represents what response the team member gave if there was a mismatch between the reactions of two validators for that sale receipt. So, this column stores the team member's responses. For reference:

{
    "team_member_response": 
    {
        "1": "A", 
        "2": "A", 
        "3": "A", 
        "4": "A", 
        "5": "A", 
        "6": "A", 
        "7": "A", 
        "8": "A", 
        "9": "A"
    }, 
    "rejection_reason_ids": []
}