hibernate - How to do database design for entities which require an approval workflow for updates -
for example, have entity called bankaccount has following attributes:
bank_account_id bank_name branch_name account_number account_type swift_code iban_code ifsc_code status (possible values - new, active, suspended, terminated) ...
when account created done in "new" status. still not active in system. end user requests approval , background workflow triggers. upon final approval status flipped "active".
there may subsequent updates attributes end users, including status change suspended or terminated. such changes visible / effected after workflow approval. hence need mechanism capture changes not persist them in same table immediately.
q. how implement database design , application layer logic , can handle such interim states ?
( using hibernate persistence layer )
wiki
Comments
Post a Comment