Hi Marco,
Like everywhere in SAP, program exits and enhancements are usually only used if no other reasonable alternatives are available.
A modelled deadline is easier. Deadline expires, the workflow proceeds down the "Latest Start missed" branch. Add your process as a step and it's done.
There are other benefits: If you perform your action as a step in a modelled deadline then it is clear from the process what happens. People expect actions of a workflow to be along the workflow path. If something is in a program exit, it is hidden away and makes troubleshooting difficult. It makes further modification more difficult.
There are some exceptions... for example if I have a very technical function with no business relevance (e.g. replicating some info), and it is implemented for several steps, then it makes no sense to clutter up the log so I would implement that as an exit.
Regards, Mike
Why program exit? Use a modelled deadline and put a step into your latest start outcome branch that does the updating. Easier and more transparent.
Hello, thank you for the reply, that was the tutorial that i was following, i succeded in creating my exit. The trouble is succeding in understand witch even is trigger when the deadline is reatched. I though it was
swfco_event_after_rule_exec but it wasn't if i use swfco_event_state_changed the exit triggered too many times.
I only want to understand if i need check an event, an workitem attribute or something else to make my exit run at the deadline.
Regards
Hello everyone,
trying to use Workflow-Exits during the Deadling-Escalation is a DEAD END, as the status of the original workitem is not changed. So there is no workitem-exit called during the missing of a deadline. I tried to figure that out for a couple of days and debugged through the RSWWDHEX and finally gave up on it, as the very only chance to enable coding there, was a BIG modification in that program.
You have to go through the modeled deadline scenario, as Mike has already suggested.
Florin
Add comment