Approve failed in UWL

We are using UWL to approve or reject travel request.
If I click on approve button I get a message as Approve failed .Same for reject also,
If I check the checkbox for approve and click submit decision button I get an error as "Function is obsolete(successor:SAP_WAPI_Decision _Complete)"
I checked the webflow connector system alias it is Sap_Webdynpro_Xss
The RFC destination for the same is also maintained in visual admin.
However when I test the system I get ITS and connection test successful but the webAs test fails.
In WebAS properties the webAs path is mentioned as /webdynpro/dispatcher.
Do we need to activate any service in SICF for this ?
Please suggest .I feel the error is somewhere linked to this WebAS test failure.
Thanks in advance;
Anzar Naik

no replies so closing it.

Similar Messages

Approval Failed Error in MSS

Hi,
i am working on MSS Travel Management Work Flow.
The problem is when i wants to approve the Requests from MSS ( Portal ) it is giving me an error Saying 'Approve Failed ' & also all the activites i click it is giving ' XXX Failed ' .
But the workflow is working fine in R/3. Only problem is when i am trying to do it from Portal.
Can any one tell me what could be the problem ?
Waiting for ur reply ....
Regards,
Srinath

I think this is aproblem in MSS. Is this happening to all the User's or some of the User's. I think there is some setting that you need to incorporate. Please check in the MSS forum.
Thanks
Arghadip

Hiding com.sap.pct.srm.core.action.oldwfl.approve button in UWL InBoX

Hi,
Currently I am working on SRM upgrade project . How to remove/hide approve button in UWL inbox.
Below xml code, using in UWL configuration file in portal:
<ItemType name="uwl.task.webflow.srm.TS90000005.SAP_SRM" connector="WebFlowConnector" defaultView="com.sap.pct.srm.core.view.tasks" defaultAction="com.sap.pct.srm.core.action.launchWD.oldwfl.cont.approve" executionMode="default">
<ItemTypeCriteria systemId="SAP_SRM" externalType="TS90000005" connector="WebFlowConnector"/>
<Actions>
<Action reference="com.sap.pct.srm.core.action.launchWD.oldwfl.cont.approve" />
<!<Properties><Property name="display_order_priority" value="uwlExcludeFromPreviewDetail"/></Properties></Action>>
</Actions>
</ItemType>
Implemented " uwlExcludeFromPreviewDetail" code in xml, but it is not working. Pls guide, how to tweak the properties definition a little bit to get it to work.
By removing approval reference in xml code, approre button and inbox hyperlink both functionality disappear. As per my requirement, Inbox approve data should have hyperlink as it is and approve button should be disappear/remove/hide.
Otherwise without hyperlink, user has to select any workflow item and click "Details" button. For this need xml code for enabling Details button
Anybody light on this

Hi,
Remove the Approval action from the XML by deleting <Action reference="com.sap.pct.srm.core.action.launchWD.oldwfl.cont.approve" />
Also on this, <ItemType name="uwl.task.webflow.srm.TS90000005.SAP_SRM" connector="WebFlowConnector" defaultView="com.sap.pct.srm.core.view.tasks" defaultAction="com.sap.pct.srm.core.action.launchWD.oldwfl.cont.approve" executionMode="default">
change the defaultAction="viewDetail" to enable the hyperlink which will open up the detail if click on hyperlink. If you need to open up the details in SAP GUI (ITS), change the defaultAction="launchSAPAction"
Hope this helps.
Jigar

Leave Approval Error via UWL

Goodday,
I am getting an error clicking on the task in UWL for leave request approval. The leave request is available in the manager's UWL. However, when teh manager clicks the workitem, we get the following dump:-
================================================================
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaData' in the SLD. No such JCO destination is defined in the SLD.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:476)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:241)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:168)
    at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:36)
=====================================================================
However, when we tried the 'leave request: approval' iview, we are able to see teh request and approve it. The error is only approving via UWL. Any idea on this?

Hi ,
please find the following solution .it will definitely work .
If you leave configuration is done.
There was an incorrect data in your system. To do these please follow following process.
delete this request using
PTARQ> Delete documents (RPTARQDBDEl)
Please read the report documentation before
deleting the request but it should be safe as it is
a development system.
Please delete this with the above information or delete all
the records for the approver.
After this,, there will be some incorrect workitem in approver inbox.
You need to clear that also by Tcode - SWWL.

