A transition is a path used to move a record from one state to another in the workflow or can be used to assign the record to another user. A transition can include fields called Task Fields that require a user to enter some information into a record before it moves to the next step in the workflow. In some cases a transition may be a loop (a transition which keeps the record in the same state). A loop transition is used when a record simply needs to have information added to a field, but does not move to another state and / or does not move to another assignee.

Please note: The "+" icon is available for expanding the Transitions sub-sections in the Workflows section. The "-" icon is available for collapsing sub-sections.

Defining Transitions for a State

The transitions for a particular state can be managed from the Workflows section or in the Available States section.

To manage the transitions for a state in the Workflows section:

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the "+" icon to the left of the state for which you want to manage the transitions
5. Click on the Manage link to the right of Transitions. Use the steps in the sections below for adding, editing, or deleting a transition.

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the Manage link to the right of Available States
5. Click on a state in the States In Use column, then click on the Transitions button Use the steps in the sections below for adding, editing, or deleting a transition.

To add a new transition:

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the Transitions button to the left of the state for which you want to define transitions
5. Click on the Add Transition button
6. Make selections for the properties described below
7. Click OK to save the transition

Properties of Transitions

The following options will be presented when you add or modify a transition:

Transition Name
Enter a label that will be used as the name of the transition during the Task operation

Order
The order of the transition. This will determine the order in which it appears in the transitions table as well as in the list displayed during the Task operation. Transitions which have the same value specified in the order field will be listed alphabetically.

New State
The state to which the record will be routed when this transition is selected during the Task operation. For this option, you may select one of the following:

• A specific state
  Any state in the Workflow State table can be selected as the new state for a transition.

• Prompt with <State Group>
  Selecting this option will allow the user performing the Task operation to choose from a list of all states within a particular state group as the new state for the record. When selecting this option, please select a state group from the second pulldown listed after New State. Review the Defining State Groups section for information on creating a state group. In the third pulldown, select "Require Selection" if you wish to force the user to manually select a state or select "Allow Default" to allow the default (initial) value to be saved without a manual selection by the user. When "Require Selection" is chosen, the default value of the Status field will be the value entered for the option Required Selection of New State Prompt in the General Preferences section. When "Allow Default" is selected, the current state of the record will be selected by default during the task operation if the current state is part of the state group selected. Otherwise, the states in the state group will be listed in alphabetical order.

• Previous State
  This option will send the record to the most recent state the record was in prior to its current state. Tracker will examine the Record History to determine the previous state.

New Assignee
The user to whom the record will be assigned when this transition is selected during the Task operation. For this option, you may select one of the following choices listed below:

• <State Manager>
  The record will be routed to the State Manager based on the New State for this transition and the State Manager settings for the combination of form and project set in the record. State Managers can be set in the Form State Managers section.

• <Same Assignee>
  This option can be used for transitions where a record does not need to be assigned to a different user. For example, if a record simply needs to be updated by the user who is currently assigned to the record.

• Prompt with <User Group>
  This option enables you to restrict the list of possible assignees to the members of a user group. The user performing the Task operation will select the new assignee from a list of users within the User Group that you specify for this option. When selecting this option, please select a user group in the second pulldown next to New Assignee. In the third pulldown next to New Assignee, select whether the user "TBD" should be included or excluded from this user group when presented during the task operation. TBD is a built-in user that can be used as a place holder or can signify "assigned to no one". In the fourth pulldown, select "Require Selection" if you wish to force the user to manually select an assignee or select "Allow Default" to allow the default (initial) value to be saved without a manual selection by the user. When "Require Selection" is chosen, the default value of the Assigned To field will be the value entered for the option Required Selection of New Assignee Prompt in the General Preferences section. When "Allow Default" is selected, the current assignee of the record will be selected by default during the task operation if the current assignee is a member of the user group displayed. Otherwise, the users in the user group will be listed in alphabetical order.

