new

Click to create a new rule.

Go to Rules folder

Click to open the Rules folder for the selected object in the Documents area, where all files for custom action and scheduled action rules are stored.

Show Rules

Select a rule type by which to filter the list.

on action.

Select an action (trigger) by which to filter the list.

Note: The contents of this drop-down list varies according to the rule type you have selected. For a list of rule triggers, see the Rule Triggers table.

Rule list

Displays all rules that have been created for the selected object that meet your view criteria.

Order

Displays the order in which rules are executed when a user attempts the corresponding action. Rules are executed in order from lowest to highest.

The order only pertains to rules of the same type. For example, all security rules are executed first according to order. After all security rules are executed, validation rules are executed according to order, and so on, according to the rule type.

For details on execution order, see Points To Remember.

Rule

Displays the name of the rule as a hyperlink, which you may click to view the rule definition.

Trigger(s)

Displays the names of the triggers that are currently associated with the rule. For a list of rule triggers, see the Rule Triggers table.

Active?

Displays whether the rule is currently active in TeamConnect. 

From TCE v7.2, users can filter rules by their status using the “Active?” dropdown options:

1. Any: Includes both Active and Inactive status types.
2. Yes: Shows only Active status types.
3. No: Displays only Inactive status types.

This Rule is Active

Select to activate the rule after you have finished developing it and you are ready to test it or make it available for users.

Important: When designing rules, you must always deactivate rules you have not completed or are not using. Having active rules may hinder your ability to design and test other rules.

Name

Enter a name that clearly and uniquely identifies the rule. This field cannot exceed 250 characters.

Tip: Avoid similar descriptions for different rules. Emphasize important information, such as the rule trigger, in the description such as the following example:

When a dispute is closed it cannot be deleted

If this rule is an approval rule, this description appears on the Workflow tab of a record that is pending approval for an operation. This helps users to understand why the operation is being sent for approval.

Unique Key

Enter an alphanumeric combination to uniquely identify the rule within the object definition. After you save the rule, the unique code appears as read- only text and you cannot change it.

The unique key cannot contain spaces, underscores, commas, punctuation marks, or any special characters and must not exceed 50 characters in length.

Although rules within the same object definition cannot have the same unique key, rules belonging to different object definitions may have the same key.

Order

Enter an integer to indicate the order in which the rule must take effect in relation to other rules that are created for the selected object.

Organize your rules in the order of their importance in your system, with the most important rule being executed first.

Type

Select the radio button next to the type of rule you want to create. For an explanation of each type of rule, see Rule Types.

Important: After the rule is saved, you cannot change this selection.

Triggering Event

Select the events, or operations attempted by the user, that you want to trigger the rule. Multiple events can be selected.

Note: The checkboxes available vary according to the rule type you select.

For details, see Rule Triggers.

Use Automated Qualifier file

Select this option to use a Java class or JavaScript file as the rule's qualifier. When this option is selected, the screen displays a drop- down list labeled Use this Automated Qualifier, where you may select the appropriate Java or JavaScript rule qualifier. For details about automated qualifiers, see Writing Automated Qualifiers for Rules.

Use Qualifier defined below

Select this option if you want to use the user interface to define the qualifier conditions and logic.

Left Argument

Allows you to create a path to the attribute that you want to use in the qualifier condition.

Select whether you want to create a path to an attribute that is associated with the Current Object or the Current User:

• Select Current Object if you want to use a field in TeamConnect as a qualifier (for example, the Current Phase of the record that the user is attempting to update).
• Select Current User if you want the rule to check the identity of the current user working with a record (for example, to verify that the user who is attempting the operation is a member of a specified group).

Click the Navigator icon to open Object Navigator, the tool for creating paths in TeamConnect, and edit the path displayed in the Attribute field, if appropriate. To create a path, you must understand the object model as described in Object Model: Read This First and in the additional tables it points to.

Important: It is recommended to use "approvalStatus.statusIID" as the path for approval status rather than "approvalStatus", as using only the "approvalStatus" will show duplicated statuses in the Right Argument.

reset

Clears the path that appears in the Object Navigator field. This button appears after an option has been selected from the drop-down list in the Left Argument.

Operator

Select the appropriate operator settings for the qualifier condition. For details, see Available Operators in Qualifier Items.

Right Argument

Select the attribute, literal value, or other setting that you want to compare to the attribute that you selected for the left argument. For details, see Right Argument Options in Qualifier Items.

