Skip to Main Content
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

Status Under Consideration
Workspace Domino
Created by Guest
Created on Oct 8, 2018

Notes Views: Separate UI from Index

I'd specifically like to be able to...

  • display keyword field values depending on a user's locale; e.g. if a keyword's stored (alias) value is "1", display it as "In Progress" to EN users, "In Arbeit" to DE users etc. in view columns.
  • display view column titles depending on a user's locale.
  • Attach files
  • Guest
    Reply
    |
    May 29, 2024

    One not exactly perfect tweak would be an option to show the 'text' of a keyword field in views, not the alias, saving us all sorts of formulas to display values making sense to the user and rendering the UI better.

    This would be very practical for categories as well.


    Could take the form of a checkbox :


    show alias value


    If not checked, the keyword is shown, if checked, the alias. If there is no alias, the keyword is shown.

  • Guest
    Reply
    |
    Oct 9, 2018

    Forgot to mention: The first column formula (according to my previous comment) would be evaluated by the indexer, while the second column formula would be evaluated by the client when rendering the view.

  • Guest
    Reply
    |
    Oct 9, 2018

    Regarding your second question, "how do you see this mechanism works": As mentioned in the subject line of this idea, I want to separate the view index from its UI. For example, this could be achived by having two separate column formulas -- one that defines what value to store in the index, plus another formula that defines how to display the column value in the UI. For column titles, it would be sufficient to allow them to be computed (as proposed previously by others).

  • Guest
    Reply
    |
    Oct 9, 2018

    see related idea:

    https://domino.ideas.aha.io/ideas/DDXP-I-188

  • Guest
    Reply
    |
    Oct 8, 2018

    And where should you put the translations?

    how do you see this mechanism works?