• <Last Assignee for New State>
  When selecting this option, Tracker will examine the Record History to find the last user who was assigned to this record when it was in the state specified in the field State for this transition. For instance, if the New State is "Scheduled", Tracker will look in the record history for the record and find the last entry where this record was in the Scheduled state. The assignee listed in this entry will become the new assignee for this record. If the record has not passed through the state selected as the New State, another transition will have to be used to process that record since there is not a user who was the Last Assignee.

• Last Assignee for <State>
  When selecting this option, please select a state in the second pulldown next to New Assignee. With this option selected, Tracker will examine the Record History to find the last user who was assigned to this record when it was in the state specified in the second pulldown. For instance, if the state selected is "Scheduled", Tracker will look in the record history for the record and find the last entry where this record was in the Scheduled state. The assignee listed in this entry will become the new assignee for this record. If the record has not passed through the state selected for this option, another transition will have to be used to process that record since there is not a user who was the Last Assignee.

• <Reporter>
  This will assign the record to the original user who reported the issue according to the value of the Reported By field.

• <LoginUser>
  This will assign the record to the user performing the Task operation. An example where this option can be used is in cases where a record is assigned to another user, such as TBD, and the user needs to assign the record to his or herself using the Task operation.

• A specific user
  Any user with "Internal" selected as the user type can be selected as the new assignee for a transition. The user type is set when the user account is created in the User Management System.

History Comment

• Selecting Required for this option will require the user to enter a history comment when selecting this transition during the Task operation.
• Selecting Optional will allow the user to leave this field blank when this transition is chosen during the Task operation.
• When Do Not Display is selected here, the history comment field will not be presented to the user when this transition is chosen during the task operation. Even though the history comment is not displayed, the record history will still reflect that the task operation was performed on a record. In addition, if Do Not Display is selected and there are no task fields configured for the transition, the transition is set up for fast tasking. Up to 2000 characters can be entered into the History Comment.

Allow Attachments
Checking the box for this option and selecting the attachment type will allow the user performing the Task operation to add the chosen attachments type to the record being processed. When selecting a transition with this option enabled, the user will have the option "Add <Type> Attachment(s)" available for selection during the Task operation.

Allow Source Code Files
Checking the box for this option will allow the user performing the Task operation to add attachments to the record being processed. When selecting a transition with this option enabled, the user will have the option "Associate Source Code File(s)" available for selection during the Task operation. This option will only be available in a transition when the Source Code Control Integration is enabled in the General Preferences section.

Clone Record

• If Yes is selected for this option, Tracker will first create a copy (clone) of the record which the user selected for the Task operation (a new record will be added with all field values the same as the record that was selected), then it will perform the Task operation on the newly created record (clone). The originally selected record ("parent" of the clone) will only have its Record History updated to note that a clone was made of the record. The clone ("child" record) will also have an extra Record History entry to note that it was created as a clone of the parent. Whether or not an Email Rule (with a condition such as "change of Assignee") is triggered by this Task operation will be based on a comparison between the parent record (record being copied) and the child record (copy) after the Task operation completes (e.g. is the Assignee different for the child than for the parent). No "Add" Email Notification Rules will be triggered (to avoid getting one notification for an Add and a second one for a Task for what, to the end user, is a single Task operation). Additional general information on cloning a record is available in the Cloning a Record section of the View page help in the Users Guide.
• If Yes is selected for this option, you can also choose to have the file attachments and/or source code file associations copied from the parent record by checking the Attachments and/or Source Code Files boxes.

Task Page Instruction Message
Enter text to be displayed on the Task Fields Page. After selecting this transition in the Task operation, the user can be presented with a message at the top of the Task Fields page. Up to 1000 characters of text can be entered as way of providing the user a customized message. The Task Fields section in the Marking a Task Complete instructions shows an example of the Task Page Instruction Message. The example is the "Explain the reason for closing the ticket..." text. You can utilize format tags such as bold, italics and others as part of the instruction message. A complete list of available tags can be found here.

Visibility
Transition Visibility is the feature that allows you to limit which users and user groups can see this transition available when performing the task operation on a record. Transition Visibility can be set by modifying each transition using the Make Visible to These Users property or by modifying each user group. If you prefer to set visibility by user group, review the Transition Visibility information in the User Accounts - Groups section. For this option, you may select one of the following:

