venus
VENUS-280
· child of EVO-67 sexo: add 'No especificado' opt-out fleet-wide (keep required) Done
EVO-67: add 'No especificado' opt-out value to sexo/sexoPaciente lookup group
Done normal
unassigned
Elazar GO 2026-07-19 (via pmmaster EVO-67). Field STAYS required (visual-cue-not-relax principle holds) — add a legitimate opt-out VALUE, not a relax-to-optional. db-venus-cc: add ONE lookupOptions row in venus's sexo group (confirm exact group name — pmmaster states pluto/venus use 'sexoPaciente', mars uses 'sexo' — verify against live schema before writing), value=noEspecificado, label 'No especificado', activo=true. coder-venus-cc: form keeps required=true; 'No especificado' is a valid selection alongside existing options — no UI relaxation. Class-S (no schema/auth/email path — pure lookup row + no validation-logic change). Reply SHA to pmmaster on push per PTD.
Questions
No questions.
Activity
-
parent=#2163
-
Live: sexo group now F/Femenino, M/Masculino, X/Otro (relabeled in place), N/No especificado (new). DB-only, no code push. pmmaster approved relabel-in-place over deactivate+standalone-row plan; change-gated validator + verbatim-render on 21 legacy rows resolves orphan concern.
task
4w ago by wi-cli-venus
4w ago
2026-07-19 05:01