Skip to main content

Multiple Positions of a single user in Siebel

What is Position in Siebel?

A position represent an actual job position in your organization. It determines the records that Siebel CRM displays to each user. A position can be a formal job title, such as the actual job title that the developer uses. It can also be any descriptive text. For example, Developer 1, Developer 2, and so forth.

To log in to a Siebel application, an employee must be assigned a position. When you create positions and position skills, it is recommended that you do the following:

To determine reporting relationships between positions and parent positions, refer to the organization chart for your company.
Because you choose parent positions as you create new positions, start at the top of the organization chart and work your way down.
Note that there is typically one position that does not include a parent position. For example, the CEO position typically does not report to a higher level.

Multiple positions of a single user:

It is Not possible to assign multiple primary position to the user in Siebel as per current product design.
An employee or partner user of a Siebel application can have one or more positions, of which one is the primary position.
When the user logs in, the user assumes the primary position only and the data access that the position determines.

Temporary Position Change:

User can change the primary/ active position from User Preference screen by navigating to Change Position view.
Once user selects a position other than the primary position, which immediately makes it the active position.
The employee then accesses only the data determined by the new active position.

Changing the active position does not change the employee's primary position. When the employee subsequently logs in, the primary position becomes active.
Data visibility for a user is generally determined by the active position, rather than by a union of the user's associated positions.

Comments

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...