In R5.x, the agents designed in the host DB/nsf are visible even though the view displayed in the frameset came from another DB/nsf. But after upgrading to R6.5.3/R6.5.4, the “local” agents are no longer visible in the Actions menu. Instead, the agents of the DB/nsf where the view came from are visible. Also, the View, Go to, and View, Agents results in the views and agents from the other DB/nsf.Is this part of the changes in R6 or R6.5?
Subject: Agents visible in R5 but not in R6 client
Check the ACL settings in the database. If you don’t have Designer access you will not see some design elements.
Subject: RE: Agents visible in R5 but not in R6 client
Hi Julie, thanks for the reply. Actually I’m the designer (with Manager’s access) of the database.
My observation is that, the context of the Menu (i.e. File, Edit, View, Create, Actions, etc) changed from the “local” database to the “foreign” database.
To refresh you on the problem, I have a Frameset with a Frame containing a View from another database. In R5, the Agents appearing in the Actions menu are the Agents of the “local” database. Apparently, in R6, the Agents appearing in the Agents menu are that from where the View came from (“foreign”).
Subject: RE: Agents visible in R5 but not in R6 client
I asked someone on the client team if this functions as designed. This will probably take a bit of investigation. If there is more info we’ll post here. Mark this thread for the follow-up email.
Subject: RE: Agents visible in R5 but not in R6 client
Julie, MANY THANKS!!
If I may add, I tried selecting the “Basic simple appearance” in the Frame properties. This made the Agents of the local db appear while in the frame with a View from a foreign db.
However, the problem complicates. Either one of the following happens:
-
when I run the local Agent, it appears that it does not run it against the selected document but randomly run it in the document in the local db (I don’t know how Notes selects the doc). Proofs: in the agent I tried to display the form name and it gives me the name of the form in the local db. Second proof, I tried to set a value to a new field, and somehow in landed in one of the document in the local db.
-
sometimes, it says that no document is selected though it also says the 1 document meets the criteria.
-
when I set the app to start at the frameset with the foreign view, Notes appears to open an infinite number of tabs and then Notes hangs.
Subject: RE: Agents visible in R5 but not in R6 client
I’m curious to know how your agent is trying to select the documents that it runs on. If it’s by db.UnprocessedDocuments, then it’s a question of which database you’re getting and how you’re getting it. It might help if you showed your code. If you use session.currentdatabase, it probably makes a difference which frame has focus when you start the agent.
I suspect, to make sure the agent is running in the correct database and on the right documents, you will have to use NotesUIWorkspace.SetTargetFrame, then maybe NotesUIView.Documents to find out what documents you have to run on. Write a test agent that doesn’t change the selected documents, but just displays some information about them, and try out different ways.
- Andre Guirard
IBM Lotus Software
Notes/Domino Client Team
Subject: RE: Agents visible in R5 but not in R6 client
Hi Again Julie,
BTW, the Smart Icons still works! So, we transferred our code from Agents to Smart Icons. That still enables us to run the code on the foreign views.
Subject: RE: Agents visible in R5 but not in R6 client
While it IS a change, it seems to me that the behaviour is more correct in the newer version. After all, you would expect to see the view’s actions in the Actions menu, and the context of the application has switched databases. Just my 2 cents.
Subject: RE: Agents visible in R5 but not in R6 client
Stan, at first that’s my reaction . . . . .
However, this means that we have to re-write our application. We have an app that display a foreign view. The user can select documents from the foreign View and run and the local agent. What the local agent does is, it creates a new document in the local db but inherits values from the document selected in the forein view. With the upgrade this no longer works!