There is a managed app on the Appexchange and it solves a limitation by employing a "Track History" concept to give admins a boolean setting specific to each datafield on User object (for the purpose of tracking its field history). , This allows admin(s) to define/manage a common set of preferences for Tracking History on User fields.
How would we modify the concept of "Track History" from the image above to build a visualpage that allows the user to manage TRUE or FALSE settings specific to each field in a dynamic fields describe call for a given custom object?
The page must "remember" (persist between page loads) the user's boolean selections for all fields in a custom object.
Unlike the "Track History" example, i dont need to track any field history. I just need to build a visualforce page that reads/writes boolean inputs (“settings”) to a user-specific cache or object where each input is specific to a dynamic list of fieldnames. I believe hierarchical custom settings are the way forward here. Another reason I'm choosing hierarchical custom settings in this design is because it is possible for users to read/write their own custom settings via visualforce
My guess is that the page needs to dynamically describe field names, then query the user's existing hierarchical settings (where they may have indicated boolean preferences for fields), then construct the input booleans on the page according to their settings or defaulting to some default in the case of no found settings record for the given field.
Has anyone tried this with any success?
Thank you community!