<< Previous in series
Continuing with the series I would like to explain some things about Siebel Open UI Presentation Model.
1. What you see is what you get.
This is the most important limitation according to me for the presentation model. It doesn’t matter which API function you use you can only get value of a field that has been exposed on UI. There are basically two way to get field value in PM.
- Execute Method – GetFieldValue: Have a look at the following code
This function needs a control (object) as an argument. You get this control object through “GetControls” method of PM and GetControl method only returns the controls that are available on UI.
To use this method you will have to have business component object but here also buscomp object has access only to the fields that are displayed on UI.
This is important limitation because if you would like to write a complex business logic in PM then you will have to either call a Workflow/Business Service or have all the fields that are needed for logic on UI (probably in hidden mode).
2. IE 11/10 issues
Can you believe it? IE used to be most stable browser for Siebel and now I have seen plenty of issues while using PM API’s in IE 11/10. Below are few important API’s that I have seen issues with:
- WriteRecord: When used through PM API (ExecuteMethod) WriteRecord either doesn’t work or causes issues in functionality
- HandleRowSelect: This function is suppose to choose desired record as is needed when you change the visualization of applets for example for list to tiles but it doesn’t work in IE 11
I haven’t had a chance to use other API functions as of yet but I am sure there will be plenty more.
On a separate note, after applying patchset 7 another severe defect (18762041 and 18762425) is introduced where you are not able to open multiple thick client sessions and you get:
Siebel Web Session
‘chrome.exe’ Browser session is still open. Please close all the browser sessions before launching Siebel Mobile Web Client.
In fact if you are using shared server then opening a session by one person would prevent anybody else opening a thick client session. The only solution at this time is to uninstall PatchSet 7 and move to the lower version which basically renders patchset 7.
It is though possible to keep tools and client on Patchset 5/6 and still move server to patchset 7. That is what we have done and haven’t seen any issues with it.
I hope this helps!!! Keep reading.
<< Previous in series