AllanGray, General Electric, True


Use Case 1: Business Process that has a Logout Step in it, used to fail with a Logout-Timeout transaction and "OR" behavior on Step filters wasn't allowed. All this is now history! Whenever the key name is the same, multiple values can be specified on a filter.

Use Case 2:  we want to create a BP step on a new SR creation which can occur on multiple web pages. We would like to configure a step filter as = 'Service Request % ' and that would cover all use cases...before this enhancement we could constraint only to a specific web page(e.g. Service Request123)