Siebel Admin Mode Flag – II – Issue Log
In the last post I described about Admin Mode Flag. However, the Admin mode flag is not always the Best way to go forward. It also comes with lots of perils of its own.
Siebel – Admin Mode Flag
In my last project,we had a requirement of Admin Views, so the admin users if required can change the data from frontend and not going to backend and running update queries.
Admin Views are those views in which all the records are visible to the person who has access to this view irrespective of the position of the person.
Siebel – SIS OM PMT Service
There are lots of vanilla business services available in Siebel which can be used to configure any process and this helps in avoiding scripting.
One of these services I came across is “SIS OM PMT Service”.
Siebel – Unable to login to mobile client
After long time I am writing a blog…
This time related to Siebel Admin ![]()
Earlier I used to work with Siebel 7.8 and now 8.1..
So quite a different experience..
In Siebel 8.1, I had successfully initilized my dbf from tool and was able to login into Siebel Tools.
But suprisingly, using same dbf I was not able to login to my mobile client and it was throwing the error,
“user id /password not correct..”
Siebel- Close Browser window when logging off
In case of standard interactivity applications like eSales , eService, when user logs off, he is directed to the page through which he logged in the application. But there is a requirement to close the IE when user logs off. Here we are doing this for eSales Application. This can be done in following manner:
• Create a new .swt file say “LogOffDestination “ which contains following HTML script:
<html>
<head>
</head>
<body>
</body>
Siebel – HTML Code displayed in Error Message
There was a requirement in our project to make Account Field required in Quote entity conditionally. I have already discussed the solution to this and to show the red asterisk in my previous posts below:
Making a field conditionally required
Showing * on a conditionally required field
When user was creating record from list applet and on saving the record he got the right message as “Account is a required field”.
But to our surprise, when record was being created from form applet and now if the user saves the record, he got the following message..
Siebel – Showing red asterisk on a conditionally required field
In Siebel vanilla Application, we see a red asterisk ( * ) in case the field is Required. However, this asterisk is not shown in case the field is made required conditionally through customization.
We had a similar requirement, to show the red asterisk against a field in the form applet, which was required conditionally. I have already discussed how to make the field read only conditionally in my previous post.
Siebel – Make a field Required, conditionally
There was a requirement in our project to make Account Field required in Quote entity conditionally. Had it not been optional, we would have done this by the setting the ‘Required’ property to TRUE for the field in the applet. But, then it would not be conditional, and would always be required.