• A specific user group
  Any user group in the User Accounts section can be selected as a user group to which this transition will be visible.

• <All Users>
  Selecting this option will make the transition visible to all users (all members of the Users and RestrictedUsers groups).

• <Assignee>
  Selecting this option will make this transition visible to the user currently selected in the Assigned To field of the record.

• <State Manager>
  Selecting this option will make this transition available to the user selected in the State Manager settings for the combination of Form and Project currently set in the record.

• <Reporter>
  Selecting this option will make this transition visible to the user listed in the Reported By field of the record.

Fast Tasking
Fast Tasking is the process where a transition is chosen and the user clicks on the OK button, the record will immediately be updated because it is set such that there are no task fields and the history comment should not be displayed. If a transition is configured to allow fast tasking and is configured to display alert settings during the task operation, the alert settings will not be displayed during the task operation. The default alert settings for the transition will be used instead.

Transitions can either be edited from the Workflows section or the Available States section.

To edit the transitions for a state in the Workflows section:

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the "+" icon to the left of the state for which you want to edit the transitions
5. Click on the Edit link to the right of the transition you wish to edit
6. Make any desired changes to the properties of the transition
7. Click OK to save the changes

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the Manage link to the right of Available States
5. Click on a state in the States In Use column, then click on the Transitions button
6. Click on the Edit button to the left of the transition you wish to modify
7. Make any desired changes to the properties of the transition
8. Click OK to save the changes

Transitions can either be deleted from the Workflows section or the Available States section.

To delete the transitions for a state in the Workflows section:

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the "+" icon to the left of the state for which you want to edit the transitions
5. Click on the Manage link to the right of Transitions
6. Click on the Delete button to the left of the transition you wish to remove, then click OK to confirm the operation

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the Manage link to the right of Available States
5. Click on a state in the States In Use column, then click on the Transitions button
6. Click on the Delete button to the left of the transition you wish to remove, then click OK to confirm the operation

Defining Fields For the Task Operation

For each transition within a particular state, you can specify which fields should be presented to the user during the Task operation. By only presenting the user with the necessary fields, you can ensure each user will correctly adhere to the workflow process.

Task fields for a transition can be managed from the Workflows section or the Available States section.

Some system-required fields cannot be added as a task field using these following steps:

Assignee
Whether this field is available during the Task operation is controlled by the New Assignee option for the transition

Last Updated Date
This field is automatically updated when the Task operation is performed on a record. This field cannot be added as a task field.

Status
Whether this field is available during the Task operation is controlled by the New State option for the transition

To add Task Fields to a transition from the Workflows section:

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the "+" icon to the left of the appropriate state
5. Click on the "+" icon to the left of the appropriate transition
6. Click on the Manage link to the right of Task Fields
7. Click on a field in the Available Fields column, then click on the Add button
8. The task field properties will be displayed at the bottom. Make selections for these properties, then click on the Update button to save your selections
9. Click on the OK button to return to the Transition list

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the Manage link to the right of Available States
5. Click on a state in the States In Use column
6. Click on the Transitions button
7. Click on the Task Fields button to the left of the appropriate transition
8. Click on a field in the Available Fields column, then click on the Add button
9. The task field properties will be displayed at the bottom. Make selections for these properties, then click on the Update button to save your selections
10. Click on the OK button to return to the Transition list

Task field properties can be edited from the Workflows section or the Available States section.

To edit the properties of a Task Field in a transition from the Workflows section:

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the "+" icon to the left of the appropriate state
5. Click on the "+" icon to the left of the appropriate transition
6. Click on the Manage link to the right of Task Fields
7. Click on the field in the Fields Used In This Transition column, then click on the Edit button
8. Make changes to the properties for the field when it is presented during the Task operation
9. Click on the Update button to save your selections
10. Click on the OK button to return to the Transition list

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the Manage link to the right of Available States
5. Click on a state in the States In Use column
6. Click on the Transitions button
7. Click on the Task Fields button to the left of the appropriate transition
8. Click on a field in the Fields Used In This Transition column, then click on the Edit button
9. Make changes to the properties for the field when it is presented during the Task operation
10. Click on the Update button to save your selections
11. Click on the OK button to return to the Transition list

