An activity trigger is set up against an activity due date.
There could be numerous reasons for an activity becoming overdue. The assigned resource may be overloaded with work or may
be sick. Timely escalation helps in acting on time.
An activity trigger is executed when the period relative to the activity due date has passed and as soon as the activity
becomes pending or is taken. However, you can set the activity trigger to execute before the activity due date is reached. A
trigger cannot execute for an activity that is either complete or on hold. For example, you may need an alert 2 days before an
activity due date if no resource is picking up and completing the activity (which means the business process is not progressing as
it should).
Create the following triggers against the Notify Customer activity in a Loan Request process map.
Activity
Due Date
Target Firing Date
Escalation Process
Notify Customer
12.00.00 28.09.2012
-1 day
Loan Application
Notify Customer
12.00.00 28.09.2012
0 day
Loan Application
Notify Customer
12.00.00 28.09.2012
+2 days
Loan Application
If the Notify Customer activity becomes pending at 12.00.00 26.09.2006, the trigger executes on the following dates.
A
27.00.2006 at 12.00.00 - when the trigger firing target duration is -1 day
B
28.09.2006 at 12.00.00 - when the trigger firing target duration is 0 day
C
30.09.2006 at 12.00.00 - when the trigger firing target duration is +2 days
If the activity is completed after the first trigger is executed, or after 27.00.2006 at 12.00.00, triggers B and C
are not executed.
Search results
Search tips
The search returns topics that contain terms you enter. If you type more than one term, an OR is assumed, which returns topics where any of the terms are found. Enclose your search terms in quotes for exact-phrase matching.
The search also uses fuzzy matching to account for partial words (such as install and installs). The results appear in order of relevance, based on how many search terms occur per topic. Exact matches are highlighted.
To refine the search, you can use the following operators:
Type + in front of words that must be included in the search or - in front of words to exclude. (Example: user +shortcut –group finds shortcut and user shortcut, but not group or user group.)
Use * as a wildcard for missing characters. The wildcard can be used anywhere in a search term. (Example: inst* finds installation and instructions.)
Type title: at the beginning of the search phrase to look only for topic titles. (Example: title:configuration finds the topic titled “Changing the software configuration.”)
For multi-term searches, you can specify a priority for terms in your search. Follow the term with ^ and a positive number that indicates the weight given that term. A higher number indicates more weight. (Example: shortcut^10 group gives shortcut 10 times the weight as group.)
To use fuzzy searching to account for misspellings, follow the term with ~ and a positive number for the number of corrections to be made. (Example: port~1 matches fort, post, or potr, and other instances where one correction leads to a match.)
Note that operators cannot be used as search terms: + - * : ~ ^ ' "
