Posted: 2 Aug 2016 2:29 EDT Last activity: 3 Aug 2016 10:45 EDT
Cell highlight required in Repeat Grid
There is a requirement where system should highlight a particular cell in repeat grid. The records in the cell is changed and needs to be highlighted in color. How to achive this requirement ? The complete row/record should not be highlighted.
Business Scenarios: User wants to see highilighted records which are changed in any particular cell of row in repeat grid.
Appreaciate your help. Thanks!
***Updated by Moderator: Vidyaranjan | Included Category, Removed user added #helpme and Ask the Expert tags. Apologies for confusion, shouldn't have been an end-user option***
You can open the Skin rule applied for your Repeat grid, Create a new Mixin of your requirement (Use bold color to highlight the Property Text)and then navigate to Components tab and select Trees and grids. Override the exisiting Mixin to highlight particular property in your Repeating grid.
Please try this suggestion and let me know if it helps you.
If you get a chance , kindly go through "Introduction to Styling an Application" topic under User Experience chapter in CSSA 7.1 course which will help you to understand in deep about configuring the Skin rule.
Thanks Ravikiran.Please find more explaination below on the issue.
User want to understand the change performed on the screen. The editable grid is provided to the user to enter data. I want to highlight changes entered by user in the particular cell of the grid. (I dont want to highlight complete row/record)
I think , the first thing we need to do here is use a kind of flag which will keep a tab of whether a particular cell value is getting changed or not.
Along with that , maintain two columns for each items. Like for example, if you want to display employee data via grid and have to show emp id, emp name , then instead of two columns , have four columns in the grid. Two each for Emp id and Emp Name.
Control the visibility using the flag and use inline style to change the color code for the cell.
A little weird but I think this is a good way to start . Later you can try optimizing it further.