Please check if you have any entries under the "UWL Actions to Exclude" property of the UWL iview.
Thanks,
Shanti
Hi Shanti,
Firstly thanks for the response. I have checked that property and nothing is there. I've noticed that the task behaves as expected in our quality system but not in our dev system.. It's the same xml file so I cannot understand why it's behaving different between the two systems.
Thanks,
Liz.
Hi Liz,
If it is working correctly in one system and not in the other, then check the following:
Turn on the UWL support information in both the systems and make sure that the UWL item is picking up the right XML configuration in both the places.
The UWL support information is a very useful thing to identify if the correct XML configuration is being picked up for the UWL items.
Thanks,
Shanti
Hi Shanti,
I have turned on UWL support info and both systems are picking up the right xml file. I have checked that the file is the same also.
One strange thing I've noticed is that the number of supported actions for the task is different between the 2 systems. Why is that or where would you define such a thing as I don't define them in my xml file?
Many thanks,
Liz.
Hi Liz,
A reason for this behavior might be that the XML configuration file cannot be generated due to the missing RFC destination for the provider connector. As a result of that, the item type information such as available actions, dynamic parameters, visualization parameters, cannot be retrieved from the backend system.
Please Refer to SAP Note 1133821 and create the RFC destination and check if this will solve your issue.
Thanks,
Shanti
Hi Shanti,
That did the trick. Thank you so, so much!
All the best,
Liz.
Hi Liz,
As Shanti mentioned, note 1133821 should resolve this issue for you, but a few more hints in regards to this issue. Here is what you need to do:
Please review also note number 1133821 and let me know if you have
followed the steps in the message:
1. Open the Visual Administrator.
2. Navigate to the Cluster -> <INSTANCE ID> -> Server <SERVER NAME> ->
Services -> Destinations.
3. Double click on Destinations node.
4. Under Destinations select RFC node.
5. Click on "New" button.
6. In the "Enter destination name:" input dialog give as destination
name the following: <SYSTEM ALIAS>$<UWL CONNECTOR TYPE>
(e.g.: BXTCLNT100$WebFlowConnector )
7. Fill in the following fields: System ID, Message Server, Logon Group
Language, Client, Username, Password. The other fields remain default.
(Make sure the user you specify has "SAP_BC_UWL_SERVICE" role assigned.
This is needed to fetch the technical informations from the backend.)
8. Click on the "Save and Test" button
9. "Successfully connected to system <SYSTEM ID> as user <Username>"
info dialog has to appear.
10. In other cases check the settings again and check the connection to
the backend system.
- Check that after applying Note 1133821 the destination names and the
UWL connector names exactly match, even considering case-sensitiveness.
If your portal system alias (=UWL connector name) is for example
XYZCLNT100, then the rfc destination name should be exactly
XYZCLNT100$WebFlowConnector. Please correct the rfc destination
accordingly.
- After you have checked/prepared the RFC destination for the future use
please delete that connector in the UWL config UI (Portal->System
Administration->System Configuration->Universal Worklist) with which you
would like to use this RFC destination.
After that
- restart the portal cluster
- recreate and reregister connector
Now retest. Are you still seeing the issue?
The UWL service user was refactored and the steps need to be applied now
and the RFC connection set up in order for this to work properly.
Also, please note, when you are setting this up in Visual Administrator (RFC connection) that there is an issue also if you set load balancing to = NO. Please see note number: 1494620 also.
Best Regards,
Beth Maben
EP - Senior Support Consultant
AGS Primary Support, Business Suite & Technology
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq ***
Hi Liz,
I am facing the same issue, May I know what is the least SP needed to avoid this issue. please find the below information and see if you can give any inputs.
Any time I am registering the system XML file linked with uwl.webflow.SAP_SRM is getting changed Please find the xml code for latest change
<ItemType name="uwl.task.webflow.decision.TS96000007.SAP_SRM" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="viewDetail" executionMode="default">
<ItemTypeCriteria systemId="SAP_SRM" externalType="TS96000007" connector="WebFlowConnector"/>
</ItemType>
Regards
Devraj
which XML we should use for the above configuration? Please advise