Task fields can be removed from a transition either from the Workflows section or the Available States section

To remove Task Fields to a transition from the Workflows section:

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the "+" icon to the left of the appropriate state
5. Click on the "+" icon to the left of the appropriate transition
6. Click on the Manage link to the right of Task Fields
7. Click on a field in the Fields Used In This Transition column, then click on the Remove button
8. Click on the OK button to return to the Transition list

1. Login to the workgroup as Admin
2. Click on the Admin icon
3. Click on the Workflows link
4. Click on the Manage link to the right of Available States
5. Click on a state in the States In Use column
6. Click on the Transitions button
7. Click on the Task Fields button to the left of the appropriate transition
8. Click on a field in the Fields Used In This Transition column, then click on the Remove button
9. Click on the OK button to return to the Transition list

Properties for Task Fields

The following properties can be set for Task Fields when they are presented during the Task operation. Review the Examples section for suggestions for how to set the properties based on the type of task field.

Field Order
The order in which the Task Field will appear on the page during the Task operation relative to the other task fields configured for the same transition. By default, the order will be the order value as listed in the Fields section. Select an integer value. If multiple task fields have the same value for the order field, the task fields will be listed in alphabetical order.

Input Type
Specifies whether the field is required, optional, or read only when it appears during the Task operation.

• Required indicates that a user will not be able to complete the Task operation until the field is changed from its default value or Initial Value, if applicable. For Integer, Float, Link, Text, TextArea, or Date types this means that a blank value will not be allowed. For Pulldown fields, this means that the user must select a value other than the field's default value (the value configured as the Add Default) or Initial Value. For Release Number fields, this means that the user must select a value other than the default value or Initial Value in each digit (the value configured as the Add Default). For YesNo fields, this means that the user must select a value other than the default value set for the field in the Field Properties or Initial Value. If the field already has a value that is not the default (it's not blank or not set to the Add Default) and it's not being initialized, the user will not be forced to change the field during the Task operation.
• Optional indicates that the user is not required to enter information into the field to complete the Task operation
• Read Only indicates that the contents of the field will be displayed for the user's reference, but the field cannot be modified.
• Invisible indicates that the field will not be displayed for the user to see during the Task operation and it will be Initialized (Reset). When a field is initialized, it is reset to its default value. For all field types, initializing removes any previous values entered/selected in the field. For fields where an Initial Value can be set and such a value is configured, the field will be set to the Initial Value specified when it is initialized. See the explanation of the Initialize property for full details. "Invisible" is not available as a selection for Link or Reporter fields.

You may wish to highlight required fields during the Task operation with a particular color, bold type or with a special character (e.g. "*"). This can be done by configuring the Required Field Highlights option in the General Preferences section.

Initialize (Reset)
For Date fields, this property specifies whether the field should be automatically initialized with an Initial Value when the Task operation is performed. You may wish to use a combination of setting the Input Type to "Read Only" and Initialize (Reset) to "Yes" for date fields. This combination will allow the date field to be set to the current date and time when the Task operation is performed, but the user will not be allowed to modify the date field.

For Text, TextArea, URL, Integer, and Float fields, this property specifies whether the field should be reset to blank or an Initial Value. By setting the Initialize (Reset) property to "Yes" and setting the Type property to "Required", you can force a new value to be entered for a Text, TextArea, URL, Integer, or Float field. This property can be useful in combination with the Clone Record option in a Transition as you may find that you would like several fields to be reset when creating a copy (clone) of an existing record.

Note 1: For Float and Integer fields, if you set the Initialize (Reset) property to "Yes" and the Type property to "Read Only", the field value will be set to the Initial Value configured (0.0 for Float and 0 for Integer) because Float and Integer fields must always have a value (blank is not a valid value for Float or Integer).
Note 2: For all field types, if you set the Initialize (Reset) property to "Yes" the existing value (if any) of the field will be overwritten. Any data previously entered in the field will be lost.