Qualifier Item List

Displays a list of qualifier items that have been added to the rule. These are the conditions used by the rule, in combination with the logic that you specify, to determine whether to prevent the operation that is being attempted, or whether the rule's action must be run.

Select or clear the corresponding check-boxes to edit or delete qualifier items.

Run the rule action when

Select how you want the defined qualifier items to be evaluated by the rule. For details, see Qualifier Logic.

The value selected in the Loss Type list field

is

Fire Damage

The current user

is not

a member of the Outside Counsel group

The Trial Date

is changed

from any date to any date

The Expiration Date field

is populated

[none]

Run the rule action when

Specify when the rule action must be run based on the qualifiers. You may specify AND or OR logic, or a formula using the qualifiers. See Qualifier Logic.

View Qualifier/Hide Qualifier

Click to view or hide the qualifier logic display.

formula

Click this hyperlink to view additional help on how to write the formula for a rule qualifier.

Qualifier

Displays a visual representation of your entire rule qualifier according to the formula that you have provided.

You cannot edit the qualifier in this area. It is provided to help you determine whether the formula you have written is correct.

Any object

Checks whether the current user who is attempting the operation is a member of the Paralegals group.

1. Current User
2. Click the Object Navigator icon
3. groupMemberList-> (traverse)
4. group-> (ok)

5. Is
6. Equal To

7. Literal
8. Paralegals

Any object

Checks whether the current user is Bob Johnson.

1. Current User

2. Is
3. Equal To

4. Literal
5. Bob Johnson

Any object

Checks whether the current user is the same user who created the record.

1. Current User

2. Is
3. Equal To

4. Attribute
5. Current Object
6. Click the Object Navigator icon
7. createdBy-> (ok)

Contact- centric custom object

Checks whether the contact selected in the contact-centric field of the project (such as the Insured) is the contact selected in a custom field of type Involved (such as Requestor).

1. Current Object
2. Click the Object Navigator icon
3. contact-> (ok)

4. Is
5. Equal To

6. Attribute
7. Current Object
8. Click the Object Navigator icon
9. detailList-> (traverse)
10. RequestedBy- > (traverse)
11. contact-> (ok)

Any object

Checks whether the value of a custom field Trial Date has changed (for example, to trigger an audit rule).

1. Current Object
2. Click the Object Navigator icon
3. detailList-> (traverse)
4. Select the category (traverse)
5. TrialDate (ok)

6. Is
7. Changed

8. Any Value
9. Any Value

Custom object (such as a matter)

Checks whether an assignee with the role Outside Counsel has been added to the record.

1. Current Object
2. Click the Object Navigator icon
3. assigneeList-> (traverse)
4. Outside Counsel (ok)

5. Not
6. Item Added

None

Custom object (such as a matter)

Checks whether the phase is changed from some other phase to Closed-Pending.

1. Current Object
2. Click the Object Navigator icon
3. currentPhaseType -> (ok)

4. Is
5. Changed

6. From: Any Value
7. To: This Value
8. Closed- Pending

Any object

Checks whether the custom field Disposition Date has no value (is null).

1. Current Object
2. Click the Object Navigator icon
3. detailList-> (traverse)
4. Select the category (traverse)
5. Disposition Date (ok)

6. Not
7. Populated

None

Any object

Checks whether the Suit Served date is after the Suit Filed date (both custom fields).

1. Current Object
2. Click the Object Navigator icon
3. detailList-> (traverse)
4. Select the category (traverse)
5. Suit Served (ok)

6. Is
7. After

8. This Date
9. Current Object
10. Click the Object Navigator icon
11. detailList-> (traverse)
12. Select the category (traverse)
13. Suit Filed (ok)

Any object

Checks whether the Incident Date was during the last 30 days. Incident Date is a custom field.

1. Current Object
2. Click the Object Navigator icon
3. detailList-> (traverse)
4. Select the category (traverse)
5. Incident Date (ok)

6. Is
7. Within The Last X Days
8. 30

9. From Now

Any object

Checks whether the Loss Estimate is greater than or equal to 1000 dollars. Loss Estimate is a custom field.

1. Current Object
2. Click the Object Navigator icon
3. detailList-> (traverse)
4. Select the category (traverse)
5. Loss Estimate (ok)

6. Is
7. Greater Than Or Equal To

8. Literal
9. 1000

Task or Expense

