Siebel Open UI, Tools, Scripting and EAI (MOSC)

MOSC Banner

Error in opening thick client when setting user's default queries via eScript

edited Mar 25, 2014 11:38PM in Siebel Open UI, Tools, Scripting and EAI (MOSC) 5 commentsAnswered ✓

Hi,

We have a requirement to automatically create the user's default queries with in User Preferences so all the users in organization have similar set of default queries executed when ever they navigate to Case and Task view and also because the default queries overrides any user created PDQs even if the user PDQ alphabetical order is lesser than default queries. So For eg:

Default Query name: All Activities

User PDQ name: AAA

Even if the user PDQ AAA comes before All Activities, whenever navigates to Task view 'All Activities' should take precedence and should executed by default

The solution we have implemented for this requirement is based on a eScript which gets triggered on Application Start. We have created a LOV Type where we store the the default queries name along with the View and screen name. In our eScript we pick the default query name from LOV and stamp it against user's default queries in User Preferences. The script works perfectly fine when we login to the thin client and correctly sets the default queries for the user. However when we login to the dedicated client we see our view access has been restricted. I have

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center