Set up- lower and upper limit to a report cell

this feature can be implemented easily by using the cube worker in the supervision server. this is much more convenient because it is not report-related but catched on a database level.

I think the feature should not be limited to upper and lower bound of a decimal value, as requested but be extended. There are already good concepts which should be considered:

1. Microsoft Excel features quite a set of cell data validations, see Apply data validation to cells. In addition to List (already implemented) and Decimal (described above) there is also Whole Number, Date, Time, Text Length and Custom. From my point of view, all these can be useful, Whole Number, Date and Time being more important than Text Length and Custom.

2. The modeler features a similar concept for attribute values, see Creating and Handling Attributes. In addition to List of values, Subsets and Stored Subsets (already covered implemented as the List feature) there is also Boolean, Integer Range (with is another term for Whole Number), Float Range (which is another term for Decimal, which is described above), Date range (which is another term for Date), Time range (which is another term for Time), Date & time range and Year & month range. It would be good to share concepts between the Domain for attributes and it's UI in the Modeler Grid with cell data validation on web spreadsheets where feasible.

3. It would be nice to refer to the Domain of an attribute value as defined in the Jedox In-Memory Database (by database, dimension and attribute name) for the cell data validation instead of duplicating the definition in the spreadsheet. This would reduce maintenance and enhance the consistency between multiple reports and between the reports and the database. (For cell values other than attributes values there is no definition in the database yet, which one could refer to)