For Pulldown fields, setting the Initialize (Reset) property to "Yes" indicates that the field should be reset to the value selected in the Initial Value field (its default value or another menu item). By setting the Initialize (Reset) property to "Yes" and setting the Type property to "Required", you can force a user to select a value other than the default or the Initial Value.

For Dependent Pulldown fields, if the parent pulldown is set to be initialized, the parent pulldown will be set to whatever was selected for the Initial Value property as long as it is a valid value according to the dependencies configured in the Item Dependencies section. Likewise for a child pulldown, If the child pulldown is set to be initialized, the child pulldown will be set to whatever was selected for the Initial Value property as long as it is a valid value according to the dependencies configured. In either case (parent or child being initialized), if the Initial Value is not a valid value according to the dependency configuration, the field will be set to the default value that is valid. In the case where the parent field is being initialized, the value of any child pulldown menus may be reset to a default value so that it matches the dependency configuration. For example, let's say a field called "Product" is parent to the "Component" field. When you select the product "Printer", the related components are "Paper Tray" and "Toner" (Paper Tray is the default). When you select the product "Monitor", the related component is "Power Cord". Let's say you set a transition such that the Product field will be initialized with the Initial Value of "Printer". If you use this transition on a record where Product is set to "Monitor" and Component is set to "Power Cord", the Product field will be set to "Printer" and the Component field will be set to "Paper Tray". The value of the Component field will be reset to a value that matches the Product field whether or not the Component field is a task field in that transition. This occurs because Component is a child of the Product field and the values in both fields must match what is configured in the dependencies section.

For RelNum fields, this property specifies whether each component of the field should be set to the value configured in the Initial Value field (its default value or another value).

For YesNo fields, this property specifies whether the field should be set to the Initial Valie configured (its default value or the other value).

Initial Value
This option is not available for Link or Reporter fields. This option will only be available when Initialize (Reset) is set to "Yes".

The value entered will be displayed by default during the Task operation and can be changed by the user. If the field is required (Input Type is set to "Required"), the user will be prompted to change the value of the field to something other than the Initial Value. If Input Type is set to "Read Only", the Initial Value will be saved for the field and cannot be modified by the user. For Date, Text, TextArea and Url fields that are set as "Read Only" and the Initial Value is blank, the following note will be displayed next to the field during the Task operation: "Note: This field will be set to blank (empty)." If the Input Type is set to "Invisible", the Initial Value will be saved for the field and will not be shown to the user during the Task operation.

For Date fields, the Initial Value can be set to "<Now>", "<Blank>" (indicating "null" or empty) or can be set to a time relative to the value in a date field. You can enter a number from 1-99, select the time interval (hour(s), day(s), week(s), month(s)), select "before" or "after" and a date field as the point of reference for the initial value. If Input Type is set to "Required", only the "<Now>" and "<Blank>" options are available. If the Initial Value is set based on a date field and the date field is not available in all of the forms used by the transition, the field will be initialized with the current date and time during the Task operation for the forms where the based on date field is not available.

If the field is visible during the Task operation (Input Type is not "Invisible") and Initial Value is "<Now>", the field will be initialized with the current date and time when the date field is displayed on the Task Page. If the field is not visible during the Task operation and the Initial Value is "<Now>", the field will be initialized with the current date and time when the OK button is clicked to complete the Task operation.

Example 1: By selecting "<Now>", the date field will be initialized with the current date and time when the user is performing the Task operation. For instance, when something is Fixed or Closed, you may have a "Fix Date" or "Close Date" field that you want initialized with the date and time when the user performed the Task operation to mark the record "Fixed" or "Closed".
Example 2: By selecting "<Blank>", the date field will be reset so that it does not have a value ("null" or empty). For instance, let's say a Close Date is set when a record is closed. If a record gets re-opened, you may want to set the Close Date to "<Blank>" (since it's being re-opened, the old Close Date no longer applies).
Example 3: By selecting "2 weeks after Date Reported", the date field will be initialized with a date that is 2 weeks after the date in the "Date Reported" field for the record. This can be used when there are deadlines. For instance, you may have a field "Estimated Close Date" which is a ballpark estimate when something will be closed. You can set the Initial Value to be the general guideline for the deadline (e.g. in this example, most issues should be closed within 2 weeks).

