Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 300
  • Last Modified:

Documents created using agent do not enforce readers field

Hi,

I have an agent which creates documents and populates readers and authors fields. Once the agent is done running, anyone with reader access to the database can access all of the documents, even if they are not in the readers field! Doing a ToolsRefreshAllDocuments fixes the problem, but I don't like this solution. I don't want anyone who is not listed as a reader to be able to view these documents at any time, instead of the current solution where they can see it between the time that document was created by the agent and the time the refresh is run.

Why is this like this and how can I fix it?

(Sorry I don't have more points to spare)

Zaphod.
0
Z_Beeblebrox
Asked:
Z_Beeblebrox
  • 3
1 Solution
 
sk5tCommented:
If you are doing this with script, you'll need to set the .IsAuthors and .IsReaders properties on those fields.  Until the document is actually computed with the form (which [ToolsRefreshAllDocuments] does), whatever you have assigned to the fields are "just plain values" to Notes.  Use NotesDocument.ComputeWithForm in LotusScript.

If the agent is purely formula language, and it does not run on the frontend, then it gets kind of messy.  (By which I mean, you'll probably have to write the document's UNID to an environment variable, then do @Command([ToolsRunMacro]) for a LotusScript agent that gets the doc by that UNID and runs ComputeWithForm on it.)

Steve
0
 
Z_BeeblebroxAuthor Commented:
Thanks for the quick response. calling doc.ComputeWithForm (True, True) just before saving the document did the trick.

Zaphod.
0
 
Z_BeeblebroxAuthor Commented:
Whoah, I think I was a bit too quick to dish out the points. That solution worked a little too well. I had a field which was of type authors which had as a default value the creator of the document, namely me. However I can no longer see the documents. I know they are there, but there is no way that I can get to them.

Zaphod.
0
 
Z_BeeblebroxAuthor Commented:
Yikes, another issue. I have a role called [Readers] which allows people to read all documents in the database. However the agent does not respect this.

I can get around the previous issue by manually setting the field to be the current user, but this role thing is a bit of a problem.

Zaphod.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now