Group Management approval failed estatus pending

Hi everybody, have a nice new year 2015,
I have an error about approval notifications and the issue is explained below in detail:
Whoever the user (approver) try to approve the requests from FIM portal (from
My Pending Requests tab), he is getting the "Request Failed" popup. the requests is not getting approved and remains with
Pending state.
There are no failure requests entries generated in the FIM admin portal (when looking into
Search requests tab) and the requests remains in Authorizing state which seems like there is a pending approval to complete the request. Because of this, in the fim server, I was unable to identify that the requests
are not getting approved (as the FIMADMIN).
The requests are stucked. All the workflows in the stucked requests are left in
Running state.
As a process, If the approvers do not approves the request in 5 days, the request gets expired on the 6th day. I have seen that the stuck requests initiated in last week are not getting
expired and remains in Authorizing state.
In the fim portal event viewer log , we have seen the below error each time the approvers were trying to approve requests and had got
"Request Failed" error pop-up.
I've done the following workarounds and none fixed it:
http://www.networksteve.com/forum/topic.php/FIM_2010_R2:_Requests_not_getting_approved_from_FIM_Portal./?TopicId=38033&Posts=7
My actually versión is 4.1.3419.
Thanks in advanced
Regards
FIM

Hi,
Once you get the ListID, please access the url in format as:
https://sitename/_layouts/15/ListEdit.aspx?List=dd96257b-9004-49c3-99fc-0dc4b9213c12
By the way, I get the ListID in Response body but not in
Request body.
Regards,
Rebecca Tu
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Aperture & Publish for Approval fails with webserver . . .

I'm trying to get Publish for Approval working with Aperture. We are able to load the webpage on the client's browser, she can select an image, but when she hits "submit," Safari can't open the page "because the server is not responding."
10.5.4, Aperture 2.1.1, Publish for Approval 1.5. The Apache2 error log:
Mon Aug 04 13:58:20 2008 warn Init: Session Cache is not configured hint: SSLSessionCache
Mon Aug 04 13:58:21 2008 notice Digest: generating secret for digest authentication ...
Mon Aug 04 13:58:21 2008 notice Digest: done
Mon Aug 04 13:58:21 2008 notice Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
Mon Aug 04 13:58:46 2008 notice caught SIGTERM, shutting down
Mon Aug 04 13:58:46 2008 warn Init: Session Cache is not configured hint: SSLSessionCache
Mon Aug 04 13:58:46 2008 notice Digest: generating secret for digest authentication ...
Mon Aug 04 13:58:46 2008 notice Digest: done
Mon Aug 04 13:58:46 2008 notice Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
Mon Aug 04 14:13:20 2008 error http://client 192.168.93.10 File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://192.168.93.10/1941/index.html
Mon Aug 04 15:56:17 2008 error http://client 192.168.93.10 client denied by server configuration: /Users/david/Sites/
Mon Aug 04 16:26:59 2008 error http://client 65.96.217.170 File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 16:28:17 2008 error http://client 65.96.217.170 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/40.html
Mon Aug 04 16:28:59 2008 error http://client 65.96.217.170 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/index.html
Mon Aug 04 16:33:17 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
Mon Aug 04 16:33:17 2008 error http://client 65.96.217.170 Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
Mon Aug 04 16:33:59 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 16:33:59 2008 error http://client 65.96.217.170 Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 16:38:17 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
Mon Aug 04 16:38:59 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:16:56 2008 error http://client 65.96.217.170 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:17:55 2008 error http://client 65.96.217.170 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/02.html
Mon Aug 04 17:21:56 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:21:56 2008 error http://client 65.96.217.170 Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:22:55 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
Mon Aug 04 17:22:55 2008 error http://client 65.96.217.170 Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
Mon Aug 04 17:26:56 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:27:55 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
Mon Aug 04 18:03:28 2008 notice caught SIGTERM, shutting down
Mon Aug 04 18:04:30 2008 warn Init: Session Cache is not configured hint: SSLSessionCache
httpd: Could not reliably determine the server's fully qualified domain name, using Russia.local for ServerName
Mon Aug 04 18:04:31 2008 notice Digest: generating secret for digest authentication ...
Mon Aug 04 18:04:31 2008 notice Digest: done
Mon Aug 04 18:04:31 2008 notice Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
Mon Aug 04 18:47:55 2008 error http://client 192.168.93.10 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://192.168.93.10/1941/index.html
Mon Aug 04 18:52:55 2008 warn http://client 192.168.93.10 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
Mon Aug 04 18:52:55 2008 error http://client 192.168.93.10 Premature end of script headers: Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
Mon Aug 04 18:57:55 2008 warn http://client 192.168.93.10 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
We've opened ports 80 and 443 on the firewall, and tried to approve and submit locally, with the same results.
If anyone has any ideas on how to get this to work, it would be great. We have a lot to submit, and the client really would like to do it on line.
Thanks,
David

