For the server, there is no difference, read the document from a different database or from one. In any case, the power of modern hardware this will be enough :) Other documents in 99% of cases are read more than a few profiles. From the LotusScript we read profiles a lot more and no drop in performance occurs.

Better to have the ability, than it does not have. Even more so when it is useful to many.

Notes Client modifications aimed at transferring from native to a Java-interface. The same is expected for the Domino Administrator. Another possible web-interface, which is also a negative effect on the speed. Other variants will not.Bearing this in mind, I want to Domino Administrator left alone. There are more important things that need to be engaged. Such as old storage nsf by capabilities is far behind mongoDb and couchDb (for example, the ability to store data in a JSON), poor API for working with XML, and so on.

I do not agree that we should move to LS or Java. Sometimes it is the context that is not executed in LS or Java or no flexibility. And the Shared Fields is not the answer, it is sometimes useful to get the text of the formula or formulas parts for the generation of the formula for db.Serch, etc.The eigenfunctions can be used in the Shared fields, Shared columns, and so on.Great idea! I voted for. This long is not enough.

I once suggested a similar (to make separate view like forum), but my idea is not supported, then remove it at all.I think that IBM does not need the number of votes for each idea - they always do only what they see fit.

MathieuIf implement what you ask for, it will be impossible to recover the document.I propose a solution that will permanently delete the document (later), and recover it.

> How long do you keep them?This is more of an organizational issue.I would prefer to focus not on the storage time, but to limit of removal of documents that may be important (eg registered, which were assigned a status, etc.).So removed will only unimportant documents (mostly drafts), and the others are not relevant at the moment, but necessary for the history to move to the archive.All these and other constraints (eg delete documents give only the author of the document or administrators) can be programmed in the event database QueryDocumentDelete. This is the only right and complete solution.

"Customize This View" is not easy for the average user.But to have the ability to configure it would be nice. The options are:1. By dint of choosing of common columns - selection dialog should contain comments-description.2. Hide / display columns for a specific user, by analogy with the ability to move the columns when in view setted jackdaw "Allow customizations".

Put handler QueryDocumentDelete and not remove documents from the database, and for example, change Form on "DeleteDocument", that is "move" documents to own recycle bin. And access to recycle bin, restrict administrators.

Kenneth Axi> has been X number of failed login attempts and the account has been locked - "Please contact IT-support for unlocking Your account"...This is good, but not much. The attack can be fixed to a single address to harm a person. As a result, his work will be paralyzed. Therefore, it is important to vote for this idea.

Let me explain why I'm against it.If you use direct access to the servers to the same store, this is a long time (large files pulled from the current server and so not fast). This will lead to difficulties in the network.If you have in mind their own store on each server, they can not be identical, because servers have different access to the documents, that is some of the documents (and their attachments) can not be replicated.Your idea is contrary to the principles of Lotus Domino.

> 9) Peter Neidhart635 (07.06.2012)> How to you prevent multiple parallel execution of the server agent?It is perfectly solved by using the (hard-) locking mechanism.

> 10) Mark Demicoli8588 (07.06.2012)> Actually Peter is right Notes is not an assynchronous architecture except for the 'hopelessly fragile' NotesTimer.Run multiple background agents and you get all asinhnonnost "problems" described by Peter.

I vote for this idea, as there are many operations where the wait for a response from the server, the user does not need. For example export data in a relational database. The user performed some action, and some data must go immediately. He does not need to wait for the result.

"Specifying user IDs in location documents is an ancient feature when Multiuser mode was not yet available."This is necessary for testers / developers who have to frequently switch between locations. Change between users of operating system uncomfortable.

I will support this idea, because it's great. It would be possible to transfer the templates of access control to customers. In principle, would have been satisfied with the decision to export / import ACL, but the templates better.

Ctrl+S - it is a challenge of dialogue save the page in the browser.The question must be put not so. We must have the ability to set keyboard shortcuts for the buttons or call agents in the context of the document.

The Watch Lists are not suitable, because necessary to introduce the variables manually. I vote against it.A better solution would be not to add, but delete variables from the list by removing the checkboxes in front of variables.

