@cindoum
I did start it before the project's pause.
Need to resume it and change minor thing to model (not supposed to be related to Entity model)... User, entity, customer will all have status.
@mabouchalkha how we decided to handle this? Status has a object_type (ex: Entity, User, Customer) so when retrieving the status to show for a customer Status.where(:object_type => 'customer').
We could add a is_object_type on all models that need it and get the class name... So class Entity
Plus some global status like 'disabled'...
Is that ok with you?
Are you ok if we say that all standing data has status_id and is_disabled and all live data has status_id and is_cancelled ?
After discussion. Each global entity (status, notes, documents) will have a relation table (ex: status_entity). So a status (Ex. 'in process') can be linked to many entity (ex: job, receipe)...
Finish Status page / model / test
@cindoum I did start it before the project's pause.
Need to resume it and change minor thing to model (not supposed to be related to Entity model)... User, entity, customer will all have status.
@mabouchalkha how we decided to handle this? Status has a object_type (ex: Entity, User, Customer) so when retrieving the status to show for a customer Status.where(:object_type => 'customer').
We could add a is_object_type on all models that need it and get the class name... So class Entity
Plus some global status like 'disabled'...
Is that ok with you?
Are you ok if we say that all standing data has status_id and is_disabled and all live data has status_id and is_cancelled ?
After discussion. Each global entity (status, notes, documents) will have a relation table (ex: status_entity). So a status (Ex. 'in process') can be linked to many entity (ex: job, receipe)...