Thanks for your input guys.
We discovered that we originally had used Publish for Approval 1.1, and subsequently have changed to version 1.5, which no longer uses the third party app.
Unfortunately, we still have the same problem, the client's browser stops loading when he or she hit's the "submit" button.
---> Could the installation of the 1.1 and third party app have left some preferences that need to be deleted or settings that need to be reset?
---> The error message on the client's web browser now states that the "server unexpectedly dropped the connection." Trying again later is not successful.
The error logs for Apache2 from the most recent attempt are different than with the 1.1 version of the software:
[Tue Aug 05 11:56:50 2008] [error] [client 76.24.22.217] File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://71.232.115.230/1941/index.html
[Tue Aug 05 11:57:50 2008] [error] [client 76.24.22.217] File does not exist: /Library/WebServer/Documents/1941/images/blank.gif, referer: http://71.232.115.230/1941/12.html
[Tue Aug 05 11:58:18 2008] [error] [client 76.24.22.217] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/12.html
[Tue Aug 05 12:03:18 2008] [warn] [client 76.24.22.217] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/12.html
[Tue Aug 05 12:03:18 2008] [error] [client 76.24.22.217] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/12.html
[Tue Aug 05 12:08:18 2008] [warn] [client 76.24.22.217] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/12.html
I don't know much about this, I just want my client to be able to approve the images through the Aperture interface.
Thanks again, I really appreciate the help.
David

"Publish for Approval" fails on submit

I'm trying to get Publish for Approval working with Aperture. We are able to load the webpage on the client's browser, she can select an image, but when she hits "submit," Safari can't open the page "because the server is not responding."
10.5.4, Aperture 2.1.1, Publish for Approval 1.5. The Apache2 error log:
[Mon Aug 04 13:58:20 2008] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Mon Aug 04 13:58:21 2008] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 04 13:58:21 2008] [notice] Digest: done
[Mon Aug 04 13:58:21 2008] [notice] Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
[Mon Aug 04 13:58:46 2008] [notice] caught SIGTERM, shutting down
[Mon Aug 04 13:58:46 2008] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Mon Aug 04 13:58:46 2008] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 04 13:58:46 2008] [notice] Digest: done
[Mon Aug 04 13:58:46 2008] [notice] Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
[Mon Aug 04 14:13:20 2008] [error] [client 192.168.93.10] File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://192.168.93.10/1941/index.html
[Mon Aug 04 15:56:17 2008] [error] [client 192.168.93.10] client denied by server configuration: /Users/david/Sites/
[Mon Aug 04 16:26:59 2008] [error] [client 65.96.217.170] File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 16:28:17 2008] [error] [client 65.96.217.170] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/40.html
[Mon Aug 04 16:28:59 2008] [error] [client 65.96.217.170] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 16:33:17 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
[Mon Aug 04 16:33:17 2008] [error] [client 65.96.217.170] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
[Mon Aug 04 16:33:59 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 16:33:59 2008] [error] [client 65.96.217.170] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 16:38:17 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
[Mon Aug 04 16:38:59 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:16:56 2008] [error] [client 65.96.217.170] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:17:55 2008] [error] [client 65.96.217.170] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/02.html
[Mon Aug 04 17:21:56 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:21:56 2008] [error] [client 65.96.217.170] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:22:55 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
[Mon Aug 04 17:22:55 2008] [error] [client 65.96.217.170] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
[Mon Aug 04 17:26:56 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:27:55 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
[Mon Aug 04 18:03:28 2008] [notice] caught SIGTERM, shutting down
[Mon Aug 04 18:04:30 2008] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
httpd: Could not reliably determine the server's fully qualified domain name, using Russia.local for ServerName
[Mon Aug 04 18:04:31 2008] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 04 18:04:31 2008] [notice] Digest: done
[Mon Aug 04 18:04:31 2008] [notice] Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
[Mon Aug 04 18:47:55 2008] [error] [client 192.168.93.10] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://192.168.93.10/1941/index.html
[Mon Aug 04 18:52:55 2008] [warn] [client 192.168.93.10] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
[Mon Aug 04 18:52:55 2008] [error] [client 192.168.93.10] Premature end of script headers: Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
[Mon Aug 04 18:57:55 2008] [warn] [client 192.168.93.10] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
We've opened ports 80 and 443 on the firewall, and tried to approve and submit locally, with the same results.
If anyone has any ideas on how to get this to work, it would be great. We have a lot to submit, and the client really would like to do it on line.
Thanks,
David

