Conditional Formatting > General Information

Introduction

Key Concepts

A conditional formatting field is necessarily associated with a level. This cannot be updated.
A conditional formatting field is composed of a set of statuses, each of which is associated with a set of rules on a set of item properties (identifier, classification, field).
A conditional formatting field can only be associated with property on an item (field, classification or identifier) from the same level.
- It is not possible to associate a given status of a conditional formatting field with a property from another level (a child or a parent).
Updating the structure of a table will automatically update the values of the conditional formatting fields for every item in the table (in the context of the owner of the table and the context of the partners using this table).

Conditional Formatting Field

A conditional formatting field has the following properties:
- A title
- Multiple localized title
- A description
- Multiple localized description
- A set of metadata
- A default status
- A list of statuses

Conditional Formatting Field Creation and Update

The creation and update of conditional formatting fields are only done using the table import task; table-import-schema.
To date, it is not possible to create or update conditional formatting fields using the API or the app.product-live.com application.

Conditional Formatting Field Lifecycle

Deleting a conditional formatting field is not allowed.
A conditional formatting field may be archived (and alternatively unarchived).
- Archiving a specific conditional formatting field is only possible using the table-import-schema task.
  - In INCREMENTAL mode
    - A conditional formatting field may be archived by adding status=ARCHIVED attributes to the targeted conditional formatting field. Only the key of a conditional formatting field is needed to archive it
  - In EXHAUSTIVE mode
    - A conditional formatting field may be archived by omitting it in the table schema.
    - A conditional formatting field may be archived by adding status=ARCHIVED attributes to the targeted conditional formatting field. Only the key of a conditional formatting field is needed to archive it

An archived conditional formatting field is no longer recalculated/interpreted. It always presents its default value on all the items concerned.

xml

<Conditional-Formattings>
    <Conditional-Formatting key="compliance" level="product" status="ARCHIVED" />
</Conditional-Formattings>

Conditional Formatting Field Limitations

The number of conditional formatting fields is limited to 8 per table.
The number of statuses per conditional formatting field is limited to 10.
See Technical Limits > Conditional Formatting for a more detailed description of the limitations.

Conditional Formatting Status

A conditional formatting status has the following properties:
- A title
- Multiple localized title
- A description
- Multiple localized description
- A color (one of the following: NONE, RED, ORANGE, GREEN, BLUE, BROWN, YELLOW, BLACK, PINK, PURPLE)
- A priority (an integer, higher then 1)
- A set of rules
A status on a conditional formatting field associated with a specific item may be triggered by one or many rules (within the list of rules of the status).
- For example: The status named Error is triggered by the rules Rule-Required on the field named Title
If more than one status is triggered on a given item (and a given conditional formatting field), the status with the highest priority is used.
- For example: If the status Error (with a priority of 2) and the status Warning (with a priority of 1) are triggered on the same item (and the same conditional formatting field), the status Error will be used.
One and only one status may be selected for a given item and a given conditional formatting field)
If no status is triggered on a given item (and a given conditional formatting field), the default status is used.

Conditional Formatting Status Creation and Update

The creation and update of conditional formatting statuses is only done using the table import task; table-import-schema.
To date, it is not possible to create or update conditional formatting statuses using the API or the app.product-live.com application.

Conditional Formatting Status Lifecycle

Deleting a conditional formatting status is not allowed.
A conditional formatting status may be archived (and alternatively unarchived).
- Archiving a specific conditional formatting status is only possible using the table-import-schema task.
  - In INCREMENTAL mode
    - A conditional formatting status may be archived by adding status=ARCHIVED attributes to the targeted conditional formatting status. Only the key of a conditional formatting status is needed to archive it
  - In EXHAUSTIVE mode
    - A conditional formatting status may be archived by omitting it in the table schema.
    - A conditional formatting status may be archived by adding status=ARCHIVED attributes to the targeted conditional formatting status. Only the key of a conditional formatting status is needed to archive it

An archived conditional formatting status is no longer recalculated/interpreted. It always presents its default value on all the items concerned.

xml

<Conditional-Formattings>
  <Conditional-Formatting key="compliance" level="product">
    <Title>Compliance</Title>
    <Default-Status key="valid">
        <Title>Valid</Title>
        <Color>GREEN</Color>
    </Default-Status>
    <Statuses>
      <Status key="unvalid" status="ARCHIVED" />
    </Statuses>
  </Conditional-Formatting>
</Conditional-Formattings>

WARNING

