"dynamic" author /reader fieldsResponse on project: Qenos Application Framework

My Links (Not logged in)

Project: Qenos Application Framework (Managed by Mark Demicoli)

Actions:

Response


Subject	"dynamic" author /reader fields
Created	05/09/2007 07:14 AM by Mark Demicoli.
Modified	<none> by <none>.

Body

Sure Wim, this would work. You could create an agent which uses the wfRefreshSecurity function in the _QAF WF API library or indeed create a copy of the RefreshSecurity agent and trigger it as desired.

However in principle I would recommend a different approach because your proposed scheme has subtle implications that can reduce the quality of your application.

Consider that:

1. Users will need to be fully aware that your application is subject to a scheduled security refresh - this is a dubious scheme because it puts the onus on the users` technical understanding of the relationship between applications.
2. Modifying a large set of documents on a regular basis renders the application prone to save / replication conflicts.

If you can organise the sort of discipline to handle the above, you're fine.

As a general rule, I use ACL roles or Domino Directory groups in QAF roles that are used in document security. This way, the onus is on Domino to do the processing which boils down the groups/roles to determine access (DYNAMICALLY), rather than the individual names stored inside fields.

Please realise that this is not a limitation of QAF, rather it is a design consideration for any application that uses data in document fields to evaluate reader / author security.

Hope this helps!

-Mark

Feedback

Hello I'm investigating whether QAF... (wim stevens on 05/09/2007 05:58:03 AM )

. . "dynamic" author /reader fields (Mark Demicoli on 05/09/2007 07:14:45 AM )

. . . . thanks (wim stevens on 05/09/2007 08:56:13 AM )

. . . . . . QAF API (Mark Demicoli on 05/10/2007 04:08:59 AM )

Check out other projects