Automatically delete - this is implicit, but because the wrong decision. The user must in such calendar entries to see what the person was fired, and decide what to do next. Perhaps on this issue will need to communicate with another person.. removing calendar entries we do not give the ability of employees to decide.

"So I am thinking of an extra property with Computed for Display fields "Calculate in Backend"." I think that it is necessary to correct title of this idea.

I have long wanted to say that "Save" or "Not Save" of the fields must be managed by a separate property (tick in the field of any type), similar SaveToDisk. Thus we have: - variations: Computed, Editable and so on, - for all variations of fields checkbox "Store on Save" (SaveToDisk), - Computed to have an additional checkbox: "For display", "For backend", "For ...". That would be correct.

> However, it now seems that you are also knocking down my ideas. > I thought the point of this site was to put out ideas for others to vote on and add their two cents to which you have... IBM realized very little of what is proposed here. And I do not want them to spend time on ideologically and technologically wrong decisions, which is why I am so actively vote against it. I repeat: the right approach - is to seek the roots of problems rather than deal with the consequences. My ideas on it and been focused: { Link } , { Link } and { Link } , but few people even understand what it...

> I truly believe that enough developers/admins have been put through the ringer with document locking issues that IBM needs to address it. Problems described by you from misuse of the functional. If done well, as I described above, they will not. With this approach, documents can be blocked only when a server crash, which happens very infrequently. The real problem is that people do not want to understand the essence, and want their challenges decided by someone else.

> In my experiences documents don't get unlocked during a computer/Lotus Notes client crash. Understand than a Soft-lock differs from the Hard-lock. Soft-lock works, what each can independently verify: 1). Open any document. 2). Make dablclick on document: - in status appears "Document successfully locked.", this suggests that the document is locked with a soft lock. You can check this by opening the Properties window (Alt+Enter) and in the list of items see $Writers и $WritersDate. 3). Demolish the Notes Client, for example, using killnotes.exe, imitating his crash, or just manually shut it processes. 4). Load the Client again and verify the same document the presence of items $Writers и $WritersDate - they will not by, because the document is automatically unlocked when crash Client. Additional information about Soft-locking: { Link }

> Putting an icon in the view to identify locked documents is a brilliant idea. I have in each database for that there is still a special View, selecting only the blocked documents with the action for unlocking (in case of crush server).

> There are so many bugs in document locking Need to be remedied the underlying cause, ie those bugs. My ideas (really reasonable) for correcting locking mechanism were almost all demoted, and now vote for to pile up hemorrhoids at each other...

1). To work in the user interface exists and is used SoftLock-blocking, that is, documents are unlocked automatically when client or computer crashes. All other processes can be (and should, especially for the transition on the web) converted to run on the server (notesAgetn.RunOnServer command). 2). The agent will seek out and unlock the only locked an hour before the documents. You can increase this time. Problem resides in the memory, and the agent up and running very short time. By the way blocked documents can be marked in the views of any icon - it will be immediately noticeable. A user who locked the document can also remove the block. 3). To control the visibility of the button and access its functionality to add the group to the ACL is not needed. Simply add the group to the Address Book on server, and a formula to hide the Action from any database can use the code: !@Member(@UserName; @ExpandNameList(@DbName[1]; "MyGroupName"))

Jochen Sack Anything you want can be done easily, I wrote about above: -------------------------------------------------------------------------------------- Want to unlock documents automatically on the server, write an agent who will do it 1 time per hour. Want to have a certain group of people (editors) could unlock the documents - give the group the ability to run agents on the server, access to the visibility of a special action, and when it is pressed, call the same agent with RunOnServer. --------------------------------------------------------------------------------------

My opinion - you need to develop applications so that documents are properly unlock themselves at the end of a process. I am categorically against the first paragraph - this is contrary to the ideology of access; sense from a lock, if it can remove another regular user?

Want to unlock documents automatically on the server, write an agent who will do it 1 time per hour. Want to have a certain group of people (editors) could unlock the documents - give the group the ability to run agents on the server, access to the visibility of a special action, and when it is pressed, call the same agent with RunOnServer. That's all you can do yourself in 10 minutes.