Setting a Conditional-Formatting.Status status="ARCHIVED" does not archive the Rules within it. They are still executed and visible in the grid.To completly archive a Conditional-Formatting.Status, either omit it in EXHAUSTIVE mode or archive it and each of its Rules

Conditional Formatting Status Limitations

The number of status is limited to 10 per conditional formatting field.
See Technical Limits > Conditional Formatting for a more detailed description of the limitations.

Conditional Formatting Rule

Conditional Formatting Rule Key Concepts

A rule within an archived conditional formatting field or status is no longer interpreted.
An archived rule within an active conditional formatting field or status is no longer interpreted.

Conditional Formatting Rule Creation and Update

The creation and update of conditional formatting statuses is only done using the table import task; table-import-schema.
To date, it is not possible to create or update conditional formatting statuses using the API or the app.product-live.com application.

Conditional Formatting Rule Lifecycle

Deleting a conditional formatting rule is not allowed.
A conditional formatting rule may be archived (and alternatively unarchived):
- Archiving a specific conditional formatting rule is only possible using the table-import-schema task.
  - In INCREMENTAL mode
    - A conditional formatting rule may be archived by adding status=ARCHIVED attributes to the targeted conditional formatting rule. Only the key of a conditional formatting rule is needed to archive it
  - In EXHAUSTIVE mode
    - A conditional formatting rule may be archived by omitting it in the table schema.
    - A conditional formatting rule may be archived by adding status=ARCHIVED attributes to the targeted conditional formatting rule. Only the key of a conditional formatting rule is needed to archive it

An archived conditional formatting rule is no longer recalculated/interpreted. It always presents its default value on all the items concerned.

xml

<Conditional-Formattings>
  <Conditional-Formatting key="compliance" level="product">
    <Title>Compliance</Title>
    <Default-Status key="valid">
        <Title>Valid</Title>
        <Color>GREEN</Color>
    </Default-Status>
    <Statuses>
      <Status key="unvalid" />
        <Title>Unvalid</Title>
        <Color>RED</Color>
        <Priority>1</Priority>
        <Rules>
          <Common>
            <Field key="titleEn">
              <Rule-Required status="ARCHIVED" />
            </Field>
          </Common>
        </Rules>
      </Status>
    </Statuses>
  </Conditional-Formatting>
</Conditional-Formattings>

Conditional Formatting Rule Limitations

The number of rules is limited to 500 000 per conditional formatting field.
See Technical Limits > Conditional Formatting for a more detailed description of the limitations.

Conditional Formatting Rule Types

There are three types of rules:

Rules specific to a type of field (or to identifiers and classifications), for example: "the title field cannot be empty".
The "inter-field" rules are also specific to a type of field, and depend on the state of a third-party element to be evaluated, for example: "the field price including tax must be greater than the field price excluding tax".
The rule "Condition". This is a generic rule allowing to trigger a status on a given field according to conditions defined within it.

Rules specific to a type of field

Rules on identifiers

Below, the only rules available for IDENTIFIER

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current identifier is required (and should not be empty)
`MIN_LENGTH`	`<Rule-Min-Length min="3" />`	If the attribute is not empty, the attribute must be at least `x` characters long, `x` included. If the attribute is empty, the rule is ignored.
`MAX_LENGTH`	`<Rule-Max-Length max="27" />`	If the attribute is not empty, the attribute must have a maximum of `x` characters, `x` included. If the attribute is empty, the rule is ignored.
`REGEX`	`<Rule-Regex regex="^[0-9]{13}$" />`	If the attribute is non-empty, the attribute must match the regex
`BARCODE`	`<Rule-Barcode type="EAN13" />`	If the attribute is non-empty, then the attribute must match the format specified in the `type` attribute. The formats are: `EAN8`, `EAN12`, `EAN13`, `EAN14`, `EAN18`, `GTIN12`, `GTIN13`, `GTIN14`

Examples for those rules may be found here

Rules on classifications

Below, the only rules available for CLASSIFICATION

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current classification is required (and should not be empty)
`IS_LEAF`	`<Rule-Is-Leaf />`	If a category is selected, then it must be a category of type last child in the tree.
`ONLY_ACTIVE_CATEGORIES`	`<Rule-Only-Active-Categories />`	Categories such as option lists can be archived, this rule indicates that for a category to be valid, this category must be in the `ACTIVE` status.

Examples for those rules may be found here

Rules on `SINGLE-LINE-TEXT` or `LONG-TEXT` fields

