Hi M's,
Martins idea is a good approach but I am not a fan of copiing over stuff to a second datebase and remerging it afterwards - my idea:
I assume, that we dont have to approve complex editing on the request but only simple state-changes - this means that is not possible to edit for example the DN of a request and let this editing only happen if two admins approve that - I dont see a use case for this....
Si I will set a mark on the original entry to point out that is processes "outside" the currrent table and establish a second table, that just holds information on the proposed action/state-change.
If the number of needed operators agreed we can simply change the originating object, if one disagrees we delete the action-proposal table.
Phone Conference is a nice idea - I should be able to setup a 3 person one with our HiCom here
Oliver
-- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72
smime.p7s
Description: S/MIME Cryptographic Signature