Because IBM chose the direction of product evolution, this says it all. Plus XPages that development for the client and the web is the same. Cons - still limited ability controls, compared even with the Notes Client. Video by development can be found on YouTube, serial, called "Notes in nine". This is all very well, but as we say in technical forums: "Before the advent of Eclipse and XPages Dmino Designer behind the advanced development tools for 10 years. Now it has become better - it lags for 5 years." If you look at the power of Silverlight and WPF, we can see the size of the backlog in eternity, and the level of IDE (for developer) and capabilities of UI-controls (for users)...

Lotus Notes - a framework for working with databases, and why somewhere to climb on the file system and search for some files? Log analysis code is also tied to the files? It is not appropriate. Should be: 1. working in the settings is ticked "Enable Logging"; 2. suppose, for example, this tick leads to the following settings in the notes.ini: LOGSTATUSBAR=2 Debug_Outfile=log.nsf

Compression and resizing - not the same thing. I am opposed to the compression is performed automatically, since This leads to a reduction in image quality. I'm much more important quality than file size.

In most cases, lack of standard keyboard shortcuts Windows: PrtSc - copy the entire screen; Alt+PrtSc - copy the current window / dialog box; Ctrl+C in a message box - copy to clipboard text of message. For more compound cases, there are free analogs of the software.

Quickr - a product that is specifically designed for storing files. For most databases, such behavior will be detrimental (their arguments I described above). I saw no real arguments to support this idea, because voting against.

Databases are different, the forms in them are different. There are forms without RuchText field. For most of the forms is not enough of attached files, you must complete a number of fields. A logic of some applications does not imply such manipulations... How do you propose to do this? Just an idea without implementation is not enough to vote for.

What we see on the link - a primitive implementation, where hundreds of the network. I did not see the problem in GetThreadInfo (LSI_THREAD_CALLPROC), the problem in the implementation. Wrote one class in the method call recording error information is transmitted the text to which you can write the name of the current class, ie, TypeName(Me), as well as the option "to go up the stack or not". Inside the method used LSI_info(12).

But LSI_THREAD_CALLPROC and Lsi_info (12) should return "" to the very top of the procedure, so I vote for.

I am in favor of these options are divided into groups, such as options for dialogue... Option "Enable persistent breakpoints in LotusScript debugger" could be moved at all in the Domino Designer's option, as a ordinary user does not need them. And so on.

And: * Notes client crashes won't affect running Designer! Clients often fall or, for example, when visiting a long time in the debugger, somewhere within an hour debugger is not turn on - need to restart Notes and Designer, which is a long time. These situations a lot.

David You can imagine that tens-hundreds of thousands of users do not speak english? Naturally, none of them will go on some english-language websites and make phone calls, even for me it is a problem.. IBM representative of our country was removed from his responsibilities (reception bugs from users, the translation into english and placing them where necessary) early in the 2000's. Therefore refer to them does not make sense. The most that can be heard in response: "Wait for the next service pack."

With regard to this idea, it is not to engage in sophistry, such as "click on one of the links to support / help" and so on, and take note of the bug as soon as possible to issue a correction. I doubt very much that no one has seen these errors, because they periodically come up for about a year. This just shows how the company treat to such things (as I mentioned earlier), and what it prioritizes...

David You can imagine that tens-hundreds of thousands of users do not speak english? Naturally, none of them will go on some english-language websites and make phone calls, even for me it is a problem.. IBM representative of our country was removed from his responsibilities (reception bugs from users, the translation into english and placing them where necessary) early in the 2000's. Therefore refer to them does not make sense. The most that can be heard in response: "Wait for the next service pack."

With regard to this idea, it is not to engage in sophistry, such as "click on one of the links to support / help" and so on, and take note of the bug as soon as possible to issue a correction.

David A small clarification: I do not want an answer from IBM, I just report a bug. If IBM is not interested in correcting it, even if you put a message about it in twenty places, then nothing will change. If interested, you can find and take note of any open source, the more that the source about products of IBM, that is not even have to look for. I prefer to use open source in a convenient place to me because I do not need to be further somewhere else to register, and it sees and knows everything, and then let each of us draws his conclusions. Hence, my main idea - to fix bugs, and only then ideas. Or rather, what kind of realization of the ideas can be discussed if the product is full of bugs?..