Below, the only rules available for SINGLE-LINE-TEXT or LONG-TEXT fields

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current field is required (and should not be empty)
`MIN_LENGTH`	`<Rule-Min-Length min="3" />`	If the attribute is not empty, the attribute must be at least `x` characters long, `x` included.
`MAX_LENGTH`	`<Rule-Max-Length max="27" />`	If the attribute is not empty, the attribute must have a maximum of `x` characters, `x` included.
`REGEX`	`<Rule-Regex regex="^hello$" />`	If the attribute is non-empty, the attribute must match the regex
`BARCODE`	`<Rule-Barcode type="EAN13" />`	If the attribute is non-empty, then the attribute must match the format specified in the `type` attribute. The formats are: `EAN8`, `EAN12`, `EAN13`, `EAN14`, `EAN18`, `GTIN12`, `GTIN13`, `GTIN14`

Examples for those rules may be found here

Rules on the `HTML-TEXT` field

Below, the only rules available for the HTML-TEXT field

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current field is required (and should not be empty)
`MIN_LENGTH`	`<Rule-Min-Length min="3" />`	If the attribute is not empty, the attribute must be at least `x` characters long, `x` included.
`MAX_LENGTH`	`<Rule-Max-Length max="27" />`	If the attribute is not empty, the attribute must have a maximum of `x` characters, `x` included.
`REGEX`	`<Rule-Regex regex="^hello$" />`	If the attribute is non-empty, the attribute must match the regex

Examples for those rules may be found here

Rules on the `NUMBER` field

Below, the only rules available for the NUMBER field

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current field is required (and should not be empty)
`LESS_THAN`	`<Rule-Less-Than value="3" />`	If the attribute is filled in not empty, the attribute must be strictly less than `x`
`GREATED_THAN`	`<Rule-Greater-Than value="27.2" />`	If the attribute is filled in not empty, the attribute must be strictly greater than `x`
`LESS_THAN_OR_EQUAL`	`<Rule-Less-Than-Or-Equal value="3" />`	If the attribute is filled in non-empty, the attribute must be less than or equal to `x`
`GREATER_THAN_OR_EQUAL`	`<Rule-Greater-Than-Or-Equal value="27" />`	If the attribute is filled in non-empty, the attribute must be greater than or equal to `x`
`DECIMAL_PLACE`	`<Rule-Decimal-Places precision="2" />`	The number of decimal places. We must not have more precision digits after the decimal point
`NOT_EQUAL`	`<Rule-Not-Equal value="27">`	Value must be different from `x`

Examples for those rules may be found here

Rules on the `IMAGE` field

Below, the only rules available for the IMAGE field

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current field is required (and should not be empty)
`MIN_WITH_PX`	`<Rule-Min-Width-Px min="200" />`	If an image is mentioned, the width of the image must be greater than or equal to `x`
`MAX_WITH_PX`	`<Rule-Max-Width-Px max="1500" />`	If an image is mentioned, the width of the image must be lower than or equal to `x`
`MIN_HEIGHT_PX`	`<Rule-Min-Height-Px min="27" />`	If an image is mentioned, the height of the image must be higher than or equal to `x`
`MAX_HEIGHT_PX`	`<Rule-Max-Height-Px max="27" />`	If an image is mentioned, the height of the image must be lower than or equal to `x`
`MAX_SIZE_KB`	`<Rule-Max-Size-Kb max="300" />`	If an image is mentioned, the size of the image must be lower than or equal to `x` kilobytes
`EXTENSION`	`<Rule-Extension extension="jpg,png" />`	If an image is mentioned, the extension of the image must be one of the extensions specified in the `extension` attribute. The extensions are separated by a comma. This rule is case-insensitive.
`COLOR_SPACE`	`<Rule-Color-Space name="RGB" />`	If an image is mentioned, the color space of the image must be the one specified in the `name` attribute. The color spaces available are `RGB` and `CMYK`
`COLOR_PROFILE`	`<Rule-Color-Profile name="sRGB" />`	If an image is mentioned, the color profile of the image must be the one specified in the `name` attribute. The color profiles available are `SRGB` and `ADOBE_RGB`

Examples for those rules may be found here

WARNING

If the rule extension is set to jpg, both jpg and jpeg file extensions are considered as valid.

Conditional Formatting extension value	Valid file extension
`jpg`	`jpg`, `jpeg` Not case sensitive, ex : `jPEG` is valid
`png`	`png` Not case sensitive, ex : `PNG` is valid

