Create your Own Object Manager

Create your Own Object Manager

Steps:

1. Create a New Component Group with the following Details:

Name	SSA Custom Group
Alias	SSACustomGroup
Description	This component group is created for testing and learning the concept and practice of creating our own object manager in using it through application

Note: This component group does not have any component inside it. But the state of this group is enabled.

2. Now let’s create a component definition to add in this group.

a.      Click the Component Definition tab and query for * Call Center *.

b.      From the Applet Level Menu or Press Ctrl-B to copy this record.

c.       Change the Values from the below table.

Name	SSA Custom Component ObjMgr
Alias	SSACustomComponentObjMgr
Component Group	SSA Custom Group
Description	This is the newly create Object manger.

Note: Component parameters are populated once you step out or save the record.

a.       Activate the component by clicking the Activate Button.

b.      Click back to Component Group tab and Query for SSA Custom Group. Now notice that one component is added in this group.

3. Now let Enable and test this group. All we need to do is that, Edit eapps.cfg file to test the object manager.

a.       Assign the Component group on the server and enable it.

b.      Restart your Siebel Server by going to Services Window.

4. Now lets edit the eapps.cfg to replace the existing object manger with new one which we have just created it.

a. Go to the Installation Directory of Siebel Web Server Extension and Bin directory. Create a backup copy of your eapps.cfg before you start editing it.

Now Search the following String in the file:

            [/callcenter_enu]

c.       Change the connection string parameter with new Object Manager Definition.

[/callcenter_enu]

ConnectString = siebel.TCPIP.None.None://R0346:2321/OUEnt/%Place Comp Name%

d.      Save the file and Restart the IIS admin service.

5. Open internet explorer and type the following url to test it.

http://localhost/callcenter_enu

Siebel Master Data

Master Data

Objective - To learns Siebel master data.

Introduction - In Siebel there is two types of data- 1.Customer Data

                                                                                    2. Master Data

1. Customer Data is dynamic, transactional type of data.

    It is managed by organization ownership, position and id.

Examples: service requests, opportunities etc.

2. Master Data is static, referential type of data.

   It is monitored by administrator.

Examples: literature, partner programs, competitors etc.

Explanation-

      To administer Master Data catalogs & categories can be used.

      The visibility of data can be determined by catalogs & categories.

          Eg. customer documentation for credit card accounts

Catalog: It contains hierarchy of categories. It does not contain direct data but acts as container for the categories. It can be marked as private.

      

ü      Public catalog can be visible to all users.

            We can mark individual categories private under public catalogs.

ü      Private catalog has visibility for only defined access groups.

Catalog should have catalog types. Seed catalog types are infocenter, customer, etc.

Categories: these are nodes of catalogs. Can have subcategories under it. It contains master data. They can not be shared between catalogs. But the different catalogs can have same names of categories.

If a category is declared private, all of its subcategories are also private. Their visibility can be managed by access groups.

Access Groups & Access Control: It is collection of positions, organizations, user lists, households etc.

 It can’t contain individuals. We have to create user list (In applicationà Administration-group- user list.)

 These can be organized in the hierarchy. Child has more privileges than parent as it inherits the access of  parent.

For controlling access assign access groups to catalog & categories.

Eg- Access groups-for catalog “ credit card customer ”,then the categories under it like “gold”, ”platinum”,” silver”.

The access groups under categories (child) have more access than catalogs (parent).

An access group can only be added to a category if:

 The access group is also assigned to the category’s parent, or  access group is a child of an access group assigned to the parent.

Removing parent access group removes all subsequent access from children.

Steps to create catalogs and categories.

1. Create the Catalog

Go to Admin-catalog-create new. Add name,type, active.

2. Add Categories to the Catalog

Drilldown  catalog. Add categories. Use promote/demote to make subcatagories.

3. Associate Master Data with Categories

Add data like literature, product, curriculum, solutions etc.

4. Declare Catalogs or Categories Private

By checking private flags make intended  categories,subcatagories private.

5. Create Access Groups

 Create access groups Admin – Group Access- Groups, parent access groups,add party (organization/userlist/etc.)

6. Assign Access Groups

Assign it to catalogs and categories.

  

    

How to invoke a Siebel Business Service

Business Service (BS): Is a place where you write to code to implement business rules and process.
We can also write the code at Bus Comp and Applet level but that makes our code and business logic to be
           • Distributed
           • Difficult to manage
           • Cannot be reused
Siebel Business service has a slight more overhead than the code at Applet or Bus Comp level but it helps us to make our code
            • Centralized
            • Easier to manage
            • Can be reused
