workflow would ignore isCmoRequest value and would allow samples to get labels generated assuming that the rest of the sample data is valid and would successfully generate a label for it
UI icons: https://mui.com/material-ui/material-icons/?query=refresh
Proposed flow:
Plan A:
- Dashboard -> publish request-samples to validator w/flag to indicate validator should send samples to label generator
- Validator treats samples as CMO samples (same CMO label validation checks), publishes samples to the label-generator
- Label-generator generates labels for samples with validationStatus = true
Plan B.
- Dashboard -> publish request samples directly to the label-generator - ignoring validation status
- Label generator force generates labels for samples as if they were CMO samples, ignores validation status
workflow would ignore isCmoRequest value and would allow samples to get labels generated assuming that the rest of the sample data is valid and would successfully generate a label for it
UI icons: https://mui.com/material-ui/material-icons/?query=refresh
Proposed flow:
Plan A:
Plan B.