Configuring a Wireless application is very much like any other app development task in Siebel Tools. The Wireless application is made up of a number of object types. Again, I’m using Service as an example, but this could be substituted for Sales or whatever:
- Application (Siebel Service Wireless)
- Screens (*SWLS Service*)
- Views (*SWLS Service*)
- Applets (*SWLS Service*)
Applets and Views are named according to the relationship that they represent (parent / child) and whether they are list (Display) or form (Detail) type . For example:
SWLS Service Account Activity Display View
This is the Wireless Service (SWLS Service) view that for a parent Account will show a list of Activities
Applets, Views and Screens are all built up in the same way as you’d expect and use a specific Wireless Web Template to allow display on the smaller device screens. Drill down, via Drill Down objects, Picklists are all supported out of the box. More complex functionality, such as buttons, are handled via User Properties on the applet level controls. Note that these are currently undocumented, so a degree of trawling through the vanilla configuration is unavoidable. You’ll soon understand what’s going on but analysis of the existing config against vanilla functionality is highly recommended.
Here are a few useful tips:
- Application Screen objects determine what will appear in the Home screen – add items as Page Tabs and ensure the Responsibility contains appropriate Views
- Views are standard though are made up of single applets
- Applets are standard and made up of two to three fields, as List Columns, or many fields as a form. Controls and List Columns on the applets use a set of specific Wireless User Properties, including:
- Page – a link to return / navigate to a specific Web Page
- View – a link to a specific View
- KeepContext – determines whether to keep the BO context when navigating
- Popup – whether this displays a popup window
- UseParent – allows displaying of a parent field value on a child applet (SR number of a list of Activities, for example)
- Drill down objects work in the same way as normal to provide drill downs to other views
- Child ‘view’ items are defined as controls on the applet, with a ‘View’ user property
- Applets will apply search spec as per Bus Comp definition but will ALSO apply the default PDQ!
My recommendation is to modify existing applets and copy existing applets instead of creating new ones from scratch. When creating my Case configuration, I copied the existing Service Request objects and modified them accordingly.
Give it a go and feel free to post comments with problems or success stories!