It looks like your webserver is not set up correctly. You might get better responses in the Networking and the Web forum - this is the Leopard Automator forum.

Approve step in UWL

Hi,
I am trying to integrate MDM Workflows with UWL. I got it working but have a question regarding the Approve MDM step. Is there any way we can get the Approve step also displayed on the Portal? Has some on done this earlier? Is there any documentation on configuring MDM Approve workflow step in UWL?
any information in the right direction is highly appreciated.
Thanks.

refer to [Integrating Universal Worklist in SAP Master Data Management|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/771f1a61-0e01-0010-daa9-93a52905da09]
Hope this helps.
Rgds

Dynamic Distribution Group - Moderator approval fails

hi,
(On premise and office365 Exchange)
we use the above in our organization. we have some dynamic groups created. I have a moderator for a couple of groups. when a user sends an email to one of the group that has a moderator, the latter gets an email to either approve or reject the message. when
he/she clicks on the accept button they get the following error:
Delivery has failed to these recipients or groups:
Microsoft Exchange Approval Assistant
Your message wasn't delivered because the recipient's email provider rejected it.
Diagnostic information for administrators:
Generating server: DB4PR07MB0701.eurprd07.prod.outlook.com
SystemMailbox{d57a4133-7e21-486e-9917-f7fb70dc2cdb}@XXXXXX.onmicrosoft.com
Remote Server returned '< #5.7.12 smtp;550 5.7.12 RESOLVER.RST.SenderAuthenticated; Delivery restriction check failed as sender not authenticated>'
Original message headers:
Received: from AMXPR07CXXXXX.eurprd07.prod.outlook.com (10.242.64.XX) by
DB4PR07XXXXX.eurprd07.prod.outlook.com (10.141.45.XX) with Microsoft SMTP
Server (TLS) id 15.1.6.9; Fri, 31 Oct 2014 14:20:41 +0000
Received: from DB3FFO11XXXXX.protection.gbl (2a01:111:f400:7e04::130) by
AMXPR07CXXXXX.outlook.office365.com (2a01:111:e400:1000::20) with Microsoft
SMTP Server (TLS) id 15.1.11.14 via Frontend Transport; Fri, 31 Oct 2014
14:20:41 +0000
Received: from XXXXX.XXXXX.co.ke (197.220.102.XXX) by
DB3FFO11FD053.mail.protection.outlook.com (10.47.217.XXX) with Microsoft SMTP
Server (TLS) id 15.0.1049.20 via Frontend Transport; Fri, 31 Oct 2014
14:20:40 +0000
Received: from XXXXX.XXXXX.co.ke (192.168.11.XXX) by
XXXXX.XXXX.co.ke (192.168.11.XXX) with Microsoft SMTP Server (TLS) id
15.0.847.32; Fri, 31 Oct 2014 17:20:37 +0300
Received: from XXXXX.XXXXX.co.ke ([fe80::4b9:1080:7301:f8be]) by
XXXX.XXXXX.co.ke ([fe80::4b9:1080:7301:f8be%15]) with mapi id
15.00.0847.xxx; Fri, 31 Oct 2014 17:20:37 +0300
From: "XXXXX XXXXX " <[email protected]>
To: Microsoft Exchange Approval Assistant
<SystemMailbox{d57a4133-7e21-486e-9917-f7fb70dc2cdb}@XXXXX.onmicrosoft.com>
Subject: Approve: * QUOTE OF THE DAY *
Thread-Topic: * QUOTE OF THE DAY *
Thread-Index: Ac/1FciNlxJwVzCBTJKjqDyb/OnY+gAAAOtxAAAChkA=
Date: Fri, 31 Oct 2014 14:20:37 +0000
Message-ID: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.XXX]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Return-Path: [email protected]
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:197.220.102.xxx;CTRY:KE;IPV:NLI;EFV:NLI;
X-OriginatorOrg: XXXXX.onmicrosoft.com
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR07xxxxx;
Kind Regards, Khuzema R.

