Scribd
Upload
46 views

SiebelInterviewQuestionsWorkflow

Uploaded by

priyankachauhan1828
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
46 views

SiebelInterviewQuestionsWorkflow

Uploaded by

priyankachauhan1828
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Siebel Workflow Questions

• What is a Siebel Workflow?


A Siebel Workflow is a sequence of tasks that automate business processes within the Siebel
application. It defines the flow of data and actions based on specific conditions.

• What is a Siebel Workflow Policy?


A Workflow Policy is used to automate actions based on specific conditions. For example,
you can create a policy to send an email notification when a service request status change.

• Differentiate between Workflow Policy and Workflow Process.


Workflow Process is used to automate business processes, whereas Workflow Policy is used
to trigger workflows based on specific conditions

• What are the different table that are invoke when Workflow Policies process
requests?
1. S_ESCL_REQ
2. S_ESCL_ACT
3. S_ESCL_LOG
4. S_ESCL_STATE

• Explain the difference between Synchronous and Asynchronous Workflows?


Synchronous Workflows execute in real-time and hold the user session until completion.
Asynchronous Workflows are triggered and run in the background, allowing the user to
continue working without waiting for the workflow to finish.

• What are the different table that are invoked while we are Runing Asynchronous
Workflows using Server Request Business Service?
1. S_SRM_REQUEST
2. S_SRM_DATA
• How do you handle looping in a Siebel Workflow
Looping can be achieved using Decision Steps and conditional branching. Evaluate conditions
and use Decision Steps to loop back to a previous step or move to a different branch based
on the outcome.
1. NumAffRows Output of Query Step and
2. NoMoreRecords Output of Next Method can be used to form the conditions

• How can you implement exception handling in Siebel Workflow


Explain techniques for handling errors and exceptions within Siebel Workflow processes to
ensure proper error logging and recovery mechanisms. It’s achieved via
1. Red Connectors
2. Stop Step

• What are the default Process Properties in Workflow, that are created by default.
1. Error Code
2. Error Message
3. Object Id
4. Process Instance Id
5. Siebel Operation Object Id

• What is the Significance to give a BO in Siebel Workflow


BO maintains below access,
1. Data Context: The Business Object defines the data context for the workflow
process.
2. Record Instances: This means the workflow can interact with and manipulate
records within the associated business object.
3. Field Access: The association with a Business Object allows the workflow to
access and manipulate fields within

• Can there be Workflows without a BO in Siebel


Technically yes, but as mentioned earlier the Workflow will not have the context and
will not be able to perform any Siebel Operations. Though we can call other child
workflows and Business Services in that workflow.

• What is the difference between the End and Stop step of Workflow
the "End" and "Stop" steps both serve the purpose of terminating the execution of the
workflow process, but there are some differences in their behaviour and usage:
1. End Step: is used to explicitly indicate the normal completion of the workflow
process. When the workflow execution reaches an "End" step, it signifies that
the entire process has successfully completed, and there are no errors or
exceptional conditions
2. Stop Step: is used to terminate the workflow process abruptly, regardless of
the execution status or completion state of the process. When a workflow
execution reaches a "Stop" step, it immediately halts the execution, and the
process is considered stopped.

• What is difference between workflow Process Manager and Workflow Process Batch
Manager
Workflow Process Manager is focused on real-time, online execution of workflows that
respond immediately to events triggered by user interactions or business processes.
On the other hand, the Workflow Process Batch Manager is designed for batch
processing, handling workflows in the background, and is well-suited for scenarios
involving scheduled, asynchronous execution or bulk operations. i.e. RCR’s

TIP: Refresh concepts around Workflow Policies and Asynchronous Workflows from
Bookshelf
If you do not get the answer to these Question, please mail to
enquiry@expertcrmservices.com, we will be happy to explain.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy