Defining Conditions

Learn how to define conditions in Aurea CRM win.

To define a condition:

  1. Switch to the level you wish to apply the condition to.
  2. Select Data > Define Conditions from the menu and select the desired info area.

    The following dialog boxes are opened:

    Note: If the Field Selection dialog box is not displayed, click on to display it.

    You can use the icons to determine which columns are displayed in the list: (Number), (Type), (Length).

    Click on a column header to sort the list according to that criterion.

  3. Select the field you wish to define the condition for.

    The Define Search Conditions dialog box opens.

    Depending on the field type, this dialog can contain a variety of different options.

  4. Select the desired operator. Depending on the field type, various operators are available:
    • = equal
    • > greater
    • < less
    • >= greater equal
    • <= less equal
    • <> not equal
    • () included: Tests whether the comparison value is contained at any point in the field contents.
    • )( not included: Tests whether the comparison value is not contained at any point in the field contents.
  5. Select what to compare the field contents with from the Compare with drop-down list and enter the comparison value or select the target field. You have the following options:
    • Value: Enter the comparison value in the field. You can enter wildcards in the comparison value.

      Click on (Select) to select a record for the comparison if you have selected a link field. This option is only available if the target info area has a key composed of the station number plus serial number. This option is not available for generic fields.

      Double-click or click on to select one or more values for catalog, date and rep fields.

      - Multiple catalog values/reps: One criterion is added for each catalog value/rep. The criteria are linked using a logical OR.

      - Date ranges (Ctrl + click in the calendar): A criterion is added for both the start and end date. The criteria are linked using a logical AND.

      When defining a condition applied to a date field, the linked time field is also displayed, so that you can enter both a date and time in a single step.

      To enter a value for the Answer No. field in the Survey Result info area, click on or double-click in the field to open a window and select the questionnaire, question and answer.

      When applying conditions to catalog fields, you can also apply the condition to the contents of the Description and Ext. Key fields of the catalog value.

      Syntax:

      #desc|xk[,Language]*:ComparisonText

      Explanation:

      descDescription

      xkExternal key

      [,Language]The language whose value is compared (Language No. in the Language (00)info area); optional
      • If a language is specified, the system only compares values in the specified language

      • If no language is specified, the system searches the language hierarchy from bottom to top until a matching catalog value is found. The condition is then evaluated for this language.

      *An asterisk must either occur before the colon or in the comparison text.

      ComparisonTextThe comparison value, which can contain placeholders

      Example:

      #desc:Aus* returns all records where the description of the catalog value begins with "Aus".

      #xk*:1_2_3 returns all records where the external key of the catalog value matches "1_2_3" exactly

      If you wish to change the field, click on (Select Field), disable the check box next to the current field, and select a new field.

      The Field option is not available for generic fields.
      • Variable: If your administrator has defined variables dependent on the current rep or station, click on (Select variable value) to select a variable to be used as the comparison value, see Variables in the CRM.core Administrator Guide.
      • Last Change: Use this option to apply a condition to the modification date of the field. Enter a date and time.
  6. If you are defining a condition for a dependent catalog field (e.g. the Interest field in the Interest info area), you have two options:
    • Enable the Independent of parent catalog check box: You can use wildcards (? and *). For example, if you enter "ice*", all catalog values that begin with "ice" (ice hockey, ice skating etc.) meet the condition.
    • Leave the check box disabled. Select a parent and a dependent catalog value (e.g. "sport" in the Interest Group field and "ice skating" in the Interest field). The condition is met if the values in both fields correspond to the condition.
  7. The Ignore Hierarchy option is available for hierarchy code fields. For more information, see Applying Conditions to Hierarchy Codes in the CRM.core Administrator Guide.
  8. When defining conditions for date fields, you can select a date function from the Function drop-down list:

    This allows you to define conditions such as "if the date is a holiday".

  9. When defining a condition for a geocoordinates field, you can select "Distance (kilometers)" from the Function drop-down list, enter a location (using geocoordinates) as the Reference point and specify a Distance in kilometers.

    The condition returns all records that are within the defined radius of the reference point based on the geographic coordinates entered in the records.

  10. When defining a condition for a group field (array fields linked to one another) using the "(>) greater" or "(<) less" operators, enable the Exclusive option to apply the condition (linked with a logical AND) to all fields in the group.

    Example: The condition "SIC1 > 2050" is defined for the SIC1 field in the Company info area. If Exclusive is enabled, the condition "SIC1 > 2050 AND SIC2 > 2050 AND SIC3 > 2050" is applied to the record. If the Exclusive option is disabled, the condition "SIC1 > 2050 OR SIC2 > 2050 OR SIC3 > 2050" is applied to the record.

    Note: This option is only available for the operators "(>) greater" and "(<) less". Conditions using the "(<>) not equal" and ")( not included" operators are linked using a logical AND. Conditions using other operators are always linked with a logical OR. If the comparison value is empty, the behavior is reversed: <> and )( are applied to all the fields using a logical OR, all other operators using a logical AND
  11. Case sensitive: This setting is only applicable to substrings in text fields. The value entered is compared to the field contents taking into account lower and upper case characters.
    Note: This option is only displayed if your database takes upper and lower case into account when searching.
  12. Use the Variable field to
    • define conditions for date or rep fields that automatically use the current date or rep as the comparison value, see Defining Variable Conditions.
    • define conditions for a selection, report or analysis. Variable conditions can be changed upon starting the selection, report of analysis, see Variable Conditions With User Input.
    Note: Comparisons with other fields cannot be defined as variable.
  13. You can add further criteria, see Defining Conditions with Multiple Criteria.
  14. Save the conditions, see Saving, Loading and Deleting Formats.
  15. You are asked whether you wish to activate the current conditions. Confirm with Yes.

You are returned to the current info area. Only those records that meet the condition(s) are displayed.