For Float fields, an Initial Value is required and must include a decimal point (for example, "0.0") and it can be positive or negative.

For Integer fields, an Initial Value is required and must be an integer and can be positive or negative.

For Pulldown fields, any non-obsolete option menu item can be selected as the Initial Value or "<Default Pulldown Item>" can be selected to set the field to its default value. If the pulldown is involved in a dependency and the pulldown is a parent, the initial value selected may cause the values in any child pulldowns to be reset to their default value relative to the value selected in the parent field. Basically, the the child fields will be reset to values that match with the Initial Value of the parent according to how the dependencies are configured. If the pulldown is a child, the Initial Value selected may not be actually set in the field when the transition is used if it is not a valid value relative to what is selected in the parent pulldown.

For a Text field configured to collect Unregistered User Email with the "Validate User Email Address" option enabled, if an initial value is entered, it must be in the form of a standard email address.

For User Pulldown fields, the following options are available. In all cases except when <Default Pulldown Item>, a specific user or TBD are selected, if the value to be set in the user pulldown is not a valid value (e.g. the user selected is not a member of the user group associated with the pulldown), the value will be set in the field and added to the pulldown as an obsolete value.

• <Default Pulldown Item>
  This will set the field to its default value.

• <Same As Next Assignee>
  This option is only available when Input Type is set to "Invisible". This option will set the field to match the user who will be assigned to the record after completing this transition based on what is set for the New Assignee property of the transition.

• <Same As Previous Assignee>
  This option will set the field to match the user who was assigned to the record before completing this transition.

• Last Assignee for <State>
  This option will set the field to match the last user who was assigned to the record in the selected state.

• <Reporter>
  This option will set the field to match the user who reported the record.

• <Login User>
  This option will set the field to match the user performing the Task operation on the record.

• A specific user that is a member of the user group associated with the field
  A specific user that is a member of the user group assigned with the user pulldown can be selected to be set as the value of the field when the Task operation is performed.
• TBD
  TBD, a built-in user that can represent "to be determined" or "no one", can be set as the value of the field when the Task operation is performed.

For Release Number fields, any non-obsolete option menu item can be selected for each digit as the Initial Value.

For Text or Url fields, the maximum number of characters that can be entered as the Initial Value depends on what is configured for the Maximum Number of Characters property for the Text or Url field in the Fields section. Or, it can be left blank.

For TextArea fields, up to 255 characters can be entered as the Initial Value or it can be left blank.

For YesNo fields, select either "Yes" or "No" to be the Initial Value.

Instruction Text
This property only applies to Text, TextArea and Url fields and will only be available when Initialize (Reset) is set to "Yes". This property will not be available when Input Type is set to "Read Only".

You can enter text that will be displayed in the field by default as instructions for the user filling out the field during the Task operation. For Text fields, the maximum number of characters that can be entered as the Instruction Text depends on what is configured for the Maximum Number of Characters property for the field. Or, it can be left blank. For TextArea fields, up to 255 characters can be entered or it can be left blank.

Clear Instruction Text on Focus
This property only applies to Text, TextArea and Url fields and will only be available when Initialize (Reset) is set to "Yes". This property will not be available when Input Type is set to "Read Only".

Setting this option to "Yes" will remove the text entered in the Instruction Text option when the user puts their cursor on the field. Setting this option to "No" indicates that the Instruction Text should remain in the field when the user puts their cursor on it. This option cannot be set to "Yes" if no value has been entered for Instruction Text.

Annotate
This option only applies to TextArea fields and will not be available if "Read Only" was selected for the option Input Type.

This option determines whether any additions to the TextArea field will be preceded with an annotation when the field is modified during the Task operation. The annotation includes a date and time stamp when the field was modified and the User ID of the user who modified the field.

