A Real World Example of Flexible User Interface Part 2
This is the follow on the my first weblog about using the flexible user interface. So if you haven’t already read it, I highly recommend you read it here : /people/paul.tomlinson/blog/2006/01/26/a-real-world-example-of-flexible-user-interface-150-part-1 I finished off my last weblog having created all of the elements we are going to use. This weblog puts them all together and assigns them to an iview. I am going to link together the layout set called NewsExplorer_Approve. In to this I am going to assign the resource renderer NewsResourceRenderer_Approve. To the resource renderer I am going to assign the command group NewsGroup_Approve. So first thing, assign the resource renderer. I edit the layout set, deselect NewsResourceRenderer and select NewsResourceRenderer_Approve. This have assigned the resource renderer to my layout set. Next I click on NewsResourceRenderer_Approve to take me into it. In here I change the resource (menu) command group to NewsGroup_Approve. This means that next to files (in our case XML files) we will have our modified menu (with approval in). Great. That is all of the technical bit done. We now need to create an iview and assign our layout set. Before that though we need to enable approval on our folder where we are going to save our XML files. The iviews point at where the XML files are saved (edit forms) and read from (read only / show forms). These folders need to be enabled for approval. The standard folder is /documents/News, but I’m going to create a new folder called News2 in the documents repository and use this. This can be done from anywhere where you can access the documents repository e.g. content administration -> KM Content. Approval only works if permissions are set correctly. If you have read /write permission to the files, you will always see them no matter whether they are approved or not. So only authors need read / write permission. So the permissions need setting up by going into the News2 folder and then menu folder -> details -> settings permissions. I would set everyone are read only and then add a few authors to have read / write or full control. We also need to set service permissions. Service permissions set who can define approvers along with some other things. If you have the service permission approval maintenance, then you will always be able to see all files. So once again change the service permissions (settings -> service permissions) so that everyone has no service permission except for whoever is administrating the approvers. Finally in settings -> approval you need to enable the approval process (big button enable approval) and assign users, groups or roles to be approvers. These are the people who will be able to approve the documents. So finally I create my iviews. I am going to create two iviews, one for editing and approval and one for displaying the XML forms. Content administration -> Portal Content choose a folder you want to create the iviews in. Then right mouse click -> new -> iview. Choose KM Navigation iview. Give the iview a name, id and prefix then open it for editing. In the dropdown proprt category, choose show all. Scroll down to Layout set (the properties are sorted alphabetically). In layout set property we are going to type in News_Explorer_Approve (no drop down I’m afraid and it is case sensitive – dropdowns in next release please if any product management people are reading this 🙂 ). I have also set the layout set mode to be exclusive. This means that the users cannot change the layout set of the iview if they are allowed to personalise it. Further down in the iview properties I have then set Path to initially displayed folder to point at my News2 folder (once again you have to type it in I’m afraid). This means that it will write any new XML files to this folder and display any XML files that are in this folder. If I preview the iview it looks like this: Notice the approval menu. So the author would submit this document for approval. (I have skip approval because I am an approver administrator). A notification would be fired off to the approvers in the UWL and via e-mail (if it has been configured). They could approve it there or in this iview by clicking Approval -> approve (or reject for that matter). I also create another iview for the end users to display the forms. The iview is exactly the same as the one I have just created except that we choose the NewsBrowser layout set (but still point it at /documents/News2). The only files that will display in this iview are approved files, since the users who will have think iview will have read only access to this folder. So that is an introduction to the flexible user interface. It is quite complex but also quite powerful once you understand it. For you java developers out there, don’t worry, there are lots of additional clever things you can do in flexible user interface using java coding. So from somewhere over the coast of Greenland, I hope that makes sense (I’ve only had two glasses of red wine!) and good luck with playing with flexible user interface.