3Administering Siebel Public Sector
Administering Siebel Public Sector
This chapter describes the general tasks that administrators perform for Siebel Public Sector. Other chapters in this guide describe the tasks that administrators perform for the specific functionality that is included in those chapters. This chapter includes the following topics:
Administrative Tasks for Siebel Public Sector
The following table lists and describes the administrative setup tasks that are specific to Siebel Public Sector and the tasks that might differ from those of the other Siebel Business Applications. The table also directs you to documentation that provides information about each task. When setting up Siebel Public Sector, use this table with Siebel Applications Administration Guide.
Siebel Applications Administration Guide includes information about the setup tasks that are common to all Siebel Business Applications, such as using license keys, defining employees, and defining your agency’s structure. It also provides the needed information to perform data administration and other administrative tasks.
Some tasks in this table might replace the corresponding tasks in Siebel Applications Administration Guide, and others might be additional tasks. For instructions about how to create the Siebel Administrator account that the administrator uses to perform the administrative procedures described in this guide, see the Siebel Installation Guide for the operating system you are using.
| Administrative Task | Description | For More Information |
|---|---|---|
Activity plan templates |
If your organization uses activity plans with predefined activities, then you must set up these templates. You can set up activity plans for cases, service plans, leads, and evidence. |
Siebel Applications Administration Guide |
Approval templates |
If your organization wants to have predefined approval templates available for users, then you can define these templates in the Administration - Case screen. |
|
Assessment templates |
If your organization mandates specific assessment criteria, then you must set up assessment templates with attributes. You can set up assessment templates for cases and incidents. |
Siebel Applications Administration Guide |
Assignment Manager |
If your organization wants to automate the assignment of case- and immigration-related activities, then you can use Assignment Manager’s predefined assignment objects. |
Assignment Manager and Siebel Public Sector Siebel Assignment Manager Administration Guide |
Data loading and integration |
If your organization wants to integrate with other database applications or perform periodic batch imports and exports of data between the Siebel database and other applications, then you can perform these tasks using Oracle’s Siebel Enterprise Integration Manager. Using Siebel Enterprise Integration Manager, you can work with the following objects and associated components:
|
Siebel Enterprise Integration Manager Administration Guide Transports and Interfaces: Siebel Enterprise Application Integration Business Processes and Rules: Siebel Enterprise Application Integration Siebel Object Interfaces Reference |
Embedded analytics |
If your organization uses Oracle Business Intelligence and wants to configure embedded analytics for Siebel Public Sector, then you can integrate Siebel Public Sector with Oracle Business Intelligence. |
|
Home page image |
If your organization wants to maintain a graphic that appears on the Siebel Public Sector home page, then you can perform this task using the Home Page Image Administration screen. |
|
iHelp |
If your organization wants to set up iHelp to provide real-time task assistance to users, then you can use the iHelp tool to embed view navigation links and to highlight fields and buttons on the views that are associated with each step of the task. |
Siebel Applications Administration Guide (developing and administering iHelp) Siebel Fundamentals (using iHelp) |
Lists of Values (LOVs) |
If your organization wants to create standard LOVs (for example, for Case Type and Stage, Case Status and Sub-Status), then you can create and modify these lists of values. |
Siebel Applications Administration Guide |
Literature setup |
If agents in your organization select literature for distribution records, then you must create these records using the Literature view of the Administration - Document screen. |
Siebel Applications Administration Guide |
Location setup |
You can create location records and associate new or existing addresses with each location using the Location view of the Administration - Data screen. |
|
Mobile synchronization |
If agents in your organization use mobile devices, then the following objects and child components are activated on the mobile devices with the noted visibilities:
Each object has partial visibility to all child components. |
Siebel Mobile Guides on Siebel Bookshelf |
Quickfill templates |
If your organization wants to create standard templates for commonly used Incident and Case types, then you can create Quickfill templates. Users can apply templates from the Case and Incident forms by selecting Apply Template, Save as Template, New from Template, or New from Last Template in the menu that appears when they click the cogwheel icon in the forms. |
Siebel Applications Administration Guide |
Responsibilities |
If your organization wants to restrict view visibility for users to conform to user responsibilities, then you can assign responsibilities to users. |
Siebel Security Guide Siebel Applications Administration Guide |
Serialization rules |
If your organization wants to change the serialization rules that are preconfigured in Siebel Public Sector, then you can edit the rule definitions using the Serialization Rules view of the Administration - Case screen. Depending on your changes to the default serialization rules, you might also have to configure the appropriate business objects and components in Siebel Tools. |
|
Siebel Tools |
If your organization wants to change or create new Siebel Public Sector fields or field properties, change colors and controls in Siebel Public Sector, and add or remove applets, then you can perform these tasks using Siebel Tools. |
Configuring Siebel Business Applications Siebel Developer's Reference Siebel Tools Online Help Using Siebel Tools |
Time entry constraints |
If your organization wants to specify the period of time that users are allowed to assign time to a case or incident after that case or incident is closed, then you can configure constraints for time entry. |
|
Time entry views |
If your organization wants to designate the time entry views in which users can assign the time of other users to cases and incidents, then you can configure the time entry views. |
|
Workflows for business processe |
If your organization wants to design and implement automatic workflows for business processes, then you can use the Business Process Designer. You must activate some predefined workflows. |
Activating Siebel Public Sector Workflows Siebel Business Process Framework: Workflow Guide |
About Serialization Rules
Siebel Public Sector can use configured serialization rules to stamp a new case with a unique, customized serial number. This serial number is generated from a combination of fields so that the numbers are meaningful to an agency. For example, in the case serial number NY-2B-296-3964041, the serial number denotes a geographic territory (NY for New York), a case category (2B for aggravated assault), and the case number (296-3964041).
Case serialization also serializes evidence, leads, and attachments associated with the case. Using the case serial number in the preceding example, the serial number generated for an evidence item might be NY-2B-296-3964041-296-3964055. The evidence item inherits the parent serial number and uses the evidence number for the evidence item.
Serial numbers for cases, leads, and evidence are generated automatically when the user saves a new record. In some instances, the user can also generate a serial number by clicking a Serial Number button, for example, in the Attachments view in Case List view of the Cases screen. For more information, see Adding Attachments to Cases.
To use the serialization feature for Siebel Public Sector, you must make sure that the PUB Enable Serialization system preference in the System Preferences view of the Administration - Application screen has a value of Y.
Siebel Public Sector provides several rules that you can configure to control the format of serial numbers on cases, leads, and evidence. The following table describes the preconfigured rules.
| Rule | Description |
|---|---|
Case Rule |
Determines the serialization of cases. The Case Rule pulls the user’s entries from the Territory and Category fields in the Cases screen. For example, if the user selects New York as the territory for the case, then the category code NY is included as part of the generated case serial number. The information from the Territory and Category fields is stored in the HLS Case business component’s Territory Code and Category Code fields. The value in the Case Number field is also selected for this rule to add numbers at the end of the serial number. By default, the HLS Case business object is serialized as the parent object. The Case Rule is the parent rule for all the other rules. For more information, see Parent and Child Serialization Rules. This rule is triggered when the user successfully saves a new case record. |
Case Lead Rule |
Determines the serialization of leads associated with a case. This rule is a child of the parent Case Rule. It is triggered when the user successfully creates a new lead record, a task that includes selecting an associated case. |
Case Evidence Rule |
Determines the serialization of evidence associated with a case. This rule is a child of the parent Case Rule. It is triggered when the user successfully creates a new evidence record, a task that includes selecting an associated case. |
Case Attachment Rule |
Determines the serialization of attachments to case records. This rule is a child of the parent Case Rule. It is triggered when the user clicks the Serial Number button in the Attachments view in the Case List view of the Cases screen. For more information, see Adding Attachments to Cases. |
Evidence Attachment Rule |
Determines the serialization of attachments to evidence records. This rule is a child of the parent Case Rule. It is triggered when the user clicks the Serial Number in the Attachments view in the Evidence List view of the Evidence screen. |
Lead Attachment Rule |
Determines the serialization of attachments to lead records. This rule is a child of the parent Case Rule. It is triggered when the user clicks the Serial Number in the Attachments view in the Lead List view of the Leads screen. |
Lead Sub-Lead Rule |
Determines the serialization of leads associated with a parent lead. This rule is a child of the parent Case Rule. It is triggered when the user successfully creates a new sublead record, a task that includes selecting an associated case. The user performs this task in the Sub-Lead view in the Lead List view of the Leads screen. |
Parent and Child Serialization Rules
Parent rules are rules generated from serialization on an independent business object and component. The serial number that the rule generates is unaffected by the serial numbers that other rules generate. By default, the Case Rule is the parent rule for the serialization rules provided with Siebel Public Sector. For a description of the Case Rule, see About Serialization Rules.
Parent rules can have several child rules. Child rules include serial numbers already generated for the parent rules. For example, the Case Attachment rule is configured so that it begins with the serial number that the Case Rule generated. Its first attribute type is Parent Serial Number. For more information, see Serialization Rule Attribute Types.
Serialization Rule Attribute Types
The following table describes when each attribute type is used for generating serial numbers.
| Attribute Type | Description |
|---|---|
Field |
Select this value to extract information from the selected business component field and include this information in the generated serial number. |
Constant |
Select this value when you want to insert an attribute separator in the serial number. Examples of constant values are hyphens (-) and periods (.). For example, a case serial number with the format: Territory Code + Constant + Category Code + Constant + Case Number field value might appear as NY-7A-296-3964041 if you use hyphens as the two constant values. |
Parent Serial Number |
Select this value when you want the parent rule’s serial number included in the current rule’s serial number. By default, all the rules generate a serial number that begins with the case serial number that the Case rule created. For example, the Evidence Attachment Rule attributes are defined as Parent Serial Number, Constant, and Evidence Id field value. |
About Editing the Default Serialization Rules
Siebel Public Sector provides you with several preconfigured rules that you can modify to suit your organization’s requirements. You can also create new rules to change how serialization is performed. For more information, see Adding New Serialization Rules.
If you modify the default rule values to extract information from different fields, then users must make sure that they enter all the information required to generate the serial numbers. For example, you change the Case Rule to include the Sub-Status value in the serial number instead of the Category Code. The user must select a value in the Sub-Status field so that a serial number can be generated for a case. If you do not change the rules, then Siebel Public Sector populates default values in the required fields so that these fields are not missing data.
Guidelines for Serializing Additional Parent Business Objects
The serialization rules provided with Siebel Public Sector are based on case serialization. HLS Case is the business object for the parent rule, Case Rule. You can edit these rules to generate serial numbers in the format that your organization requires. For more information, see About Editing the Default Serialization Rules.
However, if serialization must be performed on certain items independently of the Case Rule, then you can configure serialization on additional parent business objects.
The business components that are based on the CSSBCBase class support serialization. Observe the following guidelines when configuring serialization on additional business objects and components:
Business components to be serialized must contain a Serial Number field.
You cannot have more than one rule that is based on the same business object and business component.
You must define serialization rules and attributes in the Serialization Rules view of the Administration - Case screen for any additional serialized business objects and components.
If you create new rules to replace the default lead or evidence serialization, then you must delete the appropriate default rule.
For example, you can create a new Lead Rule and Evidence Rule to use instead of the default rules (Case Lead Rule and Case Evidence Rule) to serialize leads and evidence. These records have PUB Evidence or PUB Lead as a parent business object and, unlike the current rules, do not have the Case Rule as a parent rule. If the user creates a new evidence record, then the evidence serial number that is generated is based on only the defined attributes. The number does not include any reference to the case serial number.
When you add new columns to the tables, make sure these changes are reflected in the Siebel database. For more information, see Using Siebel Tools.
About Approval Templates and Routing
Inboxes serve as a consolidated work space for all cases, leads, and incidents that are routed to the appropriate users for approval. Automatic approval routing increases the efficiency of the approval process and reduces case, lead, and incident backlog. Administrators configure approval templates to automate the routing of approvals. For more information, see Process of Setting Up Approval Templates.
Siebel Public Sector approval routing allows for a tiered hierarchy of approval, routing cases, leads or incidents to a manager, group manager, division manager, and others within the chain of approval. The approver list can also include cross-departmental approvers. For example, users might need approval from a finance manager and a case manager before making payments relating to any case. Users cannot approve their own cases, leads and incidents.
Also observe the following guidelines for approval templates:
If an approval template has multiple approvers with the same sequence number, then when you submit a case, lead, or incident that uses the template for approval, the case, lead or incident is routed to only one of those approvers. Consequently, make sure that approvers are appropriately ordered on the template.
If an approval template has no approvers, then when you submit a case, lead or incident that uses the template for approval, the case, lead, or incident is never approved because it does not appear in anyone's inbox. Consequently, make sure that all templates have at least one approver.
The approvers that administrators add to a template are included in the case, lead or incident when you pick the template. Any changes to the template approvers have no effect on cases, leads, or incidents for which you already selected templates.
If you select a different template, then the approvers for the case, lead, or incident are refreshed.
About Location Tracking
Using Oracle’s Siebel Location Tracking, agencies can standardize locations with multiple addresses, such as malls, hotels, office parks, and campuses. Users can also specify an area that does not have address information, for example, a street intersection or the north end of a lake. Consequently, you can include locations without any precise address information when capturing information for a case, lead, or incident. For more information, see Defining Locations.
You can associate latitude and longitude pairs or Universal Transverse Mercator (UTM) values with a single location. This association provides agencies with a variety of address formats that they can use when describing a specific location. For example, you can describe a location as Central Park, corner of 5th and Main Streets, parking lot G. The combination of a specific location with a descriptive label facilitates faster response to developing incidents and builds a richer repository of data for use in later analysis.
You can also integrate Siebel Location Tracking with the Geographic Information System (GIS), which provides a graphical representation of the location. Most GIS applications support an application programming interface (API) that is accessible using a C/C++, Java, .Net, or Web services interface. You can integrate GIS applications using Siebel Enterprise Application Integration. For more information about Siebel Enterprise Application Integration, see the following guides:
Overview: Siebel Enterprise Application Integration
Integration Platform Technologies: Siebel Enterprise Application Integration
Business Processes and Rules: Siebel Enterprise Application Integration
Siebel Application Services Interface Reference
XML Reference: Siebel Enterprise Application Integration
Transports and Interfaces: Siebel Enterprise Application Integration
Some GIS applications provide libraries or dynamically linked libraries (DLLs) that you can call using a business service or eScript.
Agencies can provide external mapping applications that are integrated with Siebel data with precise geo-coded location information for use in GIS analysis. For example, using GIS integration with Siebel Location Tracking, agents can search for incidents reported within a two-mile radius of a highway construction project or for suspicious activity associated with a crime spree in a neighborhood.
Roadmap for Administering Siebel Public Sector
This roadmap consists of processes and tasks that administrators typically perform when administering Siebel Public Sector. Your agency might follow a different roadmap according to its business requirements.
To administer Siebel Public Sector, administrators perform the following processes and tasks:
Adding Images to the Siebel Public Sector Home Page
Administrators can change the image on the Siebel Public Sector home page using the Home Page Image Administration screen. For example, administrators can change the Warning Level indicator on the home page. After you publish the image, all users in the same organization can view the image. Different organizations can display different images. For optimal layout on the home page, the image must be no larger than 350 pixels wide and 175 pixels high.
This task is a step in Roadmap for Administering Siebel Public Sector.
To add an image to the home page Warning Level indicator
Navigate to the Home Page Image Administration screen.
In the Image list, create a new record, and complete the fields as appropriate.
The following table describes some of the fields.
Field Description File Name
Select the file name or type the URL for the image.
Publish
Select this check box to display the image on the home page. Although you can add multiple images to the Image list, only this image appears on the home page.
Activating Siebel Public Sector Workflows
Activating Siebel Public Sector workflows allows users to perform numerous tasks in Siebel Public Sector. For more information about the Siebel Public Sector workflows, including the name and purpose of each workflow, see Public Sector Workflows
You have to activate Siebel Public Sector workflows only once for a database. For more information about working with workflows, see Siebel Business Process Framework: Workflow Guide.
This task is a step in Roadmap for Administering Siebel Public Sector.
To activate Siebel Public Sector workflows
Navigate to the Administration - Business Process screen, Workflow Deployment, and then the Active Processes view.
In the Active Workflow Processes list, query for the appropriate workflow names, and check the status of each workflow.
If any of the required workflows are not returned, then the workflows are not yet activated.
If a required workflow is not yet activated, then complete the following steps:
Scroll up to the Repository Workflow Processes list.
Select the appropriate workflow from the list, and click Activate.
Adding New Serialization Rules
This topic contains the following related information:
This task is a step in Roadmap for Administering Siebel Public Sector.
Viewing Serialization Configuration in Siebel Tools
You might want to check the configuration of the serialization rules in Siebel Tools. The following procedure provides instructions about checking the serialization for the HLS Case business component. Serialization is preconfigured for the following business components:
HLS Related Case
PUB Evidence
PUB Lead
PUB Related Evidence
PUB SubEvidence
PUB Sublead
To view the serialization on the HLS Case business component
Log in to Siebel Tools as an administrator.
Navigate to Object Explorer, then Business Component.
Query for the HLS Case business component.
Navigate to Business Component, then Business Component User Prop.
Query for Serialization*.
The following records appear.
Name Value SerializationAutoGenerate
Y
SerializationBC
HLS Case
SerializationBO
HLS Case
SerializationChildAttBC
HLS Cases Attachment
SerializationChildBC
PUB Evidence
SerializationChildBO
HLS Case
SerializationParentBC
None
SerializationParentIdField
None
(Optional) Repeat Step 3 to Step 5 for any of the other listed business components to view the default serialization configuration.
Creating Serialization Rule Records
Perform the following procedure to create new serialization rules.
To create a serialization rule
Navigate to the Administration - Case screen, then the Serialization Rules view.
In the Serialization Rules list, create a new record, and complete the fields as appropriate.
The following table describes some of the fields.
Field Description Name
Type the name of the rule.
Business Object
Select the business object on which the rule is based.
Business Component
Select the business component containing the fields on which the rule is based.
Scroll down to the Attributes list, and create a new record.
Note: Because serial numbers can contain a maximum of 100 characters, do not include any large text fields as one of the attributes.The following table describes some of the fields.
Field Description Sequence
Type a number that controls the attribute sequence in the generated serial number. For example, 1 indicates that the selected attribute appears first in the serial number.
Type
Select the type of attribute. Values include constants, parent serial numbers, and fields. For more information about selecting the appropriate attribute types, see Serialization Rule Attribute Types.
Business Component
Displays the name of the business component that you select in the Serialization Rules list.
Field Name
If you select a value of Field in the Type field, then select a field name. The values that you can select depend on the value in the Business Component field.
Constant Value
If you select a value of Constant in the Type field, then type a value for the constant. For more information, see Serialization Rule Attribute Types.
Repeat Step 3 until you define all the attributes required for the serial number.
Note: The last attribute in the sequence is generally a field value that is a unique number so that each serial number is unique.
Example 1 of Configuring Serialization
In the following example, you add PUB HLS Incident as a new serialization business object. The primary business component for this business object is PUB HLS Incident.
To add PUB HLS Incident as a parent object for serialization, perform the following tasks:
Configuring Incident Serialization in Siebel Tools
Perform the following procedure to allow serialization on the PUB HLS Incident business component.
You must configure the incident table and business component.
To configure the incident table and business component
Log in to Siebel Tools or Web Tools as an administrator and create a new workspace.
Navigate to Object Explorer, then Table, and query for the S_INCIDENT table.
Create a new column record called SERIAL_NUM.
To get the correct values for this new column, refer to the values in the SERIAL_NUM column of the S_CASE table.
Navigate to Object Explorer, then Business Component, and query for the PUB HLS Incident business component.
Navigate to Business Component, then Field, and create two new field records called Serial Number and Incident Number.
To get the correct values for these two fields, refer to the values in the Serial Number field and the Case Num field of the HLS Case business component. In the Calculated Value column of the Incident Number field, enter RowIdToRowIdNum([Id]).
Navigate to Business Component, then Business Component User Prop, and add the following user property records.
Name Value SerializationAutoGenerate
Y
SerializationBO
PUB HLS Incident
SerializationBC
PUB HLS Incident
SerializationChildBO
PUB HLS Incident
SerializationChildAttBC
PUB Incident Attachment
Note: If you add serialization on child business objects and components, then you might have to add additional fields. Use the serialization configuration for the HLS Case as a guide. For more information, see Viewing Serialization Configuration in Siebel Tools.Deliver the changes to the Integration Branch.
Adding an Incident Serialization Rule
Perform the following procedure to add a new serialization rule to determine the format for the incident serial numbers. For more information, see Creating Serialization Rule Records.
To add a rule for incident serialization
Navigate to the Administration - Case screen, then the Serialization Rules view.
In the Serialization Rules list, create a new record with the following values.
Field Value Name
Incident Rule
Business Object
PUB HLS Incident
Business Component
PUB HLS Incident
Scroll down to the Attributes list, and create new records with the following values.
Record Field Value Record 1
Sequence
1
Type
Field
Field Name
Incident Type
Record 2
Sequence
2
Type
Constant
Constant Value
-
Record 3
Sequence
3
Type
Field
Field Name
Incident Number
Example 2 of Configuring Serialization
Your organization might want to serialize incident attachments by adding a Serial Number button to the Attachments view in the Incident List view of the Incidents screen. For more information about adding such a button to the user interface, see Adding Serial Number Buttons to the User Interface.
Before users can successfully use this button however, administrators must perform some configuration. Perform the instructions in the following procedures to allow serialization of incident attachments.
To allow serialization of incident attachments by an Incident Attachment Rule, perform the following tasks:
Configuring Incident Attachment Serialization in Siebel Tools
Perform the following procedure to allow serialization on the PUB Incident Attachment business component.
You must configure the incident attachment table and business component.
To configure the incident attachment table and business component
Log in to Siebel Tools or Web Tools as an administrator and create a new workspace.
Navigate to Object Explorer, then Table, and query for the S_INCIDENT_ATT table.
Create a new column record called SERIAL_NUM.
To get the correct values for this new column, refer to the values in the SERIAL_NUM column of the S_CASE table.
Navigate to Object Explorer, then Business Component, and query for the PUB Incident Attachment business component.
Navigate to Business Component, then Field, and create two new field records called Serial Number and Incident Attachment Number.
To get the correct values for these two fields, refer to the values in the Serial Number field and the Case Num field of the HLS Case business component. In the Calculated Value column of the Incident Attachment Number field, enter RowIdToRowIdNum([Id]).
Select the Force Active check box for the Incident Id field.
Navigate to Business Component, the Business Component User Prop, and create six new user property records with the following values and expressions.
Name Value Named Method 1
"GenerateSerialNumber", "INVOKE", "PUB Incident Attachment", "WriteRecord"
Named Method 2
"GenerateSerialNumber", "INVOKESVC", "PUB Incident Attachment", "PUB Case Serialization Service", "SetSerialNumber", "Operation", "Generate", "BO Name", "PUB HLS Incident", "BC Name", "PUB Incident Attachment", "Id", "[Id]", "Parent BC Name", "PUB HLS Incident", "Parent Id", "ParentFieldValue('Id')"
Named Method 3
"GenerateSerialNumber", "INVOKE", "PUB Incident Attachment", "RefreshRecord"
Named Method 4
"ReGenerateSerialNumber", "INVOKE", "PUB Incident Attachment", "WriteRecord"
Named Method 5
"ReGenerateSerialNumber", "INVOKESVC", "PUB Incident Attachment", "PUB Case Serialization Service", "SetSerialNumber", "Operation", "ReGenerate", "BO Name", "PUB HLS Incident", "BC Name", "PUB Incident Attachment", "Id", "[Id]", "Parent BC Name", "PUB HLS Incident", "Parent Id", "ParentFieldValue('Id')"
Named Method 6
"ReGenerateSerialNumber", "INVOKE", "PUB Incident Attachment", "RefreshRecord"
Deliver the changes to the Integration Branch.
Adding an Incident Attachment Serialization Rule
Perform the following procedure to add a new serialization rule to determine the format for the incident attachment serial numbers. For more information, see Creating Serialization Rule Records.
To add a rule for incident attachment serialization
Navigate to the Administration - Case screen, then the Serialization Rules view.
In the Serialization Rules list, create a new record with the following values.
Field Value Name
Incident Attachment Rule
Business Object
PUB HLS Incident
Business Component
PUB Incident Attachment
Scroll down to the Attributes list, and create new records with the following values.
Record Field Value Record 1
Sequence
1
Type
Parent Serial Number
Record 2
Sequence
2
Type
Constant
Constant Value
-
Record 3
Sequence
3
Type
Field
Field Name
Incident Attachment Number
Disabling Automatic Serialization
By default, Siebel Public Sector has automatic case serialization. However, you can disable this serialization and add Serial Number buttons to the user interface to allow users to manually serialize items as required.
This topic contains the following related information:
This task is a step in Roadmap for Administering Siebel Public Sector.
To disable automatic serialization on a business component
Log in to Siebel Tools or Web Tools as an administrator and create a new workspace.
Navigate to Object Explorer, then Business Component.
Query for the appropriate business component.
Navigate to Business Component, then Business Component User Prop.
Query for the SerializationAutoGenerate user property.
Change the value from Y to N.
(Optional) If you want to replace automatic serialization with Serial Number buttons for the user, then you can perform the procedures now.
Then, continue with the following step. For more information, see Adding Serial Number Buttons to the User Interface.
Deliver the changes to the Integration Branch.
Adding Serial Number Buttons to the User Interface
Using Serial Number buttons, you can give the users the option to serialize items (for example, leads) in the user interface. To view an example of a Serial Number button, navigate to the Evidence screen, Evidence List, and then the Attachments view. For more information about editing applet layouts, views, and screens, see Configuring Siebel Business Applications.
To add a Serial Number button to the Leads screen, perform the following tasks:
These tasks assume that you disabled automatic serialization on leads. For more information, see Disabling Automatic Serialization.
Checking Configuration on PUB Lead Business component
First, check the configuration on the PUB Lead business component.
To check the configuration on the PUB Lead business component
Log into Siebel Tools as an administrator.
Navigate to Object Explorer, then Business Component.
Query for PUB Lead.
Navigate to Business Component, then Field.
Check to make sure that the Serial Number field is present.
Creating and Configuring New Serialization Applet
You must create and configure the new serialization applet.
To create and configure the new serialization applet
Navigate to Object Explorer, then Applet and query for the PUB Lead Form Applet.
Copy the applet record and rename it with the suffix (Serialization) to PUB Lead Form Applet (Serialization).
Right-click the applet record, and select Edit Web Layout.
In the Mode field of the Web Controls toolbar, select the Edit List applet mode.
On the Web Controls window, click the MiniButton icon.
Click the position in Applet Layout where you want the button to appear.
Define the properties for the control in the Properties Window using the following values.
Field Value Caption
Serial Number
HTML Display Mode
EncodeData
HTML Only
True
HTML Row Sensitive
True
HTML Type
MiniButton
Inactive
False
Method Invoked
SerialNumber
Name
SerialNumber
Parent Name
PUB Lead Form Applet
Prompt
False
Read Only
False
RunTime
False
Show Popup
False
Sort
True
Text Alignment
Left
Note: This means to align text on the first character in the word or phrase.Visible
True
Visible Language Override
True
Select File and then Save.
Defining Business User Properties
You must also define the business user properties to invoke the serialization business service.
To define business user properties to invoke the serialization business service
Log in to Seibel Tools or Web Tools as an Administrator and create a new workspace.
Navigate to Object Explorer, then Business Component and query for PUB Lead.
Navigate to Business Component, then Business Component User Prop.
Create three new user property records with the following values and expressions.
Name Value Named Method 1
"SerialNumber", "INVOKE", "PUB Lead", "WriteRecord"
Named Method 2
"SerialNumber", "INVOKESVC", "PUB LEAD", "PUB Case Serialization Service", "SetSerialNumber", "Operation", "Generate", "BO Name", "HLS Case", "BC Name", "PUB LEAD", "Id", "[Id]", "Parent BC Name", "HLS Case", "Parent Id", "ParentFieldValue('Id')"
Named Method 3
"SerialNumber", "INVOKE", "PUB LEAD", "RefreshRecord"
Named Method 1 forces a WriteRecord, Named Method 2 invokes the Serialization Service business service to set the Serial Number field in the PUB Lead business component, and Named Method 3 refreshes the user interface.
Note: If additional named methods are already configured on the business component, then name the serialization user properties using the next available numbers. For example, if Named Methods 1, 2, and 3 exist, then you can add Named Methods 4, 5, and 6 for the purposes of serialization.Replace the PUB Lead Form Applet in the PUB Leads List View with the new PUB Lead Form Applet (Serialization).
Deliver the changes to the Integration Branch.
Disabling Serial Number Buttons
By default, users can click buttons as often as they like. However, clicking a Serial Number button multiple times results in multiple generated serial numbers for the same item. To create new serial numbers, use the Regenerate and Regenerate All buttons. For more information, see About Generating New Serial Numbers.
To disable Serial Number buttons when the field is not null, use the following server script:
function WebApplet_PreCanInvokeMethod (MethodName, &CanInvoke)
{
if(MethodName == "SerialNumber")
{
if(BusComp().GetFieldValue("Serial Number")=="")
{
CanInvoke = "TRUE";
return(CancelOperation);
}
else
{
CanInvoke = "FALSE";
return(CancelOperation);
}
}
return (ContinueOperation);
}
Process of Setting Up Approval Templates
This process consists of tasks that administrators typically perform when setting up approval templates. Your agency might follow a different process according to its business requirements. For more information, see About Approval Templates and Routing.
To set up approval templates, administrators perform the following tasks:
This process is a step in Roadmap for Administering Siebel Public Sector.
Creating Approval Templates for Investigative Cases
Perform the following procedure to create an approval template for an investigative case.
To allow users to select the appropriate templates from the Cases screen, you must select values for the following fields: Category, Territory, Priority, Start Date, and Status when you create an approval template for an investigative case. If users need the template immediately, then make sure you set the Status field to Active and the Start Date field to the default creation time.
The selection of templates that users see depends on the values in the case record for Category, Territory, and Priority. For example, a user who creates a case record with the values of Kidnapping (Category), New York (Territory), and Urgent (Priority), can select only an approval template with the same values. If your agency uses the Threat Level and Threat Category fields, then these values also determine the templates that users see.
This task is a step in Process of Setting Up Approval Templates.
To create an approval template for investigative cases
Navigate to the Administration - Case screen, then the Case Approval Template view.
Create a new record, and complete the fields as appropriate.
The following table describes some of the fields.
Field Description Name
Type the name of the approval template.
Template Object
Displays a value of Case. When creating a lead approval template, this field is populated with a value of Lead. When creating an incident approval template, this field is populated with a value of Incident.
Status
Displays a status of Active for the template. Values include Active and Inactive. You can predefine several templates but activate only those that users currently need. To allow users to select the template from the Cases screen, make sure that you select Active.
Category
Select a category for the template. Values depend on the types of cases that an agency handles.
In the List of Values view of the Administration - Data screen, administrators can edit the category LOVs to include the categories for your organization. They add values to a Type field of PUB_CASE_CATEGORY_TYPE. For more information, see Siebel Applications Administration Guide.
Territory
Select the territory in which users employ this approval template.
Priority
Select the urgency of the required approvals.
Type
Select the type of approval template. Values include Admin and User.
Start Date
Displays the date and time that you create the template. Thus, the template is available immediately to users. You can change this date and time that the template is in effect.
End Date
Select the date and time that the template is no longer in effect.
Drill down on the Name field, and navigate to the Approvers view.
Create a new record for each user in the chain of approval.
The Sequence Number field determines the order in which the case is routed to each user.
When users select an approval template for a case and then submit the case for approval, the case is routed automatically to the inbox of the first approver in the chain of approval. For more information, see Submitting Cases for Approval and Approving Cases in the Inbox.
Creating Approval Templates for Leads
Perform the following procedure to create an approval template for a lead.
To allow users to select the appropriate templates from the Leads screen, you must select values for the following fields: Lead Type, Territory, Priority, Start Date, and Status when you create a lead approval template. If users need the template immediately, then make sure you set the Status field to Active and the Start Date field to the default creation time.
The selection of templates that users see depends on the values in the lead record for Lead Type, Territory, and Lead Priority. For example, a user who creates a lead record with the values of Investigative (Lead Type), New York (Territory), and Immediate (Lead Priority), can select only an approval template with the same values.
This task is a step in Process of Setting Up Approval Templates.
To create an approval template for leads
Navigate to the Administration - Case screen, then the Lead Approval Template view.
Create a new record, and complete the fields as appropriate.
For more information about the fields in this view, see Creating Approval Templates for Investigative Cases.
Drill down on the Name field, and navigate to the Approvers view.
Create a new record for each user in the chain of approval.
The Sequence Number field determines the order in which the lead is routed to each user.
When users select an approval template for a lead and then submit the lead for approval, the lead is routed automatically to the inbox of the first approver in the chain of approval. For more information, see Submitting Leads for Approval and Approving Cases in the Inbox.
Creating Approval Templates for Benefits Cases
Perform the following procedure to create an approval template for a benefits case.
When you create an approval template for a benefits case, the Category field of the template is populated with a value of Benefit, and you cannot change this value. To allow users to select the appropriate templates from the Cases screen, you must select values for the following fields: Territory Name, Priority, Start Date, and Status when you create an approval template for a benefits case. If users need the template immediately, then make sure you set the Status field to Active and the Start Date field to the default creation time.
The selection of templates that users see depends on the values in the case record for Category, Territory, and Priority. For example, a user who creates a case record with the values of Benefit (Category), New York (Territory), and Urgent (Priority), can select only an approval template with the same values.
This task is a step in Process of Setting Up Approval Templates.
To create an approval template for benefits cases
Navigate to the Administration - Case screen, then the Benefits Plan Approval Template view.
Create a new record, and complete the fields as appropriate.
For more information about the fields in this view, see Creating Approval Templates for Investigative Cases.
Drill down on the Name field.
The Benefits Plan Approvers view appears.
Create a new record for each user in the chain of approval.
The Sequence Number field determines the order in which the case is routed to each user.
When users select an approval template for a case and then submit the case for approval, the case is routed automatically to the inbox of the first approver in the chain of approval. For more information, see Submitting Cases for Approval and Approving Cases in the Inbox.
Creating Approval Templates for Incidents
Perform the following procedure to create an approval template for an incident.
To allow users to select the appropriate templates from the Incidents screen, you must select values for the following fields: Incident Type, Priority, Start Date, and Status when you create an approval template for an incident. If users need the template immediately, then make sure you set the Status field to Active and the Start Date field to the default creation time.
The selection of templates that users see depends on the values in the incident record for Incident Type and Incident Priority. For example, a user who creates an incident record with the values of Child Welfare (Incident Type) and Urgent (Incident Priority), can select only an approval template with the same values.
This task is a step in Process of Setting Up Approval Templates.
To create an approval template for incidents
Navigate to the Administration - Case screen, then the Incident Approval Template view.
Create a new record, and complete the fields as appropriate.
For more information about the fields in this view, see Creating Approval Templates for Investigative Cases.
Drill down on the Name field, and navigate to the Approvers view.
Create a new record for each user in the chain of approval.
The Sequence Number field determines the order in which the incident is routed to each user.
When users select an approval template for an incident and then submit the incident for approval, the incident is routed automatically to the inbox of the first approver in the chain of approval. For more information, see Submitting Incidents for Approval and Approving Cases in the Inbox.
Defining Locations
You can define locations. For more information about how organizations can use defined locations in Siebel Public Sector, see About Location Tracking.
This task is a step in Roadmap for Administering Siebel Public Sector.
To define a location
Navigate to the Administration - Data screen, then the Location view.
In the Location list, create a new record, and complete the fields as appropriate.
The following table describes some of the fields.
Field Description Location
Type the name of the location.
Type
Select the type of location. Values include Hill, Mall, and National Park.
Cross Street
Type the location’s cross street, if any.
Country
Select the country of the location.
Altitude
Type the altitude of the location. This field can be helpful when describing a location on a hill or other raised ground.
Latitude
Type the latitude of the location.
Longitude
Type the longitude of the location.
UTM Easting
Type the Universal Transverse Mercator Easting value of the location.
UTM Northing
Type the Universal Transverse Mercator Northing value of the location.
Scroll down to the Addresses list, and create a new record.
The following table describes some of the fields.
Field Description Street Address
Type the street address for the location, if available.
Street Address 2
Type the secondary street address for the location.
Address Name
Type a descriptive name for the address, for example, High Street Mall Address.
Premise
Select this check box if the address relates to a building or part of a building.
Location
Displays the value that you select in the Location field.
Repeat Step 3 until you add all the addresses that relate to the location.
Associating Existing Addresses with Locations
You can also associate existing addresses with a location.
To associate existing addresses with a location
Navigate to the Administration - Data screen, then the Addresses view.
Select an existing address record or create a new record.
In the Location field, select the location for the address.
Process of Configuring Time Management
This process consists of tasks that administrators typically perform when configuring time management. Your agency might follow a different process according to its business requirements.
To configure time management, administrators perform the following tasks:
This process is a step in Roadmap for Administering Siebel Public Sector.
Configuring Constraints for Time Entry
Administrators can configure the period of time that users are allowed to assign time to a case or incident after that case or incident is closed. For example, if a case closes on day 1, and if the administrator configures a period of 5 days for cases, then users cannot assign time to that case on day 7 or later. For more information about assigning time to cases, see Process of Managing Case Time. For more information about assigning time to incidents, see Process of Managing Incident Time.
This task is a step in Process of Configuring Time Management.
To configure the constraints for time entry
Log in to Siebel Tools or Web Tools as an administrator and create a new workspace.
Navigate to Object Explorer, then Business Component.
To configure the period of time that users are allowed to assign time to a case after that case is closed, complete the following steps:
Query for the PUB Case Time Item business component.
Navigate to Business Component, then Business Component User Prop.
Change the value for the Allowed to Add Time Entry After Closed: Case user property.
To configure the period of time that users are allowed to assign time to an incident after that incident is closed, complete the following steps:
Query for the PUB Incident Time Item business component.
Navigate to Business Component, then Business Component User Prop.
Change the value for the Allowed to Add Time Entry After Closed: Incident user property.
Deliver the changes to the Integration Branch.
Configuring Time Entry Views
In the preconfigured Siebel Public Sector application, users cannot assign the time of other users to cases in the Case Time Tracker view of the Cases screen and in the Case Calendar view of the Calendar screen. Likewise, users cannot assign the time of other users to incidents in the Incident Time Tracker view of the Incidents screen and in the Incident Calendar view of the Calendar screen.
Administrators can complete the procedure in this topic to allow users to assign the time of other users to cases and incidents in these views. For more information about assigning time to cases, see Process of Managing Case Time. For more information about assigning time to incidents, see Process of Managing Incident Time.
This task is a step in Process of Configuring Time Management.
To configure the time entry views
Log in to Siebel Tools or Web Tools as an administrator and Create a new workspace.
Navigate to Object Explorer, then View.
To configure the time entry views for cases, complete the following steps:
Query for the appropriate view:
If you want to configure the Case Time Tracker view, then query for the PUB Case Time Track View.
If you want to configure the Case Calendar view, then query for the PUB Calendar Case Time Item View.
Navigate to View, then View User Prop.
Change the value for the Enable Access Control user property to Y.
To configure the time entry views for incidents, complete the following steps:
Query for the appropriate view:
If you want to configure the Incident Time Tracker view, then query for the PUB Incident Time Track View.
If you want to configure the Incident Calendar view, then query for the PUB Calendar Incident Time Item View.
Navigate to View, then View User Prop.
Change the value for the Enable Access Control user property to Y.
Deliver the changes to the Integration Branch.
Configuring User Approval Limits for Time Sheets
After a user submits a time sheet for approval, the user who is designated in the Submit To field of the time sheet can access the Time Sheet Approval view to approve or reject that time sheet.
The user approval limit is the maximum number of time sheet hours that a user has the authority to approve. If an approver approves a time sheet with a number of hours that exceeds the approver’s authority, then the manager of that approver must also approve the time sheet. An approved time sheet is automatically routed up the organizational hierarchy until an approver with the necessary authority approves the time sheet. For more information, see Approving Time Sheets.
After final approval, the user who submitted the time sheet for approval can further process the approved time sheet.
Administrators can configure the approval limits for the users who approve time sheets. They can configure lower approval limits for users at lower levels of the organizational hierarchy and higher approval limits for users at higher levels of the organizational hierarchy. Consequently, a user at a higher level must approve only time sheets with hour quantities that exceed the approval limits of the user’s immediate subordinates.
This task is a step in Process of Configuring Time Management.
To configure a user approval limit for time sheets
Navigate to the Administration - User screen, then the Employees view.
Drill down on the Last Name field for the record of the user for whom you want to configure an approval limit for time sheets.
Navigate to the More Info view.
In the Approval Authority section of the form, enter the approval limit in the Time Sheet Hours Approval Limit field.
Process of Configuring Embedded Analytics
To configure embedded analytics for Siebel Public Sector, administrators integrate Siebel Public Sector with Oracle Business Intelligence. You configure embedded analytics so that a graph of the number of cases by status appears in the Cases By Status view of the Cases screen and so that a list of the top 10 suspects appears in the Evidence Analytics view of the Evidence screen.
This process consists of tasks that administrators typically perform when configuring embedded analytics. Your agency might follow a different process according to its business requirements.
To configure embedded analytics, administrators perform the following tasks:
This process is a step in Roadmap for Administering Siebel Public Sector.
Configuring the Host for Analytics Server
To integrate Siebel Public Sector with Oracle Business Intelligence, the administrator configures the host for the Analytics Server in Siebel Public Sector.
This task is a step in Process of Configuring Embedded Analytics.
To configure the host for the Analytics Server
Navigate to the Administration - Integration screen, then the WI Symbolic URL List view.
Select Host Administration in the visibility filter.
For the NQHOST virtual name, enter the name of your Analytics Server in the Name field.
Example syntax for the name follows: demohost.example.com.
Configuring Symbolic URLs
After configuring the host for the Analytics Server in Siebel Public Sector, the administrator configures the symbolic URLs for the paths to the appropriate reports in Oracle Business Intelligence.
This task is a step in Process of Configuring Embedded Analytics.
To configure symbolic URLs
Navigate to the Administration - Integration screen, then the WI Symbolic URL List view.
Select Symbolic URL Administration in the visibility filter.
To set up the graph of the number of cases by status, complete the following steps:
Select the PUBAnalyticsCase URL name.
In the Symbolic URL Arguments list, in the Argument Value field for the Name field of Path, enter the path to the report for the graph of the number of cases by status.
The location of the report in your analytics setup determines this path. An example path follows:
/shared/Public Sector Analytics/Embedded/Cases By Status
To set up the list of the top 10 suspects, complete the following steps:
Select the PUBAnalyticsSuspect URL name.
In the Symbolic URL Arguments list, in the Argument Value field for the Name field of Path, enter the path to the report for the list of the top 10 suspects.
The location of the report in your analytics setup determines this path. An example path follows:
/shared/Public Sector Analytics/Embedded/Top 10 Suspects by Case Type
Creating a Profile for Analytics Data Source
After configuring symbolic URLs for the paths to the appropriate reports in Oracle Business Intelligence, the administrator creates a profile for the analytics data source.
This task is a step in Process of Configuring Embedded Analytics.
To create a profile for the analytics data source
Navigate to the Administration - Server Configuration screen, then the Enterprises view.
Navigate to the Profile Configuration view.
Select the Server Datasource profile, and copy the record.
In the copied record, rename the Profile field to Analytics Datasource and the Alias field to AnalyticsDataSrc.
In the Profile Parameters list for the new Analytics Datasource record, change the following records.
Alias Field Value Field DSDLLName
sscdsacon
DSConnectString
AnalyticsWeb. This value is the name of the DSN (Database Source Network) for ODBC (Open Database Connectivity). The Analytics Server installation creates this name for the Analytics Server.
DSTableOwner
Make sure that this field does not contain data.
Adding Analytics Data Source to Component Definition
After creating a profile for the analytics data source, the administrator adds that data source to the component definition. You must log out of Siebel Public Sector after you change the component definition so that the new component definition takes effect.
This task is a step in Process of Configuring Embedded Analytics.
To add the analytics data source to the component definition
Navigate to the Administration - Server Configuration screen, then the Enterprises view.
Navigate to the Component Definitions view.
Select the Public Sector Object Manager component, and then select Start Reconfiguration in the menu that appears when you click the cogwheel icon for components.
The State field of the component changes to Reconfiguring.
In the Component Parameters list, select the OM - Named Data Source name.
In the Value field of this parameter, add AnalyticsDataSrc to the existing values.
Select Commit Reconfiguration in the menu that appears when you click the cogwheel icon for components.
Adding Profile Parameters to Siebel Configuration File
After adding the data source to the component definition, the administrator adds the profile parameters to the Siebel configuration file. You must restart the Siebel Server after you add the profile parameters.
This task is a step in Process of Configuring Embedded Analytics.
To add the profile parameters to the Siebel configuration file
Access the Siebel Server.
Navigate to the installation folder.
Open the publicsector.cfg file at:
ses\siebsrvr\BIN\LanguageIn this path, Language is the language you are using.
Insert the following text after
[GatewayDataSrc]:[AnalyticsDataSrc] DLL = sscdsacon.dll ConnectString = AnalyticsWeb TableOwner = SqlStyle = Analytics