For this in the Form and Subform properties have long had a special option "Do not add field names to field index". For old design elements it is not actual, but for XPages - may be... so I vote neither for nor against.

Totally agree! The problem is lack of feedback. I know several large communities of Lotus-developers and users of the post-Soviet countries that did not come here, they say (verbatim): "All the major, including on critical issues, it was proposed in 2007-2008, but almost none of This was not implemented. This site is long dead and useless."

There are other problems. For example the fact that IBM does not expend any funds for the translation of literature (even in electronic form) for developers in our language, they say (I heard it just yesterday): "technologies are developing so fast that it makes no sense to translate them" . We book markets are full of literature on the latest development technologies from Microsoft, it means that their products do not develop? This is ridiculous. And sad...

David, if it is necessary constantly to refer to someone, then why would this site?!

If it is created, it is logical that his reading and take some decisions, and therefore it would be nice if the discussion was here, not even in ten places... It is also necessary to change the status to "In Progress", if IBM took the idea to the development and the "Realized" if implemented.

4091 On Error Resume Next Set ND = NA.Parent.GetDocumentByUNID (UNID $) If ND Is Nothing Then Msgbox (Required document (UNID = ") + UNID $ + (") not found in the current database!),, "Lotus Notes ..." Else Set NUIWS = New NotesUIWorkspace Call NUIWS.EditDocument (False, ND,,,, False) End If which is easy to hide from other users access settings. Inherit it to all databases.

And if in the Server Document (Server Tasks -> Agent Manager) in the field "Max concurrent agents" is set to 1?

Conditions of performance (and settings) can be different. I think that if someone uses a functional in the specific conditions and has a problem, it does not mean that others will as well.

It may of course be you are right... But I have for years used that documentation to the 30% does not correspond to reality, and there is already some personal experience. And also we know how IBM responds to questions (which they support) - this is sad...

And if the logic of an agent involves a simultaneous change of multiple documents? How will you identify and correct the situation when the change, not all documents are current "transaction"? Need a clear algorithm (at Domino), which determines the agent hangs or works.

@4: Replicator with open automatically, and you can watch the proceedings. The whole thing only in the appearance of icons? Maybe it's good, but I believe in LND is more pressing ideas that are close to the critical...

It is known only for the current client, that is when the client starts the replication manually. When he does, the move of replication and so visible in the progress bar, so it is also not necessary. Moreover, the user most of my time working in the databases, rather than considering how beautiful glitter icons...

And why should the user know what's going on replication? What is it you? In my opinion this is extra functionality, which will overload the Notes client as well as the need to constantly send requests to the server to obtain information about the beginning / end of replication.

The agent will not be able to do this, because when translating the document into edit mode is blocked. This functionality may be good for XPages, but in my opinion, for the forms it is redundant.

P.S. It is necessary to read all 3 of my ideas and evaluate the complex, all thought out and it will work, the main thing - to realize... While I understand that those who vote against it, just do not have experience with this functionality to properly assess the ideas, the other assumptions I have not.

2. It happens that the user has remained a local replica of the old agents. It creates a replica on the server and agent (has the right, as signed by the server) starts to work - it can change the data from other databases, it can be adapted to the old model of the data, ie break the new data model. These errors are subtle, more difficult to correct them later...

Established baskets used in primitive applications, where no means a multi-user work. In normal applications use a basket of its own design. It is well known. In principle, this option is possible, but that it can be off and it was turned off by default.

I am opposed because: 1. Starts the uncontrolled creation of databases / replicas on the server and free space in the server's disk subsystem, designed for the required databases, may be occupied by user. 2. This increases the vulnerability of the server, because might be possible to run the agents, who are currently (already) can not run.

View can not display the data not contained in the document, ie, by placing the document in a folder, this option should be to record the date in the document. For other databases, an additional source of conflicts, so I vote against it. You can make your own (programmatically) write the date in the document on addition.

