Groovy Series 4: Playing with cell level formatting
When it comes to highlighting certain data cells or making them read only, we all must have got our hands dirty with validation rules and valid intersections. Undoubtedly, they make things quite descriptive and help to control data entry when required. But at the same time, the trouble to maintain all these objects is equally troublesome. Lets consider three random scenarios which client must have proposed to highlight certain cells on a data form or make certain cells read-only If the entity is E105 and COA member is among ‘A66001’ or ‘A82580’, colour it red If the entity is E100 and COA member is A65001 , colour it green If COA member is A84001 , make the first open period of scenario as read only Considering the above requirements, if we intend to implement them, we would have to create validation rules to highlight the cells and create valid intersections to make specific cell read-only. W hat if, we have multiple calculating scenarios which run in isolation, say Plan scenario wher...