Edit Modes in Siebel Applet Web Templates
The other day I was discussing Applet Toggles with a colleague, and the different techniques (Static and Dynamic). My colleague was looking for a way to limit what the user edits, rather than what the user sees in an Applet. So we spoke about Field Read Only and the other various User Properties that the Siebel Configurator has in their toolkit.
The discussion reminded me of a very interesting technique that is sometimes used in Standard Interactivity applications like eService. I know that it has become fashionable to only think about Open UI and how much it will change things, and most of you know how I feel about that, so I think it would be interesting to investigate Edit Modes in Siebel Applet Web Templates. Specifically, using multiple Edit Mode Web Templates with different Sequence numbers. (1,2,3 and so forth, to quote the Bookshelf).
The Siebel Applet Web Template object in Tools allows us to specify a Type (Edit, Base, EditList in the case of a High Interactivity List Applet, but also Query and New for different layouts when the user triggers New Query or New Record. But there is one other option which has often been ignored. The fact that you can have, for example, 3 different Edit Mode Applet Web Templates.
The plan is as follows. Imagine a requirement where a user must see everything in Read-Only (Base) mode. Then, according to different criteria, the user must be able to Edit certain fields by clicking relevant buttons. For example clicking “Basic Information” means only editing the basic Fields. Clicking “Advanced” or “Other” buttons gives access to certain other Fields for editing. The advantage is of course, only one Applet, not three. And you could apply your own logic to “who can click on which button”.
The same technique is used in eService for example in some of the FINS Applets, to allow someone to click for example a “DOB’ control (Date of Birth) and Siebel shows just that Field as editable, all others are hidden. When the edit is complete, the Applet reverts to it’s original display (Base). So the Sequence is Base is 0, followed by 1,2,3, etc for your different Edit Layouts.
Enough of the talking, here is a quick walk-through to show you how. This example uses HLS Case Form Applet to demonstrate, providing 3 different Edit Mode Templates to let the user focus, task-like, on exactly what they want to do. Cool! Please note that due to location issues this eLearning is without sound – just graphics and text to accompany it. [Edit - sound added 28/1/13 17h30]
Edit Modes in Siebel Applet Web Templates
Edit Modes in Siebel Applet Web Templates Summary
It just goes to show that Standard Interactivity can still teach us a trick or two. You can find more about this and similar concepts in the back of the Configuring Siebel Applications book in the Siebel Bookshelf, adapted from the section about Popup Wizards. If you wish to bookmark the eLearning you can click here.










I, as a user, hate to click on buttons a lot of times to get the work done. So typically I end up using ‘personalization’ to dynamically show or hide applets with relevant fields.
Hi Prashanth K, thanks for your comment. I agree, in the vast majority of cases, less clicking is always better. Personalization is one Siebel engine that can help you dynamically show or hide applets. In Siebel Public Sector and Financial Services portals there are a number of OOTB applets using the technique I mentioned, defining discrete “jobs” that a user has to do. In some cases there are as many as 8 different edit templates, and toggles would not be a viable solution. So sometimes it made a little sense to the developer.
Regards
ODE