xpages document will not ever switch to the edit mode - xpages

I have tried using the simple action to toggle mode, simple action to change mode to edit, have the view link open the document in edit mode. Nothing actually puts the document fields into an editable state. There are not any authors fields on the document and I have manager access to the database. This is an application update of a classic notes client app to a xpages UI. So I am working with existing documents. I am totally clueless as to what to look at. There are zero errors in the browser or the server console. I can edit the documents just fine in the notes client.
If I create a test application and use the same methods to put documents into edit mode using the above mentioned methods, it works just fine. But not with a xpage using the existing documents. Any guidance you can give me on what to look for would be greatly appreciated.

Check the ACL and your author fields and the Internet access as Sven suggest

Related

Message while accessing lotus notes application at Lotus Designer

I have Manager rights at the ACL of an application .When I open this application from designer it gives me below error
"you cannot view the design of this database because it is hidden "
I dont know what went wrong with this application . Can any one help
You need to have access to the template (usually an .ntf- file) of the database.
The design of the database was hidden when replacing the design using a template.
There is NO WAY to access the design of the database anymore.
There was a hack some years ago where you could open SOME of the design- elements by editing some bits in the nsf with a HEX- editor, but this does not help you at all as it does not make the relevant code visible.
Wihtout access to the template that was used to create the database there is no chance for you to do anything with the design of that database anymore.

Xpages: Track changes when user updates document from Xpage

A business owner of my ticket tracking app in Xpages wants to track every change to the document. If a user opens the doc in edit mode but doesn't change anything, then no tracking. If, however, they open up a document and change one field, I have to capture that.
Here is my solution. When a user edits a doc, I create a "shadow document", which is a "before" vision. When the user saves I am comparing field for field for changes, and then acting appropriately.
Is there a better way to do this?
This is another good use case for Java beans. If you create a bean which sits between XPages-UI and Domino back-end document then you can easily track field changes.
Karsten Lehmann wrote a blog about it some time ago.
... and you could use the OpenNTF Domino API that has functions for exactly this. As far as I remember there is an example of this in the demo database. Not sure if it is also in the new version of the demo database - but then you may just need to find an older version (e.g. for milestone 4.5 where I saw this).
/John

how to invoke Out Of Office Service in lotus notes domino in Java

i am using domino designer 8.5.3 and my notes client and server are also above version 8. Manager level access is given to the user and run on behalf of field is also set correctly. can anyone tell me how to start out of office service through java code.
There is some sample code in this question that shows how to access the Out Of Office profile document.
For the rest of it, I can't answer your question, but I can teach you how to answer your own question.
The fields in that document control the Out of Office settings. You want to change those settings in code, so you need to figure out exactly what changes occur in those fields when you manually do what you want your code to do for you. You will need to analyze those fields to figure out which ones changed when you do it manually. These are the fields you need to change in code.
You can use NotesPeek to look at the fields and their values. Doing this before and after making manual changes to the settings, and compare the values of the fields should give you everything you need to know, but because of caching of profile document values, I would recommend the following steps:
Use NotesPeek to examine and record the field values in the Out of Office profile
Using the Notes client, manually make the changes to Out of Office settings exactly as you want your code to do.
Shut down Notes completely. (This means the client, designer, and admin clients, and NotesPeek. Everything. If you have any doubts, just reboot.)
Use NotesPeek to examine the field values in the Out of Office profile, comparing them to the values that you previously recorded. Note what has changed.
Then just write your Java code to modify the appropriate fields, and save the profile document.

Xpage the Domino bookmarks nsf

I am trying to create an XPage version of the domino bookmarks.nsf used for creating the home page in the client. The users want to be able to see their most used databases with a link to go straight there.
Does anybody know how the domino favorites works and how to consume data from it?
The bookmark.nsf is beaten in mystery only by the desktop.dsk :-)
All entries in the Open button are stored as Outline design elements. Outlines are read/write in the LotusScript/Java/SSJS API, so you could grab them in a SSJS library. I don't know when/how the favorites are updated

SharePoint 2010, Upload Document Redirect to Page

I have a document library in SharePoint 2010 that several different teams are using for the same purpose. Each team has their own page that has a filtered view of the document library on it. The document library also has custom columns.
The issue I am running into is when a team member uploads a document from their page. They click "Add document" from their page, and then they browse to the document they want to upload. This part works perfectly - and the URL specifies the source as the team's page. However, after a user selects the document and clicks "OK", it takes them to the EditForm.aspx page that allows the user to fill in the meta data for the document. This is fine, but now the source URL specifies a view from inside of the document library, and no longer points to the team's page (where they came from).
Does anyone know how I can change this source URL to point to the team's page instead of the document library? Or, does anyone know a workaround for this issue so that a user can upload a document from a page (with document library web part on it) so that it returns to the page?
Thanks!!
SharePoint 2010 should work the way you want out-of-the-box. I tried to reproduce your situation, but was unable to. What I did was set up a library with one custom column and two custom views. I then created two pages, one with a list form web part using one view and one with a list form web part with the other view.
When I click on the Add Document from either page, a modal dialog window opens to the Upload page. I first select the file (Upload.aspx) and then am redirected to the metadata properties (EditForm.aspx). After filling out the metadata, the dialog window closes, and the page behind it (the page we were originally on) refreshes to show the new document in the web part. So the user experience is that they stay on the page they want while adding the document as desired.
If you edit your question or provide comments with more details on your situation we can try to reproduce it, but the functionality you describe is exactly how it is supposed to work out-of-the-box.
Peter's correct - SharePoint's being SharePoint.
If I am reading this right, it may be that you should simply check out in-line editing. Using a view, you and edit the properties dynamically without leaving the page (each team getting their own view).
Alternately, I see many who simply want to redirect users back to the page they came from either edit or view of an item regardless of where that was (a link, etc.). Simplest way to do that is a little programming by adding a button to the forms replacing the OK/Cancel with your own code. Simply edit the forms using InfoPath to add the new buttons - you have the user context if you need to custom redirect to a team home page or some such.

Resources