We've been doing some development on the very new Siebel mobile connected apps. The Siebel Mobile app is a huge and exciting addition to Siebel CRM. However, Just like all new products, you can expect some product defects in the initial version of the software.
We will be updating this blog with all the bugs we come accross and their workarounds untill we have a permanent solution from Oracle.
Issue: Side effects of custom toggle applet in Siebel Mobile connected apps.
Here is how you can reproduce the Issue -
Create a toggle applet on a Form Applet to toggle on a particular LOV value. Lets say the LOV toggle Value is 'Retailer'
Issue 1 - (New Record renders the applet in Base Mode)
The applet opens in Base mode when the record context is the value (Retailer) used for the toggle in the list applet. However when you create a new record from other types record, this does not happen.
Issue 2 - (Toggling back from the toggle applet, renders the applet in Base Mode)
After you have selected the Toggle, and the toggle applet is active switch back to another LOV so the original applet loads. The applet switches to Base mode instead of staying on Edit mode.
Issue 3 - (Applet switches to List Applet on New record instead of opening the entry form applet) - Happens only in iPhone Mode
Upon creating a new record the applet switches to List mode (without loosing context, which is Ok). You then have to tap on the record again to go to Detail mode to edit/ enter data
Workaround:
The workaround to the above three issues would be to do away with the base mode completely, and have the applet render in Edit Mode at all times. You can do this by simply selecting the Applet Mode to Edit in the View web template items property.
Although, this is not the best approach to have a record editable at all times, especially when using a touch phone/pad. Its the only way that can keep the toggle from not breaking.
Any other workarounds are very welcome!
Cheers!
We will be updating this blog with all the bugs we come accross and their workarounds untill we have a permanent solution from Oracle.
Issue: Side effects of custom toggle applet in Siebel Mobile connected apps.
Here is how you can reproduce the Issue -
Create a toggle applet on a Form Applet to toggle on a particular LOV value. Lets say the LOV toggle Value is 'Retailer'
Issue 1 - (New Record renders the applet in Base Mode)
The applet opens in Base mode when the record context is the value (Retailer) used for the toggle in the list applet. However when you create a new record from other types record, this does not happen.
Issue 2 - (Toggling back from the toggle applet, renders the applet in Base Mode)
After you have selected the Toggle, and the toggle applet is active switch back to another LOV so the original applet loads. The applet switches to Base mode instead of staying on Edit mode.
Issue 3 - (Applet switches to List Applet on New record instead of opening the entry form applet) - Happens only in iPhone Mode
Upon creating a new record the applet switches to List mode (without loosing context, which is Ok). You then have to tap on the record again to go to Detail mode to edit/ enter data
Workaround:
The workaround to the above three issues would be to do away with the base mode completely, and have the applet render in Edit Mode at all times. You can do this by simply selecting the Applet Mode to Edit in the View web template items property.
Although, this is not the best approach to have a record editable at all times, especially when using a touch phone/pad. Its the only way that can keep the toggle from not breaking.
Any other workarounds are very welcome!
Cheers!
