HOWTO: No docs ae seen in a view until tea-time?

Hi everyone!

Can I construct a view selection formula, so no document can seen in a view until a specified time?

Thanx in advance,

Dmitry.

Subject: HOWTO: No docs ae seen in a view until tea-time?

I’m not sure it’s the easyiest way : an scheduled agent which adds a reader field at specific time…cheers

jean-michel

Subject: HOWTO: No docs ae seen in a view until tea-time?

Dmitry,Yes you can, except that it is very inefficient.

Subject: RE: HOWTO: No docs ae seen in a view until tea-time?

I made it this way:

SELECT @If((@Now<@Time(11;0;0))&(@UserAccess(“server.name”:“database.nsf”;[AccessLevel])<“4”);@False;(Form = “PRESS”) & (SECTION=“Главные новости”))

Here: only our analytics (users = editor access or greater) are allowed to see documents before 11.00.

Any comments?

Subject: RE: HOWTO: No docs ae seen in a view until tea-time?

You should set the view refresh frequency to once and hour (or two). Else the indexer will never finish building the view (as @now is constantly changing).

Subject: RE: HOWTO: No docs ae seen in a view until tea-time?

That approach won’t work. According to the help, @UserAccess doesn’t work in view selection formulas. I’m not entirely certain how you’d like it to work, so I won’t suggest concrete alternatives, but I suspect that you want to handle part of this with Readers fields.

Subject: RE: HOWTO: No docs ae seen in a view until tea-time?

As others have said, an agent to set the Readers field at 11:00 would work. If you don’t want to mess with Readers fields, just have your agent run daily at 11:00 and have it set the field “ShowInView” to “Y”. Then your view selection can select documents with ShowInView = “Y”.

Something along those lines may work as well. However, this solution won’t provide security like the Readers field solution.

Subject: HOWTO: No docs ae seen in a view until tea-time?

Schedule an agent to run at a specific time. Have the agent change the view selection formula.

However, the result will really only make sense on one replica. If the agent runs at 4:00 PM EST on server A, the view change won’t appear on server B in another time zone until the servers replicate, and so on.