Siebel Realtime Interview Question Answers

Siebel Realtime Interview Question Answers, Siebel Interview for Realtime problem and solutions

High Interactivity Framework Problem.

We faced this problem quite often in Siebel 7.7.
Problem:
When clicking on Pick Applet in Siebel 7.7 application the application IE instance used to crash and we had to reopen the application. It happened only in case we were working with Pick Applet.

Reason:
This error was due to High Interactivity Framework files getting corrupt.
Siebel can operate with two types of framework

• Standard Interactivity
• High Interactivity.

The difference between both the frameworks is how Siebel Client communicates with Server. In case of standard interactivity the changes you make to record are not committed automatically to the database and use has to explicitly save the record and in High interactivity even if you step of the record or screen the changes are committed automatically.
Solution:
Solution of this problem is to go and remove the High Interactivity framework files and open the application again. When you open your application Siebel downloads fresh interactivity file from server.
These are steps you can follow to remove and reinstall the interactivity files
Goto Internet Explorer –> Tools Menu –> Internet Options
Click on Settings Button

Click on View Objects Button

Locate High Interactivity Files

Siebel CRM – How To Call a Workflow Asynchronously?

This Article is about Siebel CRM 7.X Workflows and Runtime Events. It tells you how can we use them to our advantange.
We all want the response time of our Application to be as fast as it can and we do everything that we can to achieve that. Reduce the response time without actually reducing any functionality. Siebel can execute workflows in two ways.

• Synchronous
• Asynchronous

Synchronous Execution : When workflows are executed Synchronously then user gets the control back only when the workflow has finished it execution.
Asynchronous Execution: When workflows are executed Asynchronously then user gets back the control immediately and the workflow is submitted to workflow process manager (WPM) as a job to be executed.

WPM then executes the job later.
Often we have a functionality where large amount of processing needs to be done on an object which user is not going to use access right now. I can explain it with an example.
When user clicks copy button on a opportunity or quote we want certain custom entities to be copied over but which user will not access at that time but later.
So, we can reduce our response time by just copying the quote or opportunity synchronously and placing the code of copying of custom entities in workflow and executing that workflow asynchronously.
There are two way to execute a workflow asynchronously

• Workflow Policy
• Runtime Event and Business Service (BS) Combination

Workflow Policy is pretty traditional method of executing a workflow process.
You create a policy. Enter the conditions Specify the workflow to be executed Generate Triggers
Disadvantages of using Workflow Policy

1. Slow Execution
2. Difficult to setup
3. Not Reliable and Error Prone

Related Posts