Hello all,
I’m trying to devise a simple prototype workflow database to deal with purchase requisitions. What I’ve done so far is to design the app so that only certain people can see an action button which allows them to ‘Approve the request’. This then sets a field to ‘Approved’.
However I’d like to extend this so that the document is signed by the person approving the request so that the purchasing department can be sure of its validity. This is where I’ve got a little stuck.
It would appear to me that controlled access sections are the best way of doing this. However it seems that even though the ‘Approved status’ field is in this controlled section, any change to the doc will sign the section - which is not what I want.
Am I am going about this the wrong way - are CAS’s not used in this way ?
It is also feasible that a doc might need to be approved by multiple people - an hints or extensions for this ?
Many thanks in advance !
Matt
Subject: Signing documents by controlled access section
I am currently working on a Purchase Requisition database for our Purchasing department. Since our company has a number of different people that will give the approval for purchasing the items, I have a field that the approver’s name is listed and the buttons do not appear if the approver’s name and the user reviewing the document are not the same. If they are the same, the button appears, but after they have approved or rejected the button, the buttons will no longer appear. Would something like this work for you?
Thanks,
Jean
Subject: Signing documents by controlled access section
We have implemented a digital signing scheme in our document management system that allows multiple signatures to be applied. It works as follows.On the document that collects the signatures, there are several Sign buttons (along with fields that record who has signed, who can sign, etc.).
Pressing one of the Sign buttons calls NotesUIWorkspace.DialogBox with a different form (call it an approval form). There is one approval form for each of the signatures that can be applied. This approval form has an access-controlled section that contains the fields over which we want to generate the signature. It also has an apply signature button, which essentially calls NotesUIDocument.Save which in turn generates the signature (of course, the script sets the value of the ‘Form’ item to its original value before doing this save. It can also save other useful information about the signer, date of signing etc. for display in the original form).
To verify the signature at a later date, the approval form can be reopened in exactly the same way, although further saves are disabled. The section header then displays the signer’s name and time of signing. If anything had managed to modify the items in the access-controlled section it would display a warning that the document has been modified since signed.
This solution therefore allows several digital signatures to be saved, formed over the same set of items. In principle, it also allows changes to other items on the document to be saved subsequently without modifying the signatures that have already been saved.
Subject: Signing documents by controlled access section
How digitally-signed controlled-access sections work: Every time a user saves a document, the Notes client resigns all sign-enabled controlled-access sections to which the current user has edit access.
It sounds like you’d prefer that the section is signed only when the contents change. I’d try making the section formula depend on a CWC field which computes to the desired value, but then gets reset to revoke everyone’s edit rights by your Approve button. I’d suggest resetting it to contain a single role that isn’t typically assigned to anybody, and if you need to get edit the section again after the fact, you can simply assign the role to yourself or someone else as needed.
This should work because the user’s rights to edit a controlled-access section are determined by the Notes client at document Open, so changing the access formula while the document is being edited will have no effect on the user’s access to the section until the next time the document is opened. However, I’ve never tried this with a signed section, so there’s a chance that the signature won’t get applied – but I’d bet heavily against that.