Please do not try to download and/or contact us regarding this extension.
This function allows you to define and control in a more granular way which item should become suspect when you change an item.
The function also adds a comment to the items which becomes suspect.

Instead of using the auto suspect feature of Polarion you can now define a custom workflow action e.g. "undergoing change" which once it is executed marks a custom set of items as suspect.
Attributes which can be set
| Attribute name | Description | Example | Allowed values | Required |
| item.type | Only listed item type will become supect.If no item type is specified any item type is checked for suspect. | item.type = requirement | Any item type defined in workflow configuration. | no |
| project.id | Only items which are in the specified project will become suspect. If no project id is specified all projects are checked for suspect items. | project.id = library | Any existing project id | no |
| allowedStates | Only items which are in the specified state will become suspect. If no state is specified, any state can make the item suspect | allowedStates = open,accepted | Any state defined in the workflow configuration | no |
| current.project |
If value is true, then suspect affects only items of the current project. Do not use together with project.id as both variables are combined with AND. |
current.project=true | true | no |
| suspect.comment | Allows you to add a comment to the item which becomes suspect. The comment contains information about changed revision of the originator item and your custom comment message. | suspect.comment =" somebody changed a Work Item you are refering to. Please check content for consistency" | any String | no |
Example Scenarios
This section contains snipplets of different workflow configurations
| Function Configuration | Bahavior in Polarion |
<function name="AdvancedSuspect"> |
|
<function name="AdvancedSuspect"> |
|