Hi Khuzema,
Please confirm if your Dynamic Distribution Group is created on-promise and the moderator is on the Office365 Exchange.
If the Dynamic Distribution Group and the moderator are in different Exchange servers: On-premise and Online, please open the Dynamic Distribution Group in EAC, then check
Senders inside and outside of my organization in delivery management to have a try.
If it doesn’t work, I suggest we can change a moderator who is in the same mailbox server with the Dynamic Distribution Group to check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support

Leave approval text changes are not displayed in UWL

Hi friends,
I have made some changes to text label of leave approval application using ctrl+right click(done in role->workset->page->iview) in content admin but it not reflecting in UWL(when calling leave approval application in UWL).any idea pls.

Hi,
aah i think the problem is at the uwl xml config file, which controls which iview is opening for a specific task id.
please enable the support info, at this u can see which xml file is used and you can change the directory/iview which is called by opneing the "leave approval":
1. Log on to the portal
2. Navigate to the following path: system administration > system
configuration
3. In detailed navigation click on the UWL & Workflow folder
to expand out
4. Then click on the Universal Worklist Administration link
5. Scroll down to the bottom of the page:
Optional Universal Worklist Service Configuration
Open the Tray for the Optional UWL Service Configuration
Click on the button to open the tray for the optional UWL service
configuration
6. Scroll down again
7. Go into edit mode
8. Display Support Information: Set the parameter to true
9. Save
have also a look here:
http://help.sap.com/saphelp_nw70/helpdata/en/44/c0001cdfcd1386e10000000a155369/frameset.htm
i hope this can help u
br,
fabian

Attachments in Travel Expense approval not displayed in UWL

Hi guys,
We here have implemented the travel expense workflow WS20000040. According to the current std functionality, when the requestor creates a travel expense request, he is able to attach any attachments along with the request. But when the request moves to the approver in his UWL, he is not able to see the attachments. (except a default one which on clicking, opens the PR05 txn)
Is there any config or note which needs to be applied for these attachments to be visible under the UWL's attachments?
Please help.
Regards,
Pranita
Please refer attached screenshots of requestor's and approver's screens..

Hi Pranita,
as far as I know, there is no standard functionality that implements the GOS-Links into the UWL. I've had the same problem as you and implemented a workaround that works as follows:
I wrote a class that implements the Interface IF_SWF_IFS_WORKITEM_EXIT and within the only method it contains I read the GOS-Documents which I then attach as normal workflow attachments to the Workflow API. The Class is used within the programming exit of my Workflow's decision task (it's then, by definition, automatically executed). This approach has one major disadvantage: The attachments are only passed to the WF upon sending the TRIP for approval, i.e. only when the workflow is executed, naturally. This means if the TRIP is sent for approval and then the employee creates attachments afterwards (which is possible even if the trip itself can not be changed due to authorization etc.), the manager will not receive these retroactively attached documents.
Beforehand: I'll not share the coding for this because I based it on the coding of an external colleague; but the description above should give you a design-technical idea of how to achieve your requirement.
One more thing. To get rid of that nasty process object that links to the PR05, you can use SWFVISU. I didn't know how to do this myself until 4 months ago or so. Ibrahim Ansari explained me how to do it in one of my threads over here: Hide/Remove process Object from Workitem that is shown as attachment in UWL possible?
Hope it helps.
Cheers, Lukas

How to automate the approval procees of a document in UWL?

Hi All,
I am using the action Inbox connector to publish a document in KM after after approval.
My requirement is that the doc shud be approved automatically if the manager doesn't approves in a particular timespan.
The action handler for the approve action in UWL xml is com.sap.km.approve.
Please guide me how to achieve this.
Regards,
Sumit

