Maker Checker Approval DB Structure

Question

Maker Checker Approval DB Structure

deepakkn

Default port

Points: 1430
More actions
November 13, 2009 at 12:56 am

#216702

We have a ClientMaster table, and we need to do Maker/Checker for the same if anyone updates the record.
Means, if any of the column has been modified by Maker, it goes to 'Pending for Approval Status'.
The Checker Screen consists of only the modified records and Checker Approves the Status and make it Approved.
We need to show the old data in other screens till the Checker Approves the record.
We thought of the following solution.
we can have a table ClientMaster_Status (with the same structure of ClientMaster) and when maker modifies any column,
only the modified Value will get inserted into ClientMaster_Status table.After Approval of the Checker we can update the value in the main table.
The problem with this solution is that ClientMaster_Status table consists the value of only one column or two and all the other columns will be blank.
Do we have any other solution other than this?
We need to do this for all the Master tables.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 1

I have been stewing on your problem and don't think your solution is probably the right one. I see a few issues like how do you distinguish maker updates from checker updates because for a trigger to allow one and send the changes off to another table for verification it needs to be able to tell EVERYTIME. The next question is do you need this setup or do you really need to make sure that you can go back to a former version of the record AND know who changed it. Also based on your solution you can approve a single field, how do you plan to handle related field changes, ie: state changed and so did city but you only approved state, result = invalid address.

If you are going to do this you should probably do it as a whole record approval/disapproval but you still need to be sure that there is an iron-clad way to tell the difference between maker and verifier.

I guess it comes down to, what is the problem or business requirement you are trying to solve for?

CEWII

deepakkn Default port Points: 1430 More actions · Answer 2

Hi Elliot,

Thanks for reply.

For the previous data, we can maintain another table like an audittrail and it stores the data of all the previous records.

Dependent fields can be modified internally when maker done the changes.

So, the same will be stored and can be updated when the checker approves.

If we are show all the fields for approval, the end user cannot recognise the actual modified field.

Some where we need to differentiate modified field and highlight it.

I guess we can do this by comparing the data of ClientMaster and ClientMaster_Status.

Thanks

Deepak

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 3

It would probably be better to do a direct compare and highlight differences. Another twist, what happens if there is more than one change, ie: a change occurs and then later another change occurs.. You would definitely need to approve them in order.

I guess I'm back to the original question, what is the problem or business requirement you are trying to solve for? What I'm asking is not the solution you are thinking about but what is driving the discussion in the first place.

Basically we can give you advice and critique your solution but not understanding WHY you are doing this hinders our ability to give assistance.

CEWII