Rules on the `ATTACHMENT` field

Below, the only rules available for the ATTACHMENT field

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current field is required (and should not be empty)
`MAX_SIZE_KB`	`<Rule-Max-Size-Kb max="300" />`	If a file is mentioned, the size of the image must be lower than or equal to `x` kilobytes
`EXTENSION`	`<Rule-Extension extension="jpg,png" />`	If a file is mentioned, the extension of the image must be one of the extensions specified in the `extension` attribute. The extensions are separated by a comma. This rule is case-sensitive.

Examples for those rules may be found here

Rules on the fields `DATE` or Field `DATE-TIME`

Below, the only rules available for the DATE or DATE-TIME field

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current field is required (and should not be empty)

Examples for those rules may be found here

Rules on the `SINGLE-SELECT` field

Below, the only rules available for the SINGLE-SELECT field

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current field is required (and should not be empty)
`ONLY_ACTIVE_OPTIONS`	`<Rule-Only-Active-Options />`	Only active options are valid (triggered only if an option is selected, empty option is considered as valid)
`MUST_BE_SELECTABLE`	`<Rule-Must-Be-Selectable />`	Only "consistent" options are valid. An option is considered to be inconsistent when it is not present in the list of selectable options (when it has been reduced by a `SET_SELECTABLE_OPTIONS` action within a formula) If the attribute is empty, the rule is ignored.

Examples for those rules may be found here

Rules on the fields `MULTIPLE-SELECT`, `MULTIPLE-SELECT-QUANTIFIED`, `MULTIPLE-SELECT-QUANTIFIED-WITH-COMMENTS`, `MULTIPLE-SELECT-WITH-COMMENTS`

Below, the only rules available for the fields MULTIPLE-SELECT, MULTIPLE-SELECT-QUANTIFIED, MULTIPLE-SELECT-QUANTIFIED-WITH-COMMENTS, MULTIPLE-SELECT-WITH-COMMENTS

Rule Unique Key	XML Representation	Description
`REQUIRED`	`<Rule-Required />`	The current field is required (and should not be empty)
`ONLY_ACTIVE_OPTIONS`	`<Rule-Only-Active-Options />`	Only active options are valid
`MIN_VALUES`	`<Rule-Min-Values min="2" />`	If the attribute is populated, at least `x` included values must be selected from the list.
`MAX_VALUES`	`<Rule-Max-Values max="15" />`	If the attribute is populated, a maximum of `x` included values should be selected from the list.

Examples for those rules may be found here

Inter-field rules

Below, we call "Source" the field which makes it possible to test that a rule is considered as true or false and "Target" the field on which this rule applies.

The rules allowing to compare `NUMBER` type fields

WARNING

Rules below only apply if the provided source and target are non-empty.

Operation	Rule Unique Key	XML Representation	Example
Target > Source	`MUST_BE_GREATER_THAN_ANOTHER_FIELD`	`<Rule-Must-Be-Greater-Than-Another-Field field="priceHT" />`	The price including tax (target) must be strictly higher than the price excluding tax (source)
Target >= Source	`MUST_BE_GREATER_THAN_OR_EQUAL_ANOTHER_FIELD`	`<Rule-Must-Be-Greater-Than-Or-Equal-Another-Field field="priceHT" />`	The price including tax (target) must be higher than or equal to the price excluding tax (source)
Target < Source	`MUST_BE_LESS_THAN_ANOTHER_FIELD`	`<Rule-Must-Be-Less-Than-Another-Field field="priceTTC" />`	The price excluding tax (target) must be strictly lower than the price including tax (source)
Target <= Source	`MUST_BE_LESS_THAN_OR_EQUAL_ANOTHER_FIELD`	`<Rule-Must-Be-Less-Than-Or-Equal-Another-Field field="priceTTC" />`	The price excluding tax (target) must be lower than or equal to the price including tax (source)
Target = Source	`MUST_BE_EQUAL`	`<Rule-Must-Be-Equal field="price" />`
Target != Source	`MUST_NOT_BE_EQUAL`	`<Rule-Must-Not-Be-Equal field="price" />`

The rules allowing to compare `DATE` or `DATE-TIME` type fields

WARNING

Rules below only apply if the provided source and target are non-empty.

