on ‎2017 Feb 10 9:34 AM
I want to extend an existing (and working) start condition with a functional method of a custom BOR object. However, it seems that the functional method is not evaluated when the event is triggered, so the workflow is started even if conditions aren't met.
The workflow is started with event FIPP-ASSIGNED (available through delegation from custom BOR object ZOKU_FIPP). The existing start condition checks for the company code. I added a new functional method to it.

The functional method is defined as a synchronous method with some ABAP for additional checks.

I have tested that the start condition works fine when I test it in the condition editor with proper test data.

I have also tested using the corresponding functional method as a separate step in the workflow. It is called and works correctly then. However, I checked with debugging (an eternal loop + SM50) that the functional method is not called from the start condition when the event is triggered.
What am I missing?
Request clarification before answering.
This post also gave me the idea to create a suitable check function module. Still, I'd rather not do that, as I'd need to incorporate the existing company code checks as well. The start conditions should be a flexible tool for adding rules, and it's more transparent to superusers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 15 | |
| 9 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.