Need help with Webflow generated from PCRs

[Former Member]

Hi,

I'm having major problems getting webflow to work in Portal. Specifically, to get the approve or reject screens for the approver.

I'm testing with workflow WF50000041 and this is linked to the PCR 'Request Special Promotion'. I think I've done all the necessary config because now, when I go in as a user to generate that PCR, it creates a work item in the approver's Inbox and I can see it in R/3. These are steps that happens next:

1. Logged in R/3 as the approver

2. Go to the Inbox and double clicked on the work item and immediately taken to the Portal page and had to log in

3. After logging in the system displays error message:

Error in Web service execution

E:SWF_HTTP:050 TS50000075

TS50000075 being the standard task number. I searched the Portal logs and I cannot find anything.

I'm at loss at this point, because I've set the HTTP handler and all related config. I cannot find any information on 'SWF_HTTP:050' error in OSS. Note: I've not set up UWL (and I'm trying not to) because my client will not implement KM.

Has anybody come across this or have any pointers or documentation? It would be greatly appreciated.

Thanks,

JS

[Former Member · Accepted solution]

as the answers up to now didnt contain anything that did help us on our search when we had the same problem here our "solution":

- use transaction WF_EXTSRV to enter a service-id and the parameters of your external workflow service

- with transaction WF_CPL you then can connect the service-id to the workflowtaks

et voila...did work for us

[Former Member · Accepted solution]

Hi,

I used the "Generate Task" button [in WF_EXTSRV] to create the Standard Task which I included in my workflow. Problem is, that it was created as a local object ($TMP). That TS wasn't transported and now the workflow template is incomplete.

How am I supposed to do this? This config must be transported so one must define which service to start in DEV. When you transport it to QA, then the DEV settings are transferred.

I really don't want to have a branch in my workflow that checks the system-id/client.

Any ideas?

Thanks and regards,

Walter

[Former Member · Accepted solution]

Hi all,

The missing transaction code is WF_CPL. This links the generated workflow task, by logical system, to the service.

Easy, when you have the right Transaction Codes

Cheers

Walter

[Former Member]

Hi guys,

I'm encountering the same problem. Could you please clarify the steps again? We have performed the following steps in test environment:

- Create BSP applications

- Maintain entries for all BSP applications in WF_EXTSRV

- Generate the workflow tasks for these BSP applications (also in WF_EXTSRV). We entered server, port and logical system of our test environment.

- We insert the generated tasks in the respective workflow steps

- We included the generated tasks in transport requests manually

Now after transport to production the BSP Applications cannot be started because the settings regarding server, port and logical system refer to the test environment - which is of course logical. So what I did was to do a repair in production and generate every BSP application again. This works but the task numbers of test and production are not the same anymore.

So what do I have to do to make this work dynamically? Maintain entries in WF_CPL (in production system)?

Thanx in advance!

Message was edited by: Oliver Müller

[Former Member]

Sherdil,

Can you mail the document which u followed to get the workflow (webflow) setup in r/3 and for PCR ?

My email address is: sweet.shikha80@gmail.com

Thanks,

Shikha

[Former Member]

Hi,

Did you ever resolve this, we are seeing a similar problem with workflows being triggered from the UWL

Kind regards

Richard