Checks whether the project associated with the record is in Closed status. (This is the record status—not the phase.)

Tip: You may use this qualifier with the Post rule trigger to prevent posting to a closed project.

1. Current Object
2. Click the Object Navigator icon
3. project-> (traverse)
4. isClosed (ok)

5. Is
6. Equal To

7. Literal
8. Yes

Invoice

Checks the type of invoice, since some types may be subject to more stringent verification and approval than other types are. You may want to restrict your rule to a specific invoice type, or you may want to exclude a specific type (for example, "Not Shadow".)

1. Current Object
2. Click the Object Navigator icon
3. typeIID (ok))

4. Is
5. Not

6. Standard
7. Accrual
8. Credit Note
9. Shadow

Task or Expense

Checks whether the Current Phase of the project associated with the record is Pending.

Tip: You may use this qualifier with the Post rule trigger to prevent posting to a project when it is in an inappropriate phase for posting.

1. Current Object
2. Click the Object Navigator icon
3. project-> (traverse)
4. currentPhaseType -> (ok)

5. Is
6. Equal To

7. Literal
8. Pending

Contact

Checks whether there are any phone numbers added to the contact.

1. Current Object
2. Click the Object Navigator icon
3. phoneList-> (ok)

4. Not
5. Populated

None

Approval route

Select an existing route from the drop-down list to specify the users who must authorize the request. If this area displays (No Items to Select), then you must first create a route. For details, see Creating Routes.

Process Manager

Select a user group from the drop-down list. (You may first need to define a new group and/or add users to a group, as explained in "Account Administration" chapter of the TeamConnect Administration Guide.) The group must contain at least one active user. When you add a Process Manager, any user in that group may reassign processes, restart processes, or return requests to requestors for the following statuses:

Action on reject - Send to Process Manager (see below in this table)

Expiration action - Send to Process Manager (see below in this table)

Action on reject

Select one of the following:

• Return to requestor—This stops the approval process. The requestor will still have the option to resubmit the approval request.
• Send to first stop—If an approver at the first stop rejects the operation, the approval process will end. If an approver at the second stop or later rejects the operation, the approval will be pending for the first stop's approver. No matter where in the route the rejection took place, the request is rejected. The Workflow block of the record indicates who rejected the operation and the date and time.
• Send to Process Manager—Select to allow a Process Manager to reassign the request to a new user (non-approver), restart the approval process, or return the request to the requestor.

Action on return to requestor

This field is used when the previous field, Action on Reject, has the option "Return to Requestor" selected. If Action on Reject has a different option, the setting in this field is ignored.

Select one of the following:

• No Action—The approval is marked as rejected and it is returned to the requestor with no other action taken.
• Use template—The approval is marked as rejected and the template that is selected in the drop-down list is executed. The link Go to Templates allows you to view and manage templates, then return to this page and choose a template to be executed with this action.
• Use automated action—The approval is marked as rejected and the automated action that is selected in the drop-down list is executed. The link Go to Automated Action Folder allows you to view and manage automated actions, then return to this page and choose an automated action to be executed with this rule action.

If the same Approver is at multiple stops

Select one of the following:

• Approver approves at each assigned stop—The assigned approver must approve at all assigned stops. This is the default option.
• Approver approves once and is skipped in subsequent stops
  —Once the approver approves at the first stop, all subsequent stops where this user is an approver are marked "Approved" with comments populated. Workflow functions as if the user manually approved each of these stops.

Notes: This option only applies to actual approver action and does not apply if stop members are auto-approved via an expiration date.

Also, if a stop member approves under this option, and later, a process manager assigns the same user to a stop, the stop member must manually approve the new assignment and approval automation will not overwrite the previously-automated approval.

Use Stop-level parameters

If you select the Use Stop-level parameters option, you may define workflow approval behavior per stop.

Options available prior to approval

You may select one or more of the following for each route stop:

• Send for review—(optional) Select this option to allow the approver the option to assign reviewers to the operation before he or she approves.
• Send for additional approval—Select this option to allow the approver, before approving, to send the request to another user.
  If the new approver approves the request, the request continues to the original approver. If the new approver rejects the request, the specified Action on Reject occurs.
• Update records pending approval—If approval is pending for one or more approvers at a stop level, then any of the approvers at that level have edit rights for the tabs and fields in the record. This field is mutually exclusive with the "All users that are approvers can update" option present in the Options available upon approval section.
  • All users that are approvers can update—All users on the route will have edit rights for the tabs and fields in the record. This field is mutually exclusive with the "Update records pending approval" option present in the Options available prior to approval section.
    
    Note: This selection is only available if all users are required on the stop.

