Hello, It seems that I have a problem with the binding between a task and the workflow-container. But I'll describe my problem and hope there's someone out there with a solution :
I created the object zbus2083, with supertype bus2081(MMInvoice). I added an attribute 'goedkeurder'.
I created a new method, which searches the value, change it into 1, and writes it back to the container (using swc_set_element container...)
this method works fine when I link it to a task, but the problem occurs with the binding. When I define only the binding from workflow to task, there's no problem. But when I define also the binding from the task to the workflow there occurs an error and the workflow stops.
The definition of the binding workflow - task is &zbus2083& -> &_wi_object_id&
and the other way around (The definition of the binding workflow - task is &zbus2083& <- &_wi_object_id&)
please help !
thanks for the info. I'll take a look at the rules of engagement and try my best to follow them next time I use the forum.
Concerning my problem : i got things mixed up, it was a problem with the link between the method and the task. But with a lot of trial and error I found the problem
Thanks anyway for the tip concerning the bor-objects, I didn 't know that !
A couple of things:
Firstly, please always mention the version even if you don't think it's relevant and provide enough detail. I'd suggest having a read through the
Regarding providing enough detail: you say you get an error - perhaps you could share the error message with us?
Also - why are you binding the object back? You rarely need to do this. An object is just a reference - a handle - so both your task and your WF will point to the same thing. So if the object came form WF, it's attributes will be the same wherever you look at it. Not sure what you're trying to accomplish, but also have a look at Virtual Attributes in the WF doc and in this forum, you can basically write a piece of code that gets executed each time the attribute is queried.
Lastly, you should look at delegation. It's the reverse of inheritance and makes all you Z-subtype's components visible as if they were part of the BUS2081 object. Thus you should very rarely have to use a Z-subtype in your workflows. In the front screen of SWO1, settings -> delegate -> system-wide.
Hope that helps,