Operation	Rule Unique Key	XML Representation
Target > Source	`MUST_BE_GREATER_THAN_ANOTHER_FIELD`	`<Rule-Must-Be-Greater-Than-Another-Field field="start" />`
Target >= Source	`MUST_BE_GREATER_THAN_OR_EQUAL_ANOTHER_FIELD`	`<Rule-Must-Be-Greater-Than-Or-Equal-Another-Field field="start" />`
Target < Source	`MUST_BE_LESS_THAN_ANOTHER_FIELD`	`<Rule-Must-Be-Less-Than-Another-Field field="end" />`
Target <= Source	`MUST_BE_LESS_THAN_OR_EQUAL_ANOTHER_FIELD`	`<Rule-Must-Be-Less-Than-Or-Equal-Another-Field field="end" />`

The rule allowing to declare a mandatory target if a source is not empty

WARNING

The rule below only apply if the provided source and target are non-empty.

Rule Unique Key	XML Representation	Example
`REQUIRED_IF_ANOTHER_FIELD_IS_NOT_EMPTY`	`<Rule-Required-If-Another-Field-Is-Not-Empty field="southernDepot" />`	“Qty to order 1 – south” (target) is mandatory if the attribute “South depot” (source) is filled in

The rule allowing to make a target mandatory if a certain option is selected in a option list type field

This can be applied to below field types :

SINGLE-SLECT
MULTIPLE-SELECT
MULTIPLE-SELECT-QUANTIFIED
MULTIPLE-SELECT-QUANTIFIED-WITH-COMMENTS

WARNING

The rule below only apply if the provided source and target are non-empty.

Rule Unique Key	XML Representation	Example
`REQUIRED_IF_ANOTHER_FIELD_HAS_OPTIONS`	`<Rule-Required-If-Another-Field-Has-Options field="batteryIncluded"><Option key="batteryIncluded" /></Rule>`	"Number of batteries provided" (target) mandatory when the value "Battery included" is entered in "Battery/battery included" (source).

The rules to make a target mandatory if a source has a value greater or lower than a given value

WARNING

Rules below only apply if the provided source and target are non-empty.

Operation	Rule Unique Key	XML Representation	Example
Mandatory target if source is > value	`REQUIRED_IF_ANOTHER_FIELD_IS_GREATER_THAN`	`<Rule-Required-If-Another-Field-Is-Greater-Than field="quantity" value="0" />`	The field (DARTY - Delivery date 1 – north) is mandatory if the value of the attribute "DARTY - Qty to order 1 - north" is greater than 0
Mandatory target if source is >= value	`REQUIRED_IF_ANOTHER_FIELD_IS_GREATER_THAN_OR_EQUAL`	`<Rule-Required-If-Another-Field-Is-Greater-Than-Or-Equal field="quantity" value="0" />`	The field must not be empty (because {sourceTitle} is greater than or equal to {value})
Mandatory target if source is < value	`REQUIRED_IF_ANOTHER_FIELD_IS_LESS_THAN`	`<Rule-Required-If-Another-Field-Is-Less-Than field="quantity" value="0" />`	The field must not be empty (because {sourceTitle} is less than {value})
Mandatory target if source is <= value	`REQUIRED_IF_ANOTHER_FIELD_IS_LESS_THAN _OR_EQUAL`	`<Rule-Required-If-Another-Field-Is-Less-Than-Or-Equal field="quantity" value="0" />`	The field must not be empty (because {sourceTitle} is less than or equal to {value})
Mandatory target if source is = value	`REQUIRED_IF_ANOTHER_FIELD_IS_EQUAL_TO`	`<Rule-Required-If-Another-Field-Is-Equal-To field="quantity" value="0" />`	The field must not be empty (because {sourceTitle} equals {value})

The Rule Condition

The Rule Condition is a more generic rule, allowing to define the condition that triggers it, as well as the message to display to the user. The condition used can use the following information associated with the current item:
- The values of its identifiers
- The values of its classifications
- The values of its fields
The Rule Condition uses the same condition tools as the formula feature. See the Condition documentation for more information.
The Rule Condition possesses the following caracteristics:
- A unique key (provided by the user)
- In case multiple Rule Condition with a same Conditional-Formatting/Status/Field share the same key, each definition of the Rule Condition will overwrite the previous definition.
- A set of conditions
- A title
- Multiple localized title
Examples for this rule may be found here
Deleting a Rule Condition is not allowed.
A Rule Condition may be archived (and alternatively unarchived):
- Archiving a Rule Condition is only possible using the table-import-schema task.
  - In INCREMENTAL mode
    - A Rule Condition may be archived by adding status=ARCHIVED attributes to the targeted Rule Condition. Only the key of a Rule Condition is needed to archive it
  - In EXHAUSTIVE mode
    - A Rule Condition may be archived by omitting it in the table schema.
    - A Rule Condition may be archived by adding status=ARCHIVED attributes to the targeted Rule Condition. Only the key of a Rule Condition is needed to archive it