Options available upon approval

You may select the following for each route stop:

• Send for additional approval—Select this option to allow the approver, after approving, to send the request to another user.
  If the new approver approves the request, the request continues to the next stop. If the new approver rejects the request, the specified Action on Reject occurs.
  If the rule uses a route with conditions, this settings does not appear on your rule.

Approval time limit

You may set the number of days approvers in each stop have to respond.

This number is converted into exact hours. For example, entering 5 gives the approvers five days, or 120 hours, to make a decision concerning the action. So if the rule is invoked on October 15, 2008 at 3:00 pm, the approvers have until October 20, 2008 3:00 pm to approve the action.

The countdown starts when the operation is first attempted by the user.

You must use a value other than zero when specifying the length of an approval process. Otherwise, the approval period expires almost immediately.

Expiration action

You may select one of the following for each route stop:

• Send to Process Manager—Select this radio button to allow the Process Manager to reassign or reject a request after the approval time limit has passed.
• Auto-approve—Select this radio button to allow the operation to be performed after the approval time limit has passed.
• Auto-reject—Select this radio button to prevent the operation from being performed after the approval time limit has passed.

Email Actions

The Allow approval/rejection via email field is a check-box you select if you want users who receive approval requests during the stop to receive an email from which they can approve or reject the request. This setting also allows them to enter internal comments and comments to the requestor after approving or rejecting through email.

Email Template

The drop-down contains all email templates you can select as the approval request email users receive during this stop. If you do not select a template, TeamConnect uses a default email template. You can design an approval request email from the Notifications page of Admin Settings. See Notification Settings for more information.

Hold Conditions

Hold conditions allow you to ensure approvals on a certain stop are contingent on meetin predetermined stipulations. Use the Hold Condition message entry field to provide users with detail on why the approval is blocked. For more details, see Hold Conditions. Note: Feature only available in TeamConnect 4.0.8+.

Approval route

Select an existing route from the drop-down list to specify the users who must authorize the request. If this area displays (No Items to Select), then you must first create a route. For details, see Creating Routes.

Process Manager

Select a user group from the drop-down list. When you add a Process Manager, any user in that group may reassign processes, restart processes, or return requests to requestors for the following statuses:

Action on reject - Send to Process Manager (see below in this table)

Expiration action - Send to Process Manager (see below in this table)

Action on reject

Select one of the following:

• Return to requestor--Stops the approval process. The requestor will still have the option to resubmit the approval request.
• Send to first stop—If an approver at the first stop rejects the operation, the approval process ends. If an approver at the second stop or later rejects the operation, the approval will be pending for the first stop's approver(s).
• Send to Process Manager—Select to allow a Process Manager to reassign the request to a new user (non-approver), restart the approval process, or return the request to the requestor.

If the same Approver is at multiple stops

Select one of the following:

• Approver approves at each assigned stop—The assigned approver must approve at all assigned stops. This is the default option.
• Approver approves once and is skipped in subsequent stops
  —Once the approver approves at the first stop, all future stops where this user is an approver are marked "Approved" with comments populated. Workflow will function as if the user has manually approved each of these stops.

Notes: This option only applies to actual approver action and does not apply if stop members are auto-approved via an expiration date.

Also, if a stop member approves under this option, and later, a process manager assigns the same user to a stop, the stop member must manually approve the new assignment and approval automation will not overwrite the previously-automated approval.

Use Route-level parameters

This option applies a general set of workflow approval settings across all stops for the selected route. See more details below.

Options available prior to approval

You may select the following for the route:

• Send for review—(Optional) If you select Use Route-level parameters, you may select this option to allow the approver the option to assign reviewers to the operation before the approver approves.
• Send for additional approval—Select this option to allow the approver, before approving, to send the request to another user.

If the new approver approves the request, the request continues to the original approver. If the new approver rejects the request, the specified Action on Reject occurs.

Options available upon approval

You may select the following for the route:

• Send for additional approval—Select this option to allow the approver, after approving, to send the request to another user.

If the new approver approves the request, the request continues to the next stop. If the new approver rejects the request, the specified Action on Reject occurs.

If the rule uses a route with conditions, this settings does not appear on your rule.

Updates to records pending approval

