Adding Methods to Interface IF_WAPI_WORKITEM_CONTEXT

[Former Member]

Hi All,

As we are installing OPENTEXT VIM 7.5 in two different systems. One system(SAP -ABAP) RELEASE is at 700 Patch Level 011 and other at Level 014.

As a complete upgrade is time consuming , we had manually added methods to this interface IF_WAPI_WORKITEM_CONTEXT and their implementation in class CL_SWF_RUN_WORKITEM_CONTEXT.

We added all necessary Parameters, Additional attributes.

Complete code is activated and this led to successful installation and implementation of VIM7.5. We did not modify any existing methods, but only added new methods as present in our advanced system with Patch level 0014.

Now the question is, will the adding this new methods will have any impact in existing Workflow usage scenarios.?

Please let us know if any one who have done such enhancements with a manual access keys got any issues?

[pokrakam]

My opinion is that if the only thing you did was adding methods you should be OK ... for now.

As to how existing functionality is impacted, you do have a thorough test process in place, no?

I think the bigger risk is what may happen in future. Every patch/upgrade/note in this area will carry a small risk of breakage. Personally I'd rather go for changing VIM and copy the newer SAP stuff into a Z-class/subclass and pointing VIM to that. Fewer potential dependencies.

[Former Member]

Thank you very much Mike. I shall definetely request for watch out when they do the future upgrades.

Yes we added only the methods and two attributes which are in the Note as given by Sandra below.

Thanks a lot.

Regards,

Kumar

[Sandra_Rossi]

My 2 cents that nobody did such a big change.

You have to make sure that no other class implements this interface (because in your old release (but dépends on kernel too) I think that interface methods must be explicitly implemented in classes) : search in class pools in table SEOMETAREL where REFCLSNAME = 'IF_WAPI_WORKITEM_CONTEXT', and search if any local class implements it in the whole system using program RS_ABAP_SOURCE_SCAN.

Of course, if there's a new implementing class in a future support package/release, then you'll have to handle it.

Moreover, we can't tell you whether your solution may put down your system as we don't know what you did.

Note that I don't think that it makes a difference to do it with an object key or via the Enhancement Framework (not sure whether interface pools could be enhanced in 7.0).

By the way, may we know why you did a so big change?

[Former Member]

Thank you Sandra for the response.

I checked in the table you specifed and found only one class.

This is exactly the class where we added the implementations for the methods added.

GET_DEADLINES Instance Method Gets Deadlines (in SY-ZONLO)

GET_ACTION_DATA Instance Method Gets Action Data

GET_ACTION_NAME Instance Method Gets Action Name

We have to add these methods during VIM 7.5 implementation, as we got dumps pointing these methods were missing ( because we are at lower patch level)

[Sandra_Rossi]

It's a bit risky to implement manually the SAP notes. At your own risk.

• GET_DEADLINES is in note 1056341 - Enhancement of exit contexts
• I think that the methods GET_ACTION_DATA and GET_ACTION_NAME are in the note 1056344 - Additional workflow exit during when forwarding work items, but this note cannot be applied alone (probably many objects or elements which cannot be applied automatically), the whole support package SAPKB70013 must be applied.

[Former Member]

Thanks again Sandra for your great insights. Thank you very much for the NOTE mentions.

And as specified, we did the needed additions in the given NOTE as we proceeded with the testing , 1056344 - Additional workflow exit during when forwarding work items,