Hi All,
Our application requires security and so I am utilising the readers and authors fields. This works quite well. I do have a problem where a particular form is initially created by a 3rd party application. It would appear that when this application creates a new form, it simply writes its necessary data to designated fields and any programming within the form is not carried out. As such, the default values for the Authors Field is not applied when the form is created by the 3rd Party Application. As such, people with Author access in the ACL can open the form, but not edit it.
I created a 2nd Authors field on the form and got the 3rd Party App. to write a group name to this field which should then give people in that group editor access. This is the same group used in other forms successfully. I have checked the contents of the 2nd authors field and it looks fine.
I can fix the problem by refreshing the form, but this defeats the purpose and requires manual intervention every time a form of this is created - which is often!
Is the process of creating a new form from the 3rd party app. the problem??
Is there a script anyone can suggest that could be incorporated in a scheduled agent to refresh the form design?
I wrote an agent to do this manually using @functions, but because the authors don’t have edit access to the form, the agent doesn’t work unless carried out by the database administrator??
Any suggestions would be appreciated - big time !!
Phil Peckman
Subject: Authors Access Problem
How is the 3rd party app creating / writing the new documents? There is a ‘computeWithForm’ method that might be able to be called from the 3rd party app which would solve your problem.
Alex
Subject: Authors Access Problem
The problem is that when the 3rd part application is populating the new document, it’s probably just creating Text items in the document. That is the item that it’s putting the group name in is not, at that time, an authors item. This is becuase Notes is not using the form at all to create the document items - it does not know that an item should be set to Authors.
You can check that by looking at the properties that item in a new document.
There’s 2 ways to make that item an actual Author item.
Open the document with the form, and save it. Notes now sees that the form on the field is an Authors field, and saves the document item as Authors.
Have the 3rd party application tell notes that that field is Authors.
If using LotusScript, that done by setting the NoteItem’s IsAuthors property.
Alternatly, use the ComputeWithForm to tell Notes to use the form’s field definitions to set the item properties.
Subject: Authors Access Problem
Alex’s direction makes good sense, it would be how I would try to solve the problem.
However, why are you using a second Authors field? Why not populate the existing Authors field with the group name.
You should be able to schedule that agent to run, what happens when it is scheduled.
Shawn
Subject: Authors Access Problem
As already has been suggested you might need to run an agent that does a computwithform on all new documents because when a field is created in the Backend document everything is text unless you specifically set it when the document is created. The form controls the data type, so when opened in a form and refreshed and saved all of the fields get ‘typed’, so either have the import routine smarter and do the’typing’ or write a small agent that periodically runs that makes sure the data is ‘typed’ by using ComputWithForm.