If you select Use Route-level parameters, you may select one of the following:

• Not allowed. While the request is pending approval, no contacts have edit rights for the tabs and fields related to that object.
•  Allowed to approvers of current stop. The approval request is sent to all members of the group. While the request is pending approval, any approver from the current stop has update rights for the tabs and fields in the record.

Note: If the Route Stop has been set to require all members to approve, and this option is selected, the stop members will not be able to update the record.

• Allowed to anyone. While the request is pending approval, any approvers have update rights for the tabs and fields in the record.

Approval time limit

(Optional) Enter the number of days approvers have to respond.

This number is converted into exact hours. For example, entering 5 gives the approvers five days, or 120 hours, to make a decision concerning the action. So if the rule is invoked on October 15, 2001 at 3:00 pm, the approvers have until October 20, 2001 3:00 pm to approve the action.

The countdown starts when the operation is first attempted by the user. It does not reset each time a route stop is completed.

Expiration action

You may select one of the following:

• Send to Process Manager—Select to allow the Process Manager to reassign or reject a request after the approval time limit has passed. The Process Manager will have option to either restart the workflow approval process or return the request to the requestor
• Auto-approve—Allow the operation to be performed after the approval time limit has passed.
• Auto-reject—Prevent the operation from being performed after the approval time limit has passed.

Internal auto- reject comment

(Optional) If the Auto-reject option was selected above, then you may type a comment that will be displayed to the requestor, such as the reason for rejection. The maximum length is 250 characters.

Use this Automated action

Select the Java or JavaScript file that defines the action that is executed according to the schedule. This same action is executed for each repetition that you specify in these parameters.

This drop-down list contains documents that have been uploaded to Top Level/System/ObjectDefinitions/ObjectName/Rules/Automated Actions and have the document type JavaClass or JavaScriptCode.

To open the folder where Automated Action files for this object definition are stored, click Automated Actions Folder hyperlink.

Use template to send notification

Select the email notification template that is to be sent according to the schedule. This same notification template is sent for each repetition that you specify in these parameters.

Track in History

(Optional) Select whether a history record will be created every time a notification is sent out. A drop-down list appears when the Track in History check-box is selected.

From the Location drop-down list, select which level you want the history record to be saved in: Record, Object, or System. Record will not be available if the rule triggering event is Delete.

Execute

Specify when the automated action or notification is to be executed.

• Immediately—The action is executed immediately after the rule is triggered. This is the default option.
• After—The action is executed a specified period of time after the rule is triggered. Select from Minutes, Hours, Days, Weeks, Months, or Years in the drop-down list, then enter a value in the text box to specify how long after the trigger the rule will be executed.
• On Specific Date/Time—Use the fields that appear to specify the calendar date and time for the scheduled action to be executed.

Do you want the action to be repeated?

Select whether the action is repeated. If you select Yes, then additional options appear, where you specify how often and how many times the action is repeated. The default option is No.

Repeat

Specify the period of time between rule action repetitions after the initial execution after the rule has been triggered. Additional options will appear depending on the selection in the Repeat drop-down list.

• Hours and Minutes—The scheduled action will repeat after the specified number of Hours and Minutes have passed.
• Daily—The scheduled action will repeat every day. Select the Weekdays only check-box to set the rule action to be repeated only from Monday through Friday.
• Weekly—The scheduled action will repeat every week. Use the Day drop-down list to select on which day of the week the action will be repeated.
• Monthly—The scheduled action will repeat every month. Use the Day of the Month drop-down list to select on which day of the month the action will be repeated, from 1 to 31, or Last for the last day of the month.
• Yearly—The scheduled action will repeat every year. Use the Day and Month drop-down lists to select on which month and day of the year the action will be repeated.

End

Specify when the rule action repetitions will stop.

• No End Date—The scheduled action will repeat indefinitely until the rule is deleted or inactivated.
• After—The scheduled action will execute for the specified number of repetitions. This is the default option, with a value of 1.
• Until—The scheduled action will repeat until the specified date and time.

Location

Select the target location for storing the history record that is created when the audit rule is triggered.

Depending on the object that you are defining, this drop-down list may include some or all of the following options:

• Current record—For example, if you select Matter, a related history record will be created in the affected Matter record.
• Object definition—For example, if you select Matter Object Definition, a history record will be created in the Matter custom object definition.
• Parent project or projects—For example, if you select a Claim's parent project, Policy, a related history record will be created in the policy record.
• System—If you select this item, the history record will be created for the TeamConnect System user. You may access history records assigned to this location on the History tab of the System Settings screen.
  Note: History entries saved to the "System" location will also be available to pull up via the Histories Object/Page in the TeamConnect front-end available under All pages menu option on the global navigation menu (as opposed to History entries saved to the "Object Definition", which can only be seen from the TC backend Setup menu).

Use default description (i.e. "Matter record has been updated")

Select this option if you want TeamConnect to insert a default description of the event that triggers the audit rule in the history record's Description field.

The default description combines the object type, record name, and triggering event to form a description such as "Matter Simmons vs. Acme Auto Rental has been updated."

Use description defined below

Select this option if you want TeamConnect to insert a custom description of the event that triggers the audit rule in the history record's Description field.

This is the default option, and you must use the associated batch screen to define a custom description.

For more information on whether you need a default description or a custom description, see Audit Default Description.

Item Type

Select an item from this list to build the description for the history record.

Depending on the option that you select in this field, different settings appear for the Item Value:

• Object Attribute—Select this option to define an object attribute.
• Literal—Select this option to manually enter a text value.
• Line Break—Select this option to insert a carriage return in the text description.
• Character Space—Select this option to insert a space between items in the text description.

Item Value

Define a value to build the description for the history record.

• For object attributes, select Current Object or Current User, click the Navigator icon to open Object Navigator, and then select an attribute. For details, see Using Object Navigator.
• For literals, enter a custom message in the text field.

Old Value or New Value

Select Old Value or New Value for the attribute.

This drop-down list only appears if the Item Type is an object attribute. The old value refers to the attribute's value in the TeamConnect database before the record is changed and updated by an action. The new value refers to the attribute's value after the record has been updated and saved.

Tip: This may be useful in building the history record's description by capturing information that might not exist in the record after it is modified and saved.

Order

Enter an integer to indicate the Order of the item you defined to place it correctly within the entire description statement.

Item List

Displays the items that are already added to be used in the custom description.

Select the check-box of an item and click edit or delete to make changes.

Category

Select a category from this list to be automatically added to the history record.

This list shows all the categories available in the History object definition.

Make sure that you have created descriptive categories in the History object definition and defined custom fields within these categories that you plan to populate with the audit rule. For details, see Configuring History Object Definition for Audit Tracking.

If you do not select a different category, the Root category is automatically used.

After you select a category, you may use the Field Label and Field Value fields to define the content that will populate the category's custom fields.

Field Label

Select the label of the custom field that you want to use in the history record.

This drop-down list contains the labels for the custom fields in the History object definition. The values available in this list depend on the History category selected in the Category field.

These field labels appear on the Details block of the history record that is created when the rule is triggered.

This field is not available for the User and Group object definitions.

Field Value

Select Current Object or Current User, click the Navigator icon to open Object Navigator, and then select an attribute to populate the field that is identified in Field Label. For details, see Using Object Navigator.

You must select whether you want the field to be populated with the Old Value or New Value.

Make sure you have defined any necessary custom fields for the category you want to use in the History object definition.

Make sure to match the field type to the attribute type, such as matching a date field to an object attribute that stores a date value.

This field is not available for the User and Group object definitions.

An error message appears for a rule that must not be triggered in the situation you are testing.

Check for the following issues:

• Open the error messages of the rules being triggered.
• Do they have the correct messages?
• Does the rule have multiple triggers associated with it? Are those the correct triggers?

Note: You may have another rule being triggered with the same error message, especially if you used the Create Copy button to create this rule.

A rule is not being triggered.

Once you create any rules, test them to see whether modifications are needed to get a rule to trigger in the correct situations. If your rule is not being triggered, check for the following issues:

• Is the rule active?
• Did you select the correct rule type? Security and validation rules are easy to confuse.
• Is the qualifier defined correctly?
• Is the entire qualifier met?

If at least one of the qualifier conditions or the logic that you have defined is not met, the rule is not executed.

My Approval rule is not being triggered at the right time.

Check for the following issues: Is the rule active?

Is a route selected?

Does the route have members?

Note: If a group is the only stop member in the selected route and there are no active users added to the group, there is no indication that the rule was triggered, because the approval request was not sent to any users.

• Is the qualifier defined correctly?
• Is the entire qualifier met?

If at least one of the qualifier conditions or the logic that you have defined is not met, the rule is not executed.