ABAP OO Workflow passing variables

[JuanCarlosDelga]

Hello guys,

we are trying to build our own custom workflow class based and facing some comprehension problems. First of all we read this blog and it's very helpful: https://blogs.sap.com/2006/08/21/using-abap-oo-attributes-in-workflows-and-tasks/

So we created a workflow (see screenshot below) that gets triggered by FI document change (without BOR) and leads to a user-decision for approval. The results are approve or decline. In both cases workflow ends. That all works fine.

The problem now is how can we pass variables in our custom Z-class, that was build for the workflow, from one step to another? If we create a new container element lets say ZVARIABLE everything works fine. We define it in every step and pass it through the different steps. But if we have a variable in the workflow class and try to give it back to workflow it stays empty. It looks like that only variables which get filled when creating object with constructor will be transfered through the workflow steps because they are available in all workflow steps. So isn't it possible to use variables of the workflow class for the whole workflow when they are getting filled after constructor?

And if its possible: This leads to the question how is the correct order of passing variables through the workflow? We have a workflow activity which has task in it. In the activity/step itself we can do binding from Workflow to Step and back from Step to Workflow.

In the task of the workflow we have a custom method of our Z-class which has binding from Task to Method and back from Method to Task.

So which of the bindings is called first? The workflow passes variables to the task and its method? The method then passes variables back to the task? Then the task passes it back to the workflow?

Regards
Michael

[JuanCarlosDelga]

Hi Michael,

First, from the starting event you can pass the WF a parameter (your class and the key). Then, your class must have a constructor to create an instance.

So, when you trigger the event, you need to pass some paremeter (the class and the data to create an instance of your workflow class).

Best Regards

JCD

[Missschaaa]

Hey Juan,

I work with constructor to create instance. As I understand constructor it is used to identify the workitem in every step of the workflow. So my constructor method passes the key of my object to the persistant object reference and correct workitem is identified.

I also have a public instance structure in my Z-class where some fields get filled in constructor method. But this structure also has some fields in it, which I canot fill in constructor because they are dependent from the workflow step. For example I have a boolean which is set to true if some checks in one step of the workflow gives a special result. So I thought of setting the variable of the structure in the corresponding method call of the step of the workflow and give it back to the workflow then. But it looks like that it gets lost after it is setted in the method. If I do the same with a variable that is defined in the workflow container itself without being part of the workflow class object it works.

Regards
Michael