HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Forms is no good, as often a document will have its form changed as it progresses through workflow
It should be at the document level
Moving config & parameter & profile docs to another db is a possibility
Not sure I understand your second paragraph though
Alternatively, instead of using another more hardcoded field, just give forms an additional property telling the update task to include (or not include) documents using that form in FT index.
But there already is a form property which decides if a form can be used in form based FT search. Perhaps that already is a perfect fit. Then just have update task to use that form flag to FT index these documents, or not.
Workaround: If you have such amount of parameter and config documents that they really matter to FT indexing, just outsource them to a separate config/parameter database which is not FT indexed.