An archived Rule Condition is no longer recalculated/interpreted. It always presents its default value on all the items concerned.

xml

<Conditional-Formattings>
  <Conditional-Formatting key="compliance" level="product">
    <Title>Compliance</Title>
    <Default-Status key="valid">
        <Title>Valid</Title>
        <Color>GREEN</Color>
    </Default-Status>
    <Statuses>
      <Status key="unvalid" />
        <Title>Unvalid</Title>
        <Color>RED</Color>
        <Priority>1</Priority>
        <Rules>
          <Common>
            <Field key="titleEn">
              <Rule-Condition key="TITLE_IS_MANDATORY" status="ARCHIVED">
            </Field>
          </Common>
        </Rules>
      </Status>
    </Statuses>
  </Conditional-Formatting>
</Conditional-Formattings>

Conditional Formatting > General Information ​

Introduction ​

Key Concepts ​

Conditional Formatting Field ​

Conditional Formatting Field Creation and Update ​

Conditional Formatting Field Lifecycle ​

Conditional Formatting Field Limitations ​

Conditional Formatting Status ​

Conditional Formatting Status Creation and Update ​

Conditional Formatting Status Lifecycle ​

Conditional Formatting Status Limitations ​

Conditional Formatting Rule ​

Conditional Formatting Rule Key Concepts ​

Conditional Formatting Rule Creation and Update ​

Conditional Formatting Rule Lifecycle ​

Conditional Formatting Rule Limitations ​

Conditional Formatting Rule Types ​

Rules specific to a type of field ​

Rules on identifiers ​

Rules on classifications ​

Rules on SINGLE-LINE-TEXT or LONG-TEXT fields ​

Rules on the HTML-TEXT field ​

Rules on the NUMBER field ​

Rules on the IMAGE field ​

Rules on the ATTACHMENT field ​

Rules on the fields DATE or Field DATE-TIME ​

Rules on the SINGLE-SELECT field ​

Rules on the fields MULTIPLE-SELECT, MULTIPLE-SELECT-QUANTIFIED, MULTIPLE-SELECT-QUANTIFIED-WITH-COMMENTS, MULTIPLE-SELECT-WITH-COMMENTS ​

Inter-field rules ​

The rules allowing to compare NUMBER type fields ​

The rules allowing to compare DATE or DATE-TIME type fields ​

The rule allowing to declare a mandatory target if a source is not empty ​

The rule allowing to make a target mandatory if a certain option is selected in a option list type field ​

The rules to make a target mandatory if a source has a value greater or lower than a given value ​

The Rule Condition ​

Conditional Formatting > General Information

Introduction

Key Concepts

Conditional Formatting Field

Conditional Formatting Field Creation and Update

Conditional Formatting Field Lifecycle

Conditional Formatting Field Limitations

Conditional Formatting Status

Conditional Formatting Status Creation and Update

Conditional Formatting Status Lifecycle

Conditional Formatting Status Limitations

Conditional Formatting Rule

Conditional Formatting Rule Key Concepts

Conditional Formatting Rule Creation and Update

Conditional Formatting Rule Lifecycle

Conditional Formatting Rule Limitations

Conditional Formatting Rule Types

Rules specific to a type of field

Rules on identifiers

Rules on classifications

Rules on `SINGLE-LINE-TEXT` or `LONG-TEXT` fields

Rules on the `HTML-TEXT` field

Rules on the `NUMBER` field

Rules on the `IMAGE` field

Rules on the `ATTACHMENT` field

Rules on the fields `DATE` or Field `DATE-TIME`

Rules on the `SINGLE-SELECT` field

Rules on the fields `MULTIPLE-SELECT`, `MULTIPLE-SELECT-QUANTIFIED`, `MULTIPLE-SELECT-QUANTIFIED-WITH-COMMENTS`, `MULTIPLE-SELECT-WITH-COMMENTS`

Inter-field rules

The rules allowing to compare `NUMBER` type fields

The rules allowing to compare `DATE` or `DATE-TIME` type fields

The rule allowing to declare a mandatory target if a source is not empty

The rule allowing to make a target mandatory if a certain option is selected in a option list type field

The rules to make a target mandatory if a source has a value greater or lower than a given value

The Rule Condition