Hi Sumit,
In order to publish a document you could try something like this:
IResource resource = ....;
IStatemanagementManager service = (IStatemanagementManager)ResourceFactory.getInstance().getServiceFactory().getRepositoryService(resource, "StatemanagementRepositoryService");
IStatemanagementResource smResource = service.getStatemangementResource(resource);
IResourceTransition resourceTransition = smResource.getTransition("lbl.skip.tobereleased");
boolean success = resourceTransition.execute();
Now this will only work if the user in the ResouceContext is an owner of the resource and if the resource is in "To be released" status.
For a better understanding of the process decompile km.appl.repository.service.statemanagement_core.jar and study the code.
Best regards,
Avishai Zamir

UWL- Mass approval fromPortal.

Dear Experts,
We have a requirement like mass approval from MSS UWL- tasks from Poral.
I have checked below threads,
uwl mass Approval- Select all option
and
UWL Mass Approval XML changes or Custom App
Please provide any other inputs to achieve mass approval from portal.
Thanks in advance.
Regards,
Mahee.

Hello Piyush, I'm solving the same problem. Can you help me ?
I have found, that I can add new button into mass approval's view:
               <Action name="accept" groupAction="yes" handler="UserDecisionHandler">
               <Properties>
               <Property name="decisionKey" value="1"/>
               </Properties>
               <Descriptions default="Accept all"/>
               </Action>
That approves all displayed items. But that's not exactly what I'd like to do.
I just want to select all checkboxes/radio buttons in mass approval view.
Could you be so kind and give me your solution ?
Thank you very much,
Roman

Disabling/Hiding Approve button UWL Inbox

Hi,
Currently I am working on SRM upgrade project . How to remove/hide approve button in UWL inbox.
Below xml code, using in UWL configuration file in portal:
<ItemType name="uwl.task.webflow.srm.TS90000005.SAP_SRM" connector="WebFlowConnector" defaultView="com.sap.pct.srm.core.view.tasks" defaultAction="com.sap.pct.srm.core.action.launchWD.oldwfl.cont.approve" executionMode="default">
      <ItemTypeCriteria systemId="SAP_SRM" externalType="TS90000005" connector="WebFlowConnector"/>
      <Actions>
       <Action reference="com.sap.pct.srm.core.action.launchWD.oldwfl.cont.approve" />
<!<Properties><Property name="display_order_priority" value="uwlExcludeFromPreviewDetail"/></Properties></Action>>
     </Actions>
    </ItemType>
Implemented " uwlExcludeFromPreviewDetail" code in xml, but it is not working. Pls guide, how to tweak the properties definition a little bit to get it to work.
Tried by mentioning USERDECISION parameter in UWL iview exclude property.

Hello,
Have you tried to remove:
<Actions>
<Action reference="com.sap.pct.srm.core.action.launchWD.oldwfl.cont.approve" />
<!<Properties><Property name="display_order_priority" value="uwlExcludeFromPreviewDetail"/></Properties></Action>>
</Actions>
from the xml file? Then upload the new xml file with a new name with high priority to the portal? Also another thing that you can do is hide the whole descriptions section with all of the buttons. This is listed in the help documentation on how to do that.
Beth Maben
EP - Senior Support Consultant II
AGS Primary Support
Global Support Centre Ireland
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq ***

UWL approval creates additional task compared to SBWP

Hi..
We have workflow to approve travel expenses in ESS/MSS. If the task is approved via SBWP, then one item (TSxxxxx) appears in the folder "Work items executed by me" and the same in the "Completed Tasks" dropdown in the Universal Worklist.
However if it is approved via the UWL, two items are created - one TSxxxxx and one WSxxxxx - both these items appear in the "Completed Tasks", and also the "Work items executed by me" folder of SBWP.
Can someone explain what is happening please?
Many thanks
Jane

Hi,
I have no idea and that makes no sense.
But it seems that this could be solved probably by some debugging. Just do an RFC trace to find out that which function is used to get the completed tasks (I cannot remember the function), and then do some debugging and check where the function gets the data and what's the difference between these two cases.
Regards,
Karri
PS. What do you use for approval? Do you use same application both in portal and in backend? Or if you use different application (maybe web dynpro in portal and transaction in backend?) that could explain your problem. Maybe they are causing the workflow to react differently for approval.

Approve failed in UWL

Similar Messages

Maybe you are looking for