Hide Applet Control / List Columns At Runtime

Applet User Property "HIDE CONTROL" which can help you to hide Applet Control / List Columns at Runtime.










This user property set in Applet allows you to hide some control/List columns at runtime.




Syntax:
Name: Hide Control
Value: Control to hide, Condition
So in the below screenshot configuration NewRecord button will be hidden if Account record is present on that applet.
This User property could be based on class and so far I have explored it works only in Order Management realm.

Predefined Queries (PDQs)

Predefined Queries (PDQs) feature is one of the best user friendly feature of Siebel application. User navigate to a view and query some data to get related records. In his daily work he will apply same query to filter the data of his need. Now what if he can see the filtered data by default as soon as he navigate to that view. Here comes the concept call Predefined Queries (PDQs).

User can write a PDQ and this will give him filtered data once he will navigate to the view. These stored PDQ's can be find at the drop-down box at the top - right side of application. Various set of PDQs can be written and stored for a view.

PDQs are of 2 type. Private and Non Private. 

Prior to 8.0 release one had to add DisablePDQView = “Name of the view to be disabled” in cfg file.

But yearlong oracle supports effort to minimize configuration file dependency resulted in creation of this Application Level User Property.

To set this up go to Tools – Application -> Application user Property.
Create new record as follows.

Name: PDQDisabledViewn
Value: Name of the view to be disabled
n is a number, As we can see in tools that this property is used for few views and let say it has been used for 4 views that means PDQDisabledView0, PDQDisabledView1, PDQDisabledView2, PDQDisabledView3 are already there then the new property will be added as PDQDisabledView4
For Example:
PDQDisabledView4 = Order Approval View (eSales) 

Navigating Backward

Scenario:

Navigating backward is a fair ask by customer, who has migrated from simple web based application to siebel.

Solution: 

There are multiple ways to achieve this.

·         Some of the OOB business services which could be used to achieve this are "CUT eSales Order Entry Toolkit Service" or "FINS Goto View Service" which has got "GotoView" method which can be used to navigate to destination while maintaining the context

·         Siebel makes use of underline java script functions to go to previous page. It can come handy in many scenarios. Following code could be used on browser side of applet for going backward.

if(name == "Back")

{

history.go(-1);

return ("CancelOperation");

}

Or

if(name == "Back")

{

window.history.back(-1);

return ("CancelOperation");

}