Thank you for your vote and comment, Peter. 1. If IBM will not support the UI, based on the Forms, you have officially reported this state, then we will not spend time with each other. 2. If XPages will work in the Notes client, and interface documents will be built on XPages, then the above problems are also possible, because mechanism, one(?) What meaning to write a second mechanism for XPages? In my opinion, better to refine the mechanism so that it worked in Forms and in XPages.

"If document locking is enabled and a user opens a document in read mode they get a warning..." This I know - this is not the situation. The situation, of which I speak (described in first paragraph) is indeed possible, that is very bad. For some applications, the conflicts are not allowed in principle, this message allows the user to perform actions not provided for the application and the developer can not affect it, which is also very bad.

I think that cleaning the cache when you start to only during debugging, and then not always. That is the best option would be a parameter in the notes.ini. A global solution - to make the container of code (or configurations) that will be executed when you start the client.

So you can specify the field names, well, maybe even a couple of other properties. All properties are still set to be impossible, it will be the same setting properties, as in the field. Is that set for all the same properties?.. Generally I do not see the point to develop an alternative mechanism to specify properties for the fields.

A simple way to replace a item value - to overwrite it (ReplaceItemValue). In order to value in $UpdatedBy changed, you need to enter under the user who will be prescribed in this item, and execute this code.

The option "Inherit from refresh or replace to modify" is present in this Custom Contols just as in any element of design. Thus, you can use these controls in different databases. I do not understand what this idea.

Ralf Petter When I write "Use" and put a space, then nothing happens, but should appear a window with a list of all libraries in the current database, so you can choose the one you want. And what do you mean?

An alternative solution could be an indication of the properties of the database name of the template from which to inherit the ACL. Or, utility in the Domino Administrator to copy the ACL from the selected database.

Thank you, Bruce, I read. What can I say: I also thought about the evaluation of ideas, but by quality, otherwise it will lead to the discarding of ideas by skin color. Now I think that all this is difficult (everyone their opinions on the correctness and so on...). Must be some kind of optimum, which would suit everyone. While I do not know any of his acquaintances, who would be comfortable current "What's Hot". What do we have? We have kinds of Popular, Most Comments, Recent Comments, but it is static. No dynamics, which should be in the hot ideas! I propose the principle of forums, in my opinion, it there would be more appropriate, fairly easy to implement and easy to use!

It is pointless for two reasons: 1. Lotus within the server sends the message almost instantaneously. 2. It is implemented entirely different principle - the default is that all messages are sent successfully, if for some reason is not sent you this will be notified. For example, if the mailbox outside the recipient is not found, then the server will perform a certain number of attempts, as he needs this for some time... And so on. Because I vote against, I and my colleagues do not have confirmation of the obvious.

One should just replace the old Netscape engine to something more reasonable and all the related problems go away by themselves. I think that this is not done, because with the advent XPages will refuse buggy Notes-UI. But I will support this idea.

"Open in new window" function in the Notes Client is useless because anyway you can not open the same database twice (for example, a journal-View with the working papers and reference-View). Here's an idea! IMHO.

But a lot of unnecessary; I would have left: * user/server(also on execution of agents) errors * user deletes a database * user change ACL * password is invalid (? doubt...) * user sends an email (to whom and the subject and Date) - but only when the letter goes beyond the organization.