So general rule of thumb to select where to write the code is
If same business rules are applicable on more than one entity then we write a generalized code at BS level.
You can create business services in
Siebel Tools: Code change is SRF dependent.
Siebel Client: Code change is SRF independent.
You can read more on both kinds of business services in the following post.
We can invoke a business Service through
1.    Runtime Events
2.    eScript
3.    User Property
4.    Runtime Events

To call a business service through runtime events
Enter the following information in the Action Set that you are creating
Business Service: Business Service Name
Business Service Method: Method Name
Business Service Context: “Input Argument”, “Value”
And based on the Event that you choose this business service will be invoked


• eScript
You can use the following Code to invoke a business service from escript
var svc = TheApplication().GetService(“BS Name”);
var Input = TheApplication().NewPropertySet();
var Output = TheApplication().NewPropertySet();
Input.SetProperty(“Type”,this.GetFieldValue(“Status”)); // Input Agruments
svc.InvokeMethod(“BSMethod”, Input, Output);


•    User Property
You can use named method property to invoke a business service from BC but this method is rarely used as it including complex conditions in the User property might not be possible. But it can come quite handy if you just want to invoke BS based on simple conditions

Name: Named Method 1
Value: “New Record”, “INVOKESVC”, “BS Name”, “BS Method”, “‘Input Agrument’”, “Value”, “‘Input Argument 2’”, “Value”

Invoke a Workflow using Custom Buttons

******* Invoke a Workflow using Custom Buttons *******

Create the Workflow as per your requirement.

1- Validate it to ensure there is no error.

2- Publish and activate the workflow.

Create button and write a code to invoke workflow.

1 - Create a Control and Assign the following properties:

            - Name , Display String Override , Runtime , MethodInvoke : "CallWF"

2 - Invoke the Web Layout.

            - Place the button on form.

3 - Write a Applet Server Script to Call the Method and Enable the button.

            function WebApplet_PreCanInvokeMethod (MethodName, &CanInvoke)

            {

                        if(MethodName == "CallWF")

                        {

                                    CanInvoke="TRUE";

                                    return (CancelOperation);

                        }

                        return (ContinueOperation);

            }

4 - Create Applet User Property :

            Name : Named Method: CallWF

            Value : 'INVOKESVC', 'Workflow Process Manager', 'RunProcess','"ProcessName"', '"%Name of your workflow here%"', '"RowId"','[Id]'

5 - Test the Record

           

Data Validation Manager Part 1

Data Validation Manager

1 - Whenever user creates a new Service Request you need to ensure that he write a summary about it.

So here lets process it with DVM Concept. (Data Validation Manager)

Let Begin the Practice with Simple Example as mentioned above:

1- Open Siebel Call Center Application and Loing with SADMIN with Connecting to Sample database.

2 - Go to Administration - Data Validation Screen and Enter the Following Details

            1 - Lets Create a Validation Message First:

            Message Code : SR101

            Message Level : Service Request         

            Message Source : SR Validation Process

            Message Text : Service Request must have a summary.

            2 - Lets Create a Rule Set to enforce our business policy.

            Name : AUT SR Validation

            Business Component : Service Request

            Business Object : Service Request

            3 - Click[Rules Tab] in the bottom Applet and Define your rule.

            Name : Description Validation

            Expression : [Abstract]IS NOT NULL

            Business Component : Service Request

            Apply to: Current Record

            Start Date: Today's Date

            End Date : As per your wish

            Retrun Code : SR101

           

            4 - Goto Rule Details Tab and Check the following Property to prompt the Message.

                        - Stop on Error : True

                        - Immediate Display : True

 3 - Now Lets call our Validation rule using a Data Validation Manager Business Service using Workflow Process.

            1 - Create a Workflow with the following Property:

                        Process Name :

                        Project :

                        Business Object :

            2 - Drag following steps from platte.                 

                        - Start - Business Server - End

3 - Configure the Step as per the given images. 

    

4 - Validate the workflow to ensure that you don’t have any error.

            5 - Publish and activate the workflow.

4 - Login Back to Siebel Call Center Application to Reload the runtime Events.

            - Administration - Runtime Events

                        - Click on Events

                        - Click on Menu and Select Events.

5 - Create a Test Record and Check it.

To display Birthdays of Contacts

1.      Create Control on Contact Form Applet and Map with Birth Day Field.

2.      Create new applet named Birthday Applet based on Contact BC and Place it in Home Page View  (WCC)

3.      For  Birthday Applet set Search Specification as below,
JulianMonth([Birth Date])-JulianYear([Birth Date])*12 = JulianMonth(Today()) - JulianYear(Today())*12  AND JulianDay([Birth Date])-JulianYear([Birth Date])*365 = JulianDay(Today()) - JulianYear(Today())*365

4.      Compile and Test

 

 

User Properties

User Properties Examples