Note: Minimum Required Ivinex Version: 4.3.1The display colors tool is found in the module details window (in the admin area). After clicking the Display Colors link, you will open a new window where you can build your display color rules.
Color RulesClick the new button to start creating a display color rule. After clicking the new button, you will be presented with a new color rule that has the following settings:
- Evaluate Field: The field that will contain the value.
- Value: The value that will trigger the color rule.
- Text Color: The color that will be applied to the text.
- Background Color: The color that will be applied to the background.
- Color Field: Which element will be colored (row or table cell).
- -- Entire Row --: This is the default value. When there is a value that matches the color rule, the entire ROW will be colored according to the color settings you provide.
- Specific Table Cell: The options that appear here are based on what module you have selected and what fields have been setup to display as columns. When there is a value that matches the color rule, the TABLE CELL that you select here will be colored according to the color settings you provide.
- Delete: Click the delete link to delete the color rule.
Note: TEXT, DATE, TIME, INTEGER, DECIMAL, CHECKBOX, PHONENUMBER, SELECT, RADIO, LINKED RECORD, USER, and TIMESTAMP DIFF are good candidates for creating color rules.
Warning: You must currently use the ID in the color rule VALUE field for the following field types: SELECT, RADIO, LINKED RECORD, and USER.All color rules that you setup will only be applied to your current selected data module. To create color rules for a different data module, select the new module and then start setting up your color rules for that data module.
Note: Currently it is not possible to clone/copy color rules from one data module to another (even when creating a new data module based on an existing data module). This should be resolved in the near future.
Color Rule Examples
Multiple ColorsWhile coloring the entire row can be helpful, it can also override the current theme functionality of highlighting the current selected record (in the list). Here is an example of using multiple colors per row.
Using "Blanks"It is possible to use "blanks" for setting up color rules. There are a few things to note before doing this. If you are using a field like a text box, then leaving the Value field blank will work just fine. If you are using a LINKED RECORD, SELECT, RADIO, or other field that has multiple options or stores an ID, then you must type a zero "0" in the Value field. The zero will act as a "blank" for these types of fields.
Advanced UseYou may find that just typing in a Value or leaving the Value blank, does not fully support what you want to do with the Display Color rules. What if we want to compare the Value using GREATER THAN or LESS THAN (or something else along those lines)? While it is not possible to build this type of logic using the Display Colors tool, you can use other fields and/or workflows to populate a field that the Display Color rule Value will match. Since the Display Colors rule will always depend on a single value, your other fields in combination with workflows can trigger when the color rule is true.
Example: We have a lead module where records are created in Ivinex from a web form. When our staff calls leads, they set a field called "Last Call Date". We have a TIMER workflow setup to check if the last call date is EQUAL TO the last call date +15. If so, the timer workflow will set a field called "Priority" to "High". Our color rule is looking for a value of "High" in the "Priority" field.The example above is just that.. a simple example of using fields and workflows to add more logic to when a Display Color rule should trigger. Explore the Display Color tool and let us know (or leave a comment below) if you have come up with a really clever way of using it.
- 30 August, 2013 @ 15:40 [Current Revision] by Ivinex Customer Support
- 30 August, 2013 @ 15:40 by Ivinex Customer Support
- 19 August, 2013 @ 22:50 by Ivinex Customer Support
- 19 August, 2013 @ 22:49 [Autosave] by Ivinex Customer Support
- 19 August, 2013 @ 19:31 by Ivinex Customer Support
- 19 August, 2013 @ 19:30 by Ivinex Customer Support
There are no differences between the 30 August, 2013 @ 15:40 revision and the current revision. (Maybe only post meta information was changed.)