I'm looking for some help on the mechanics of workitem visualization.
We have a workflow workitem that exists on the ABAP stack of an XI server. This workitem needs to be displayed to the EP Portal user in a screen with a web page look consistent with a web application now in use by the customer.
We have configured the Universal worklist and are now displaying the workitem in the default SAP Gui for HTML visualization. This is working fine and acts just like it does in ABAP. You get the transaction screen, do your thing and off you go.
In order to make a more "web looking screen" I understand we need to create an IVIEW that has the look and feel that the customer is used to and then via configuration in the worklist, associate that IVIEW with that specific workflow task number.
That seems simple enough at a high level but I'm a long time ABAP guy and a rookie Java guy. What I can't seem to find out is this: If I have java IVIEW, there will be fields on that IVIEW that must be mapped somehow to a corresponding field on the ABAP screen of the workitem transaction. How is this connection made and how does the ABAP transaction screen know that Screen Field A on the IVIEW maps to Screen Field VBAK-VBELN on the ABAP transaction screen?
I would appreciate any direction anyone could give me.
Jocelyn Dart replied
Yes there are a couple more types but those are the main ones. There's some good blogs by Ginger Gatling on this stuff in SDN so take a look at those. Particularly at how the workitem id is passed as a dynamic parameter.
Apart from the SAPGUI approach, you usually need to pass the work item id so you can read other data from the workitem container (function module SAP_WAPI_CONTAINER_READ) and also to tell workflow the work is done (SAP_WAPI_COMPLETE_WORKITEM or SAP_WAPI_CREATE_EVENT).