It has been suggested that some more incremental outcomes would be desirable, e.g. "Approved with qualifications", "Approved for specific usage", etc.
To be clear, this would just affect the application list as far as the users are concerned -- we can already create whatever data we want in the data tables, but in the list everything is labelled with one of the above.
My suggestion would be to leave this field as it is (enums), but create a new table of custom outcomes, with fields:
id
name
description
colour
base_outcome (which must be one of the core values above)
Then add a "custom_outcome_id" field to application table that links to one of these. By default it would be null, in which case the list would show the existing Outcome label. But if a custom outcome is defined, we then display that label, in its defined colour, instead of the basic ones, in the list.
Work required:
schema changes as above
update the "changeOutcome" action to handle custom outcome input, and update according, including giving the application one of the "core" outcomes that it's related to.
Currently, every application ends with either:
It has been suggested that some more incremental outcomes would be desirable, e.g. "Approved with qualifications", "Approved for specific usage", etc.
To be clear, this would just affect the application list as far as the users are concerned -- we can already create whatever data we want in the data tables, but in the list everything is labelled with one of the above.
My suggestion would be to leave this field as it is (enums), but create a new table of custom outcomes, with fields:
Then add a "custom_outcome_id" field to application table that links to one of these. By default it would be
null, in which case the list would show the existing Outcome label. But if a custom outcome is defined, we then display that label, in its defined colour, instead of the basic ones, in the list.Work required:
This isn't a huge job in itself (prob only a day), but it wouldn't be much use unless reviewers had the ability to select additional outcomes, which would require https://github.com/msupply-foundation/conforma-server/issues/1113 to be done too.