> What about specifying the vew name too? With the embedding if we set tick "Choose a View based on a formula", then the event "Embeded selection" described "Formula", where varying the name. All have long been well implemented in the Outlines, there is 3 fields: - Formula for kind of named element; - Formula for database; - Formula for name of named element. I do not know, why not use the same mechanism?! Probably because IBM no longer positioned LND as a platform for development of workflow, unfortunately ... :-(

By number of votes can indirectly judge the quality of ideas. Assessment - this is good, but difficult; should we so complicated? In my opinion the main thing to know that these ideas will be implemented IBM, otherwise it all becomes a game: how many points someone has earned...

Another offer. "Top Innovators" show not by count of ideas, but by count of votes, that is, to graduation was not on the number and quality of ideas. In "What's Hot" show the most discussed ideas; it is not clear on what principle they are displayed now. I would like to see a list of ideas that IBM will realize or who are now in the implementation.

Necessary determine which settings are critical to change. If you do not allow the user to change, for example "Default font ...", it is not serious. The idea is good, but the problem is much deeper and harder it will be to implement.

There is a "Monitoring Results", but this too seemed not something ... RALS needed purely for the developer team. I do not know whether to impose this additional essence for storage (database) .. but in any case the work RALS with conservation outcomes - it is good. If these records will be displayed in the "Problems" is excellent! Under this option, you will not need an additional protocol to the opening of the design elements in Domino Designer (I think that the notes :// protocol will not be able to do this). If the tab "Problems" will be the interface to display the results of RALS (reports), then we must be able to choose these reports (from different developers and dates...).

By default can specify log.nsf on Local; if there is a setting that allows to specify another database, it will be fine. Collecting such information for all the developers in one place I think is right.

@ 6) Tom Van Aken > I'm not sure about this, but I do hope that IBM has some coding standards for Lotus applications. Judging from the mail template, it appeared that his students wrote: haphazardly named variables, a lot of global variables in each library, and even a few NotesSession and NotesUIWorkspace within one library ... about any standards even the question.

> Are the community members willing to follow these standards instead of their own. This is not a problem if they were... When something interesting was this question, because I developed my: { Link } (at the bottom there is a link to continue). It's the old standards, and, sorry, they are in Russian, but Googlle translate can give at least some idea.. The main thing in the standards did not even name the variables and elements of design, and the presence of logic.

Now I took as a basis for "OpenNTF Mail Experience (R8.5)" and corrected: - Fixed an old bug: when BackEnd-creating (from another database) of letters and opening of his on-screen field Body overwrited signature. Written for the class hierarchy to insert a signature in the FrontEnd and BackEnd. - Fixed a bug cleaning Quick Stuff. - Many improvements in the contacts (Person card). - Unification of the main global variables, some libraries. If it's someone needs...

As to the location to save the results... I believe that if recompiled database: - is located on Local then save the results in log.nsf on Local; - is located on Server then save the results in log.nsf on Server. Because it will be possible to collect this information from agent, if required.

As developer, I do not work in local replicas, because it becomes useless to use the lock design elements when working in a team.

If the server is eliminated, then this feature would be useful. If the server is eliminated and user is transferred to another server, it would be useful for desktop icons indicate new server. Icons of databases that are not found by ReplicaiD, should be removed.

The idea is good, but initially the view can display information from only one database, so I doubt there ever will be done. Previously proposed to do this with Java-applets, but it is very tedious .. Now we all hope for XPage. It seems that the old technology eventually will no longer be supported.

Colleagues, thank you for your additions! In any case, put the application icon in place under the mouse pointer. If this place is occupied, then put the application icon in free space, located right-below. This should be supported and when you open a database on Ctrl+O.

We can do custom hierarchy, that is to build the hierarchy of types of responses to a different field that has a special type of "Response Reference List" with a value in the form of 32-byte number.

In the view of simply redefined item, which by default ($REF), for example, before SELECT in the view selecting formula write: DEFAULT $REF := $RefCustom This enables the formation of different hierarchies, for various dependencies.

So, to create such a field (type of "Response Reference List") necessary to copy now $REF somewhere, then do makeResponse another "parent", rename, resulting in $REF to $RefCustom (or another name) and then return the old $REF in place ... And in order to get all the "child's" to the "parent" of $RefCustom, must either create an additional view to the selection by UNID or use notesDatabase.Search, that differently, but still affects the performance is not improved. I proposed setting and functionality techniques could elegantly solve these problems.

I apologize for my English.

:

:

Welcome to IdeaJam™

You can run IdeaJam™ in your company. It's easy to install, setup and customize. Your employees, partners and customers will immediately see results.

Use IdeaJam to:

Collect ideas from employees

Solicit feedback and suggestions from employees and customers

Run innovation contests and competitions

Validate concepts

Use the power of "crowd-sourcing" to rank ideas and allow the best ideas to rise to the top

IdeaJam™ works with:

IBM Connections

IBM Lotus Quickr

Blogs and Wikis

Websphere Portal

Microsoft Sharepoint

and other applications.

IdeaJam has an extensive set of widgets and API's that allow you to extend and integrate IdeaJam™ with other applications.