UWL Config for WD4A vs ESS/MSS

[Max S Gro]

Hi,
Jocelyn, thanks for the answer. I managed to get the workflow working.

Below are the portal system configuration (System Admin - System Config -
Portal Content - System) :

   - Web AS Host Name : <domain>:5XXXX
   - Web AS Path : /webdynpro/dispatcher

Even though connection test for SAP Web AS failed, but the setting has
served ESS/MSS very well.

In continuation of my below email, I have created an WD4A application,
mapped TASK ID and WD4A, and register my UWL in the portal.

The issue comes when approver clicks on the workitem in his UWL. He got the
following error message: "The requested object does not exist".

I can understand the error comes because system try to call
"http://<domain>:5XXXX/webdynpro/dispatcher/WD4A
Application", while my WD4A application resides at
"http://<domain>:8XXX/sap/bc/webdynpro/sap/WD4A
Application".

If i change the portal configuration to
"http://<domain>:8XXX/sap/bc/webdynpro/sap/",
the UWL will call WD4A Application correctly, but ESS/MSS doesn't work
anymore.

I don't want to change the existing portal configuration.
But how do i call my WD4A from my UWL ?
Any idea what configuration that I miss ? or maybe alternative solution ?

Thanks in advance.

Again, sorry for my silly questions.

Regards,

On Fri, Jun 3, 2011 at 8:46 AM, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:

> Hi Max, ****
>
> You might want to take a look at workflow patterns generally...   ****
>
> ** **
>
> For 5. Usually a loop with a background step to check if there are more
> approvals to go, plus a background step to get the number of approvals.
>  That way if you add more levels or reduce levels later you are covered. *
> ***
>
> ** **
>
> For 6. You want to think about using a subflow and raising an event in the
> subflow on rejection – the main flow responds to the rejection by restarting
> at wherever you need. ****
>
> ** **
>
> Re your statuses ... no we don’t usually bother with multiple approval
> statuses – you can always use a container element to keep your intermediate
> status – but you need to think about what information the initiator needs to
> see to know where the approval is up to. ****
>
> ** **
>
> Cheers,****
>
> Jocelyn  ****
>
> ** **
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Max S Gro
> *Sent:* Thursday, 2 June 2011 10:45 PM
> *To:* SAP Workflow Users' Group
> *Subject:* Offline PDF Form and Workflow Integration****
>
> ** **
>
> Hi WUG-ers,
>
> Due to my lack of SAP workflow knowledge, I would like to apologize
> beforehand for my silly questions. Please kindly bear with my questions.
>
> I have the following scenario:
>
> 1. Offline interactive PDF form with "Submit" button.
> 2. Once "Submit" button is clicked, it will call web service.
> 3. Web service will save the form entries into custom table and trigger the
> event.
> 4. By triggering the event, system will then trigger the customized
> workflow.
> 5. Depends on certain condition, number of approvals will vary (the setting
> is in custom table).
>     example: < 1000 = 1 level of approval
>                   1000 - 3000 = 2 level of approvals
>                   3000 - 5000 = 3 level of approvals
>     Q: How do i do this kind of dynamic level of approval ?
> 6. Any Approver can "approve", "reject" or ask requester to "revise"
> (change the application).
>     "Approve" and "Reject" will end the workflow cycle.
>     "Revise" ---> requester needs to change the application from offline
> interactive form and "Re-Submit" the application.
>      Q: For "Revise" case, how can i continue the previous workflow cycle
> ?
>
> I have the following status:
> S = Submitted
> A = Approved (by all approvers)
> R = Rejected
> V = Revised
> T = Re-Submitted
>
>      Q: Best practice: do i need different status for different level of
> approval (eg: A1 = approved by 1st approval, and so on) ?
>
> I marked my questions in blue. Hopefully i explain the scenario clearly.
>
> Again, apologize for my silly questions.
>
> Thanks In Advance !!****
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110812/4c3465f3/attachment.htm