Creating or changing standard strategy conditions

For details on how the Strategy Condition screen works, see Menu 10.3.25 - Account Strategy.

To create or change standard strategy conditions:

  1. From the Master menu, navigate to ClosedManagement Strategy > Work Strategies > Account Strategy (menu 10.3.25).

  2. In the Account Flow Manager window, select Strategy Conditions, and press Enter or click Ok.
  3. If you have incomplete strategies, the Strategy Test Conditions window displays and includes a list of your incomplete strategies. Select Enter Strategy ID, and press Enter or click Ok.
  4. In the Enter Strategy ID (?,/P) window, do one of the following, and press Enter or click Ok:

    When creating or renaming a strategy, we recommend that you name it with a meaningful title to help others understand what the strategy does. Also, we recommend that you do not use spaces in the name.

  5. In Desc(?) field of the Strategy Conditions screen, type a descriptive name for the strategy, and press Enter.

    The information in this field displays in other areas of AFM to describe what this strategy does. This field also allows you to set specific options for this strategy. For more information, see Configuring strategy options.

  6. In the Type field, do one of the following to indicate the type of accounts a strategy is designed to work with, and press Enter:
    • For trust accounts, type T.
    • For precollect accounts, type P.
  7. In the Control field, do one of the following to specify how the system handles packeted accounts, and press Enter:

    • To evaluate the new account according to its own record without regard to any other packet member, type I (for Independent).
    • To start the account that the primary packet is on, type P (for primary packet).
    • To start the account on the same strategy as the primary packet member, type A (for any packet member).

    If there is no packet member on a strategy, then the system treats the account as if it has an "I" (for Independent) in the field.

  8. In the Restrict field, to restrict specific user logins from starting or stopping this strategy, type Y, and press Enter.

    Use this field as a flag rather than completely removing all strategies from a role profile.

  9. In the Data Field, add one of the following for AFM to test:

  10. In the Value/Field field, type the logical operator and the value or expression to compare to the item you entered in the Data Field field, and press Enter.

    If the value to compare against is also a location value (i.e. D23, C16), the Value/Field must be enclosed in quotes. For example, to compare a desk that uses a reserved letter (i.e. C16), type "C16".

    A logical operator indicates the type of comparison or test to make. If you do not type a logical operator, by default the system inserts the equal to (=) operator. The following table includes a list of operators to use:

    Operator

    Description

    =

    Equal to

    #

    Not equal to

    >

    Greater than

    <

    Less than

    >= or =>

    Greater than or equal to

    <= or =<

    Less than or equal to

    For example, to select all accounts that have an assigned amount over $1000, in the Data Field, type $1, and in the Value/Field field, type >1000.

  11. Before entering the strategy action in the 1st Action field, to add another test condition that the account must meet before the action is applied by the system, press Enter until the cursor moves to the Data Field field of the next line. Repeat Steps 9-11 until you add all of the AND conditions.

    For example, to select all accounts that have an assigned amount of over $1000 and have an address in Arizona, in the Data Field field of the first test line, type $1, and in the Value/Field field, type >1000. Instead of entering an action in the 1st Action field, press Enter until the cursor moves to the second test line. Instead of displaying OR IF to designate another separate condition, the system displays AND to mean that both the conditions in the first and second line must be met for the action(s) to occur.

    The example below selects accounts which have a cell phone as a home number that has been marked as "BAD". In the first line of the Data Field field, select the Debtor file and then D8.C to use contacts fields for the home phone. Select field CT5, which is the phone's sub-type. To check that this is a cell phone, in the Value/Field field, type =CELL. Press Enter until the cursor is on the next line of the Data Field. Select Debtor and then D8.C, and use contact field CT4 to test for a phone status that is =BAD. After setting the test conditions, an action can be assigned.

  12. In the 1st Action field, do one of the following to enter the strategy action to take if the account meets the condition:

  13. In the Event field, do one of the following to specify the event that triggers an action:

  14. In the 2nd Action field, do one of the following to indicate what, if any, secondary action should occur when the event listed in the Event field occurs:

  15. In the Next Strategy field, do one of the following to indicate which, if any, strategies to run on an account after the current strategy is complete:

  16. In the Data Field field of line 2, do one of the following:

    • To add more conditions to the strategy, proceed with Step 9-15.
    • To save the strategy, type #, and press Enter.
      • At the OK to file strategy name? prompt, click Yes.

    Though a message does not display, The Collector System saves your changes to the strategy.