Siebel allows keyboard to perform some functionality such as scrolling up and down arrow key for moving to next record and previous record respectively in list applet and Pg Up and Pg Dn key to navigate to next set and previous set of records in applet respectively. Let’s see how to configure this Keyboard accelerators functionality.
Keyboard accelerators are nothing but short cut keys used to invoke some functionality in the application. Users are sometimes so familiar of using the keyboard buttons that they don’t want to go for mouse to navigate from one record to another or to click on some button as this may become time consuming and hence reduce their productivity. In such cases we can enable these functionalities on the click of the buttons on the keyboard.
To illustrate with an example lets consider the PageUp and PageDown buttons. We all are very much aware of the functions of “Page Up” and “Page Down” buttons available on the key board. We can navigate Up and Down using these buttons on a page. But there may a requirement to use the same buttons to navigate within a bunch of records in a List applet. Some times user wants to use “Page Up” and Page Down” buttons in the key board to navigate to next set or Previous set of records in a list applet.
Here is when the accelerators come into picture as they accelerate the work and hence the Productivity of the users. We can easily achieve this with a little configuration. Detailing out the steps here — Open the Siebel Tools and go to the “Command” object definition in the “Object Explorer” and create a new Command.
Mention the “Method” name (any name) for the new Command. Now go to the “Accelerators”, the child object definition of “Commands” and create a new record. Mention the “Name”, “Key Sequence” for the “Accelerators”. PGUP Key Sequence for “PageUp” Button; while for “PageDown” the Key Sequence would be PGDN .
“Key Sequence” is the key from the key board on which the required functionality need to be implemented. There are set of key words for different keys as follows. They are not case sensitive.
Now navigate to the Applet object definition and add the “command” Name in the “Applet Method Menu Items” child object definition of the Applet.
You need to add server script in the Applet PreCanInvoke Method and PreInvoke Method to perform different task for the defined method as below (script below needs to be modified as per the command and the logic behind it) PreCanInvokeMethod
Once this is done compile all the objects ie the applet and the commands used and login to the application. Navigate to the List applet where you want to implement this. Make sure you have more than one records in the List applet. Now focus on the top record and hit the “Page Down” button on keyboard. It will take you to the records below, similarly if you hit the “Page Up” button it will take you to the record above. You can see these accelerators along with the short cut key sequence in the Menu items on the same applet.
If you don’t want to display these key sequences in the UI, you need to keep the “Display Name” empty under the Accelerator Locales.
Since accelerators are mapped directly to commands, the scope of the actions represented may be specific to the currently active applet, or it may apply to the application session as a whole. For example, an accelerator to initiate a new query will have specific focus on the current applet, while an accelerator to invoke the Site Map page is independent of the current application context. We can also use accelerators for invoking functionality behind a custom button. I will flash light on the same may be later in the next posts.