• Select "Optional" if you wish to have the annotation be included in the field only when the user clicks on the Annotate button
• Select "Automatic" if you wish to have the annotation included automatically when the field is modified. When selecting Automatic, the Annotate button will not be displayed. The annotation will be applied to the field (only if it was modified) when the user clicks on the OK button to complete the Task operation. Selecting Automatic will result in the Append option being set to "Yes" (the annotation and any new information typed into the field will be added after any existing information in the field. Existing information in the field is protected from any changes during the Task operation). Since any new information can only be appended to the field when "Automatic" is selected, any existing data in the field will not be displayed during the Task operation.

  Automatic will not be available as a selection if "Yes" was selected for the option Initialize (Reset).

• Select "Unavailable" if you do not wish to have the field annotated when it is modified

Append
This option only applies to TextArea fields and will not be available if any of the following conditions applies:

• "Read Only" was selected for the option Input Type
• "Yes" was selected for the option Initialize (Reset)
• "Automatic" was selected for the option Annotate

• Selecting "Yes" indicates that any new data added to the field should be appended to the existing data. This option preserves any existing data in the field from being modified during the Task operation. Any existing data is not displayed in the field when "Yes" is selected for this option and Show Current Text is set to "No".
• Selecting "No" indicates that the contents of the field can be modified by the user performing the Task operation. The user can add new data anywhere in the TextArea field.

Show Current Text
This option applies to TextArea Fields and will not be available if the any of the following conditions applies:

• "Read Only" was selected for the option Input Type
• "Yes" was selected for the option Initialize (Reset)
• "No" was selected for the option Append

Examples of Useful Combinations of Task Field Properties

The following are some examples of how to set the task field properties for specific situations.

Example 1 - You want to force a user to enter something into a field or select something other than the default
Set Input Type to "Required". If you also want to clear out what's already in a field (e.g. clear out existing text in a Text or TextArea field or reset a Float, Integer, History, Pulldown, Release Number, YesNo to its default value), set the Initialize (Reset) option to "Yes".

Example 2 - You want a date field to be set automatically during the Task operation
If you want to set the date field to the current date and time when the record is being processed and will not allow the user to change its value, set Input Type to "Read Only", Initialize (Reset) to "Yes", and Initial Value to "Now".

Or, if you want to set the date field to be a date and time relative to the current date and time when the record is being processed (e.g. 2 weeks from now, 1 day before the date in the Estimated Close Date field), set Input Type to "Read Only", Initialize (Reset) to "Yes", and set "Initial Value" to be the relative date of your choice.

Or, if you want to set the date field automatically without displaying it to the user, set Input Type to "Invisible" and set "Initial Value" as desired.

Example 3 - You want to set a field with a particular value, but not show it to the user
Set the Input Type to "Invisible" and set the Initial Value to be the desired value.

Example 4 - You want to protect the text that's already entered into a TextArea field while still allowing a user to add new information
If you want to protect the text that already in a TextArea field, set Initialize (Reset) to "No" and set Append to "Yes". You can set the Show Current Text option to "Yes" to allow the user to see what's already in the field without allowing them to alter the existing text. If you want the new information added to the field to be annotated with the user's name and the date and time the information was added, set the Annotate option to "Automatic".

Example 5 - You want to want to enter some sample text into a field to give the users a hint about what to enter into the field
Set Input Type to "Optional" or "Required", set Initialize (Reset) to "Yes" (NOTE: this will clear out anything that already in the field) and type in the sample text into the Instruction Text option. Decide whether you want the sample text to be cleared out when the user put their cursor in the field by setting the Clear Instruction on Focus option.

Alerts are email notification messages that can be sent automatically by Tracker at a later date and time to remind a user or group about a record (e.g. send an alert a day before a deadline date in the record passes) or to notify people about a lack of change of status (e.g. record should be processed within a certain time threshold, send an alert if this is not done). Alert settings can be configured for each transition such that these settings will be applied to any record processed with the transition. It is also possible to allow users to be prompted to configure the Alert settings during the Task operation.

To configure default alert settings for a transition:

