This Blog explains how to customize the Item launch feature available in the UWL.
The Universal Worklist enables SAP Portal end users to manage all their task items by bringing together tasks from different workflow systems, including SAP R/3 Business Workflow, and Java Ad Hoc Workflow. In Short it acts a single point access to all their tasks at hand.
Each task item in the UWL has a specific task item type. Each task item type has a default action to it. When the user clicks on it (on the trigger of the event) the default action is performed.
Objective of this Blog:
The objective of this blog would be to change the default action associated with the items displayed in the portal. For this scenario I have taken an alert item and changed the default action associated with it. On clicking the item, by default it shows information about the alert. This blog will guide you in directing the control to backend Alert category screen where one can find the category, that the alert item is associated to thereby changing the default action of that particular alert item.
1. Knowledge on Portal is necessary.
2. A basic understanding of UWL features and Concepts.
3. UWL is configured in your portal and items are displayed.
4. The scenario explained in this blog was done in Enterprise portal 04s.
Steps to be followed:
1. Go to UWL iView (Content Administration – Portal content – Content Provided by SAP – End user Content – Standard portal users – iViews -Universal worklist) and open the property Editor and set the property Display support to YES.
2. Go to UWL iView (Home – Work) and Select the UWL item whose default action is to be changed and find the Item type configuration name and Item type from the support information displayed. (For this scenario let me take an Alert Item)
3. Now next step involves either downloading the already existing uwl.standard XML file and editing it (System Administration – System Configuration – Universal Worklist administration – click here to Administrate and view item configuration Files – Select standard file in the current configuration tab and download it) or create a new XML file in a such a way that in both cases the end result should resemble the following outline:
4. After editing the file to the above outline, now we need to specify the item type which we need to change and the custom action we need to perform on click of the item.
At first add the ItemType tag with a unique type name. For my case I have added the line:
Where uwl.alert stands for alert system and UWL95ALERT, R3snw4 are the specific item type obtained from support information.
5. Next step involves adding the action tag in the XML where you need to say the custom action to be performed on click of the item.
You could see from above lines that I have named my action as ‘click’ (as entered in the default action attribute in the ItemType tag) and at the trigger of my event I have called upon the SAPTransactionLauncher to handle the event occurred.
The Handler attribute is the one which comes in handy during Customization. There are many type of action handlers provided by SAP which can be used based upon the application/action we need to perform. To know more about action handlers look for online help with the key word ‘Action handlers ‘.
Each action handler has its respective implementation in form of properties, to be defined in the XML in order to complete the action. For the present scenario I have given the property ‘TransactionCode’ and its corresponding value (you can give any backend transaction code) – I have given the transaction code for Alert categories which would list all alert categories and its info. If no transaction code is defined then it takes the default value -SWK1 transaction.
6. Once the Action and ItemType are defined close any open tags and save it.
7. Now upload the XML file into your system in the same screen where we downloaded it but this time in the Upload tab.
While you are uploading you need to give details such as Config name, Adapt to system (system alias of the system defined for Alertconnector), Check the High Priority and then upload.
8. If your XML adheres to the SAP standards the file would be uploaded and registered successfully without any errors. You would be able to see the XML file in the Current configuration tab in the same screen (Will be listed with the Configuration name that you entered when uploading). The resulting screen should resemble as given below:
9. Now go to the Alert tab in the UWL iView and click on the item. You would be able to see the custom action taking place in my case the transaction was executed and the screen was displayed.
As you could see with the help of handler attribute we can change the default action and thereby implement the action in custom way. There are different action handlers available with which we can customize according to our needs. For example take the case of URLlauncher which needs a URL as its value which could point to your own application running in your portal or an external source thereby providing lot of scope to our imagination and creativity.
I take this opportunity to thank Ginger gatling for her series of blog providing valuable info on various features of UWL.
Looking forward to lot of action in this space. 🙂