KM provides the feature Publishing with approval process . We can use this feature to implement a standard workflow process for the resources or documents in a KM folder. In my project we have provided an Input form for creating a resource in KM which we develop using Web DynPro application.
This application will create a resource in a predefined folder in KM. The folder will be set up for approval process so that once the user submits the document for approval, it will go through the Workflow process.
Once in workflow, the approvers will see the document pending in his standard UWL iView for his review and action (Approve, reject, send feed back etc).
Now, if the approvers at each stage can edit these resources. And he needs the same input form we created in Web DynPro to perform this action. So essentially we need to kick a Web DynPro application from UWL.
In this scenario, I used OTH configuration to attain the requirement. The UWL may contain many work items other than resources from this KM Folder. So the configuration of OTH will ensure that it affects only the resources in a particular KM Folder. More over this solution gives many more advantages like, even the recent notification iView will be affected in our way. To be precise, where ever this KM Folder resource will be referred, when opened will open the Web DynPro application.
We need “Super Admin Role” to configure OTH. Only with this role one can have “Rendering Information” link on the top of every KM Folder.
What we will do is, create an OTH, upload the file into the OTH folder. A sample OTH is provided in this blog. We can view the loaded OTHs in the server by going to “OTH Overview” from the “Rendering Information” link
Reload the OTH and we can see our new OTH file.
Remember, the OTH file will be seen only if the file is a valid xml file. Even if we upload an OTH file, it will be seen in the OTH folder. But if its not a valid xml, it wont be shown in the OTH overview page. Once the OTH appears in this page, the effect will take place immediately, means you don’t have to restart the server or any thing.
We have two important areas to concentrate in the oth file.
2. Action URL
Path describes on which KM folder this oth should act on.
Action URL describes which WDP application to open up
and the additional parameters to be passed while opening the WDP application. We are using parameters to be passed through URL.
Below is a sample oth file
In your WDP you can receive the resource.uri using this code.
String rid =
Make sure that when you create a WDP iView in Portal, provide a application parameter with the name Resource.
Now as you got the resource name( which can be filtered from the resource.uri using the following code
rid.substring(rid.lastIndexOf(‘/’) + 1) ), its up to you to implement the business logic.
In my scenario, I had to open the same creator view with the values populated in the respective fields.
Assumptions and Restrictions
1. Dont put any other files in this folder other than what your application is expecting.
2. The WDP application will be kicked in from UWL, Recent notification iView- from wherever where this folder is referred.
1. Make sure that the OTH files are reloaded in the OTH overview page.
2. In the OTH overview page, the OTHs will be listed according to the oth name, not the OTH file name.
3. While making the Web DynPro iView in portal, make an application parameter by the same name as that you are using in the oth file.