1. Login to the workgroup as Admin
2. Click on the Admin icon in the top button bar
3. Click on the Workflows link
4. Select the desired workflow in the Workflows pulldown at the top. The page will be refreshed with the properties of the selected workflow.
5. Click on the "+" icon to the left of the state which contains the desired transition
6. Click on the Manage link to the right of Transitions
7. Click on the Alerts button for the desired transition
8. Make selections for the fields described below, then click OK save the changes
   
   • Set Alert
     Selecting "Yes" indicates an alert should be generated for a record that has been tasked using this transition and using the alerts settings below. By selecting this option, the user will not be prompted to Set the Alert Settings when selecting this transition. Selecting "No" indicates that no alert should be sent when this transition is selected for a record. Selecting "Leave Current Values" indicates that an alert should be generated for a record that has been tasked using this transition, but the existing alert settings in the record should be used instead of the settings for this transition. The existing alert settings are those that were set during the Add operation or by the transition selected the last time a task operation was performed on the record.
   • Send Alert
     The period of time that should pass before the alert is sent. You can enter a number from 1 - 99, select the interval (hour, day, week, or month), select "before" or "after" as the point of reference for the alert, and a starting point for the time period. The starting point can be "<Now>", or can be based on any of the date fields in the record. Example 1: By entering "1 day after <Now>", the alert will be sent 1 day after the record is added. Example 2: By entering "1 day before <Date Field>", the alert will be sent 1 day before the date entered in the date field selected.

     If a date field is selected as the date to generate an alert and this date field has no value in a record, an alert will not be generated. If a date field is selected as the date to generate an alert and this date field is later removed from the record (deleted in the Fields section, then <Task Date> will be set as the date to generate an alert (to replace the date field that was removed).

   • Repeat options
     Check the box to allow the alert to be sent multiple times after the initial time period (in Send Alert field above) has passed. Select the repeat period by entering a number from 1 - 99 and the interval (hour, day, week, month). Then, select how many times the alert should be repeated. Select either Stop after X alerts where X is a number from 1 - 10 or Repeat forever. Repeat forever will continue to repeat the alert periodically until the state of the record is changed.
   • Send Alerts To
     Click on the groups and / or users who should receive the alert message if the record's state has not changed when the configured time period has passed. To select multiple users and / or groups, hold down the Ctrl button on your keyboard while clicking on each user and group you would like to select.
   • Show Alert settings during the Task operation
     Selecting Yes indicates that the user should be prompted to select alert settings when this transition is selected during the Task operation. If a transition is configured for "fast-tasking" (the transition has no task fields and history comment is set to "do not display"), then the alert settings will not be displayed during the Task operation.
   • Groups / Users that can edit alert settings during the Task operation
     Click on the groups and / or users that should be allowed to edit the alert settings during the Task operation when selecting this transition. To select multiple users and / or groups, hold down the Ctrl button on your keyboard while clicking on each user and group you would like to select.
9. After clicking OK to save the changes, click on the Alerts button for another transition to configure the default alerts settings.

Viewing and Editing Alert Settings during the Task Operation

When the task operation is performed on a record, the user may be prompted to configure alert settings depending on the default alert settings for the transition selected (setting the default alert settings for a transition are defined in the Configure Default Alert Settings per Transition section above.

In order for the user to view the alert settings when performing the task operation for a record, the transition selected must have Show Alert Settings during Task Operation set to "Yes" and the user must be a member of a group with the View Alerts Settings user group privilege. After selecting a transition during the task operation, the user meeting the criteria mentioned above will be able to see the alert settings section, but cannot modify the values. The Additional Information field can be modified to add a note or other information to be included in the alert notification message. Click OK to complete the Task operation.

For a user to edit the alert settings during the Task operation, the transition selected must have Show Alert Settings during Task Operation set to "Yes" and the user (or a group of which the user is a member) must be specified in Groups / Users that can edit Alert Settings during the Task Operation. After selecting a transition, the user meeting the criteria mentioned above will see the alert settings section. The user can modify the following alert settings. By default, the values displayed here will be the values selected in the default Alert settings for the transition selected.