As Symphony is now integrated into Notes Client, it would be great, if a Lotus Script Class library could be provided. With greater integration between Notes Document Fields data exchange to Symphony documents.
I don't know how many manhours this would have saved me, but ancient records finding their way back into dbs can often only be found by the added property. However this property is currently only available through the API making it more difficult to gather docs by.
I can't think of how many times I would have appreciated being able to get a handle on another document open in the UI. Ideally, the NotesUIWorkspace should return handles on whatever is open in the UI, whether its a database, view or a document.
I developed a website where there is a feature to sort/move the content documents. A sort/move action would modify (Sort Order Number) most of the documents. If some error came up, some of the documents will be in modified state and some will be in original state. This mess up the ...
the ability to have the document id of the selected document(s) returned without having to add a column with the documentID in it would save having to create those workarounds...
Allow document link to design elements (forms, views, agents etc) to be sent to other Notes developers.
If the recipient has Designer then clicking on the link will open the corresponding design element.
In a existing response document, @InheritedDocumentUniqueID returns the @DocumentUniqueID. That is to say, only when the response being created, the formula behaves like what its name suggests. That's rather misleading. Why not return the parent document id, I think it's not so complicated for you can get it from $Ref.
With Notes 6, the Domino server will prevent two users from editing the same document in the Notes client. Awesome. Additionally, the NotesDocument.CopyToDatabase method will not allow a document currently being edited to be copied. Why can't we tell via the NotesDocument properties who has a document open in edit ...
A special kind of view that can show documents that exist in memory only; are not saved to disk. This way I could compute joins on documents and "save" them to the in-memory document that would be shown in the view. Essentially any time I would create a stub document ...
It would be nice to have the option to highlight a document in a view and have the highlight move to that document when you switch to another view in that database. Sometimes it is necessary to see a document in a different context. For example, from a view containing ...