Generic decision Task and ABAP OO

[former_member192189]

I have implemented a workflow using ABAP OO, which has a couple of user decision steps.

Now I have made a copy of the generic decision task (8247) into my own custom task. I then copied over the code from the process method of the DECISION BO into my own custom BO. I then referenced the custom BO in my custom task. I tied this custom task to a user decision step in my workflow.

code

I had to this so that I could extend the functionality of the code to do something specific to my logic. This works fine.

However when I write the same code in a method of my ABAP class and tie it to the same custom task instead of the BO, the workflow complains while activating "TASK XXXXX cannot be used as a decision task".

Any advice would be greatly appreciated. Thanks a lot in advance.

[former_member193382]

Hi,

May we know what is the logic that you are trying to imply through this customization?

Regards,

Raj

[former_member192189]

There is a unique requirement where when the user rejects a document, a list of rejection codes are displayed, which upon selection will display a textbox for some rejection reason.

I wanted to implement this in one logical unit of work instead of seperate steps in the workflow.

[vijy_mukunthan]

Hi Amlan Bardhan

In OO ABAP you cannot use Decision task in your code i guess. Only task can be used. Which class your are enhancing. What you want to achieve?.

Regards

vijay

[former_member192189]

Thanks for your reply. Let me try to add a little more clarity to my question.

Suppose, I copy the code from the PROCESS method of the DECISION Business Object and paste the code into a method into my class.

Now as usual I call the method in the class from a standard task. When I try to attach the task to a user decision step in the workflow, I get the messsage "Task 9100XXXX" cannot be used as a decision task.

Regards,

Amlan

[Former Member]

Hi Amlan,

What I could figure out from your query is that, you want to use ABAP OO, functionality of classes in implementing a task. Please correct me if I am wrong.

I would suggest you that Let your Workflow work with the BO, because there are certain tasks for which only BO works, implementation of classes might give some problem.

check saptechnical.com - business workflows for further correspondence

Best Regards,

Kanika

Edited by: kanika chopra on Dec 9, 2008 5:12 AM

[former_member192189]

Kanika Thanks. Yeah, that's how I have it working. I was just wanted to have all the functionality rolled up into one class and have zero references to any BO.