Академический Документы
Профессиональный Документы
Культура Документы
Jocelyn Dart
share 0
share 0
tweet
share 5
Follow
This is the start of a series on how to use ABAP OO with workflow.
What other reasons are there for using ABAP OO with workflow?
Ive saved the best for last because ABAP OO for workflow means: Any ABAP developer who can code
ABAP OO can (after reading this series) code for workflow. So now project managers and workflow
creators can call on any ABAP programmer to assist with custom development for workflow you
wont need a specially-trained workflow code-cutter any more.
The SELFITEM object for sending mails. This is still useful as everything, including the Send
Mail step type, is pre-built for you. So its probably not worth creating an ABAP OO
equivalent.
The DECISION object for user decisions. Theres a lot of special functionality around this
object for simple question/answer decisions especially if you are using the UWL.
Generic Object Services a lot of transactions still link to BOR objects so it can be worth
referencing the BOR object to keep the Workflow Overview feature going.
BOR events from standard transactions a lot of transactions that have inbuilt workflow coding
that raises BOR events so its still handy to reference BOR objects in your ABAP OO classes
for these scenarios too.
And of course theres a fair bit of business content in provided BOR objects you might want to reuse.
Coming Attractions
Over the coming series well be discussing
So therell soon be plenty of help to get you going. In the meantime, make sure you get involved in the
Business Process Management forum.