Siebel has provided its base functionality (Vanilla Functionality). For Siebel Testing we have following structured Testing Methodology. We are applying following Strategies against SIEBEL (Sales Module).
1. Functional Testing.
2. Boundary Conditions :Test method and equivalence Partitioning Test Method.
New View:
• Verify the entire BC field Names mapped to UI fields as per Design Document. Verify All the Label Names in List And Form Applet. BC Field Names and Label Names should be consistent in List and Form.
• If new view fields are exposed in any analysis view, Field label names should be consistent in all related Views (Analysis Views)
• Validate field Properties (Editable, Read-only, Runtime True and Pick Applet). Should maintain consistency in List and Form Applet.
• All fields that are in Form Applet should be there in List Applet with same Field Properties.
• Verify copy functionality in applet level (File). If it is not mention in requirement or Design escalate it to BA (Business Analyst).
• If a view has been removed, then it should be checked that any hyperlink in any other view should not have this view as its destination drilldown object.
• If a view has been removed check that it has also been removed from the Site Map.
Applet:
• Verify the entire BC field Names mapped to UI fields as per Design Document. Verify All the Label Names in List And Form Applet. BC Field Names and Label Names should be consistent in List and Form.
• If fields are exposed in any analysis view, Field label names should be consistent in all related Views (Analysis Views)
• Validate field Properties (Editable, Read-only, Runtime True and Pick Applet). Should maintain consistency in List and Form Applet.
• All fields that are in Form Applet should be there in List Applet with same Field Properties.Verify copy functionality in applet level (File). If it is not mention in requirement or Design escalate it to BA (Business Analyst).
• When developer copies the existing Applet and built new functionality on top it. Validate the search spec weather he modified it or not. Also the hyperlinks whether they should got to the same view or different views.
-
Field:
• If you add new field do following Testing.
• Check in list and form applet.
• Filed Length, Field Properties, Field Mapping, Copy functionality. If it is date. It should not display time Stamp unless it is mentioned in design or Requirement Document. It should verify with BA’s where all this field needs to be displayed.
• When they delete the Field or inactivate the field. Check in List and form Applet. Verify with develop weather that particular field is used in any Script. Test in Reports and other Views if they are deleting from first or second Screen. It should be deleted in BA views.
• Whenever any field is pulled from join then all associated fields along with the pulled field must be read only. For Ex: Suppose Accounts field is pulled then fields contact, state, country,zip all must be read only.
• Check the Roll-ups and Calculations in the fields.
• Check that the numeric fields should not accept negative values. Error message should get fired.
Data Validation:
• You should make use of Filters wherever possible in the excel sheet while updation/validation of data.
• While creating new records, query from the backend (if possible) so as to minimize the effort.
• If some view or some functionality has to be removed, do check whether the state model has been modified to remove the respective states or not.
Assignment Rules:
• Should check whether the concerned candidate has been added in the rule or not and whether he is an active or a terminated user.
• Should check that whether the Activation/Expiration date has been filled in case of activation or expiration of the rules.
• Should check that if a candidate has multiple positions then he should be added in the list for the respective position only.
08 February 2011
Siebel Testing
Siebel has provided its base functionality (Vanilla Functionality). For Siebel Testing we have following structured Testing Methodology. We are applying following Strategies against SIEBEL (Sales Module).
1. Functional Testing.
2. Boundary Conditions :Test method and equivalence Partitioning Test Method.
New View:
• Verify the entire BC field Names mapped to UI fields as per Design Document. Verify All the Label Names in List And Form Applet. BC Field Names and Label Names should be consistent in List and Form.
• If new view fields are exposed in any analysis view, Field label names should be consistent in all related Views (Analysis Views)
• Validate field Properties (Editable, Read-only, Runtime True and Pick Applet). Should maintain consistency in List and Form Applet.
• All fields that are in Form Applet should be there in List Applet with same Field Properties.
• Verify copy functionality in applet level (File). If it is not mention in requirement or Design escalate it to BA (Business Analyst).
• If a view has been removed, then it should be checked that any hyperlink in any other view should not have this view as its destination drilldown object.
• If a view has been removed check that it has also been removed from the Site Map.
Applet:
• Verify the entire BC field Names mapped to UI fields as per Design Document. Verify All the Label Names in List And Form Applet. BC Field Names and Label Names should be consistent in List and Form.
• If fields are exposed in any analysis view, Field label names should be consistent in all related Views (Analysis Views)
• Validate field Properties (Editable, Read-only, Runtime True and Pick Applet). Should maintain consistency in List and Form Applet.
• All fields that are in Form Applet should be there in List Applet with same Field Properties.Verify copy functionality in applet level (File). If it is not mention in requirement or Design escalate it to BA (Business Analyst).
• When developer copies the existing Applet and built new functionality on top it. Validate the search spec weather he modified it or not. Also the hyperlinks whether they should got to the same view or different views.
-
Field:
• If you add new field do following Testing.
• Check in list and form applet.
• Filed Length, Field Properties, Field Mapping, Copy functionality. If it is date. It should not display time Stamp unless it is mentioned in design or Requirement Document. It should verify with BA’s where all this field needs to be displayed.
• When they delete the Field or inactivate the field. Check in List and form Applet. Verify with develop weather that particular field is used in any Script. Test in Reports and other Views if they are deleting from first or second Screen. It should be deleted in BA views.
• Whenever any field is pulled from join then all associated fields along with the pulled field must be read only. For Ex: Suppose Accounts field is pulled then fields contact, state, country,zip all must be read only.
• Check the Roll-ups and Calculations in the fields.
• Check that the numeric fields should not accept negative values. Error message should get fired.
Data Validation:
• You should make use of Filters wherever possible in the excel sheet while updation/validation of data.
• While creating new records, query from the backend (if possible) so as to minimize the effort.
• If some view or some functionality has to be removed, do check whether the state model has been modified to remove the respective states or not.
Assignment Rules:
• Should check whether the concerned candidate has been added in the rule or not and whether he is an active or a terminated user.
• Should check that whether the Activation/Expiration date has been filled in case of activation or expiration of the rules.
• Should check that if a candidate has multiple positions then he should be added in the list for the respective position only.
1. Functional Testing.
2. Boundary Conditions :Test method and equivalence Partitioning Test Method.
New View:
• Verify the entire BC field Names mapped to UI fields as per Design Document. Verify All the Label Names in List And Form Applet. BC Field Names and Label Names should be consistent in List and Form.
• If new view fields are exposed in any analysis view, Field label names should be consistent in all related Views (Analysis Views)
• Validate field Properties (Editable, Read-only, Runtime True and Pick Applet). Should maintain consistency in List and Form Applet.
• All fields that are in Form Applet should be there in List Applet with same Field Properties.
• Verify copy functionality in applet level (File). If it is not mention in requirement or Design escalate it to BA (Business Analyst).
• If a view has been removed, then it should be checked that any hyperlink in any other view should not have this view as its destination drilldown object.
• If a view has been removed check that it has also been removed from the Site Map.
Applet:
• Verify the entire BC field Names mapped to UI fields as per Design Document. Verify All the Label Names in List And Form Applet. BC Field Names and Label Names should be consistent in List and Form.
• If fields are exposed in any analysis view, Field label names should be consistent in all related Views (Analysis Views)
• Validate field Properties (Editable, Read-only, Runtime True and Pick Applet). Should maintain consistency in List and Form Applet.
• All fields that are in Form Applet should be there in List Applet with same Field Properties.Verify copy functionality in applet level (File). If it is not mention in requirement or Design escalate it to BA (Business Analyst).
• When developer copies the existing Applet and built new functionality on top it. Validate the search spec weather he modified it or not. Also the hyperlinks whether they should got to the same view or different views.
-
Field:
• If you add new field do following Testing.
• Check in list and form applet.
• Filed Length, Field Properties, Field Mapping, Copy functionality. If it is date. It should not display time Stamp unless it is mentioned in design or Requirement Document. It should verify with BA’s where all this field needs to be displayed.
• When they delete the Field or inactivate the field. Check in List and form Applet. Verify with develop weather that particular field is used in any Script. Test in Reports and other Views if they are deleting from first or second Screen. It should be deleted in BA views.
• Whenever any field is pulled from join then all associated fields along with the pulled field must be read only. For Ex: Suppose Accounts field is pulled then fields contact, state, country,zip all must be read only.
• Check the Roll-ups and Calculations in the fields.
• Check that the numeric fields should not accept negative values. Error message should get fired.
Data Validation:
• You should make use of Filters wherever possible in the excel sheet while updation/validation of data.
• While creating new records, query from the backend (if possible) so as to minimize the effort.
• If some view or some functionality has to be removed, do check whether the state model has been modified to remove the respective states or not.
Assignment Rules:
• Should check whether the concerned candidate has been added in the rule or not and whether he is an active or a terminated user.
• Should check that whether the Activation/Expiration date has been filled in case of activation or expiration of the rules.
• Should check that if a candidate has multiple positions then he should be added in the list for the respective position only.
29 December 2010
How to create MVG?
How to create MVG?
First create parent BC and required fields, then create child BC and required fields (or) Select existing Parent and child BC's and check the relationship between them. For MVG relation should be 1:M or M:M.
If there isn’t an existing link between them, create a new link. In link object enter Name, Parent Business Component, Child business Component, Inter Table, Inter parent column, Inter Child Column properties.
Then go to parent BC, click Multi Value Link, It identifies the link that provides the field values from the multi-value group business component (child BC). In this enter Name, Destination Business Component, Destination Link and Use Primary Join (It will convert 1: M to 1:1 relationship). Use Primary Join identifies the foreign key field in the originating, or joined, business component. The foreign key field identifies the primary record in the set of records for one multi-value group.
Next select Multi Value Fields object, these fields are in the originating business component that are populated by the multi-value link. In Parent BC’s Multi Value Fields object enter Multi Value Field Name, Multi Value Link and Field properties.
Next which fields you created in MVF, add in Parent BC List Applet's List columns and edit web layout.
Then create a MVG Applet, in this enter Name, Business Component (Child BC) and Type as MVG. In the list columns enter Name, Field and Display Name. In list columns should enter "SSA Primary Field" as a field.
In MVG Applet go to Control object, enter
Name Caption HTML Row Sensitive HTML TypeMethodInvoke
PopupQueryPick-- OK -- Active-- MiniButton -- CloseApplet
Next go to Parent BC's List Column object. In this where you want to see popup applet, in that record enter MVG Applet name and Runtime Properties.
Then go to View object and edit web layout as View Detail (Parent with Pointer) template.
Next Add view name in screen, add screen in application.
Then Compile the Project.
First create parent BC and required fields, then create child BC and required fields (or) Select existing Parent and child BC's and check the relationship between them. For MVG relation should be 1:M or M:M.
If there isn’t an existing link between them, create a new link. In link object enter Name, Parent Business Component, Child business Component, Inter Table, Inter parent column, Inter Child Column properties.
Then go to parent BC, click Multi Value Link, It identifies the link that provides the field values from the multi-value group business component (child BC). In this enter Name, Destination Business Component, Destination Link and Use Primary Join (It will convert 1: M to 1:1 relationship). Use Primary Join identifies the foreign key field in the originating, or joined, business component. The foreign key field identifies the primary record in the set of records for one multi-value group.
Next select Multi Value Fields object, these fields are in the originating business component that are populated by the multi-value link. In Parent BC’s Multi Value Fields object enter Multi Value Field Name, Multi Value Link and Field properties.
Next which fields you created in MVF, add in Parent BC List Applet's List columns and edit web layout.
Then create a MVG Applet, in this enter Name, Business Component (Child BC) and Type as MVG. In the list columns enter Name, Field and Display Name. In list columns should enter "SSA Primary Field" as a field.
In MVG Applet go to Control object, enter
Name Caption HTML Row Sensitive HTML TypeMethodInvoke
PopupQueryPick-- OK -- Active-- MiniButton -- CloseApplet
Next go to Parent BC's List Column object. In this where you want to see popup applet, in that record enter MVG Applet name and Runtime Properties.
Then go to View object and edit web layout as View Detail (Parent with Pointer) template.
Next Add view name in screen, add screen in application.
Then Compile the Project.
20 December 2010
Certification Questions
1. In order to change the fonts used by your Siebel application, what file(s) should you modify? Select one answer.
A.Siebel.exe file
B.Siebel template files
C.Cascading style sheets
D.SQL scripts to change the data model
2. Which Link property must be populated for a MVG with a M:M relationship, but is not populated for a MVG with a 1:M relationship?
A.Inter Table
B.Destination Field
C.Child Business Component
D.Parent Business Component
3. You have enabled the Workflow Management component group on the server through the Siebel user interface, but you are unable to run workflows using Workflow policies. Which step might have you forgotten to execute? (Choose two.)
A.restarting the Siebel Server service
B.running a Generate Triggers batch job
C.enabling the Generate Triggers component
D.setting the Workflow Policy properties in Tools
E.specifying the triggering event in the detail applet for the workflow step branch following the Start Step
4. Which three are true about a task in Siebel task UI? (Choose three.)
A.It implements process automation.
B.It must be invoked by a run-time event.
C.It consists of a sequenced set of views.
D.It does not support conditional processing.
E.It does not support transactional processing.
F.It is designed for novice users performing complex tasks.
5. Business rules consist, in part, of concepts. Which two are examples of concepts? (Choose two.)
A.Field
B.Entity
C.Value
D.Object
6. Which describes the role of Assignment Objects for Assignment Manager?
A.to identify the people that will be assigned to records
B.to describe when a record should be assigned to candidates
C.to identify the types of data to assign using Assignment Manager
D.to evaluate all people for a matching skill in order to assign records
7. Which statement is true regarding making changes to assignment rules?
A.To make changes you must first deactivate the rule.
B.If you make changes to a released assignment rule, you must release the rule again.
C.Changes to a released assignment rule take affect automatically when the record is saved.
D.Once an assignment rule is released it cannot be changed, it must be revised before it can be edited.
8. Which two statements concerning interface tables are true? (Choose two.)
A.An interface table can populate only one base table.
B.An interface table may populate more than one base table.
C.A base table may be populated by more than one interface table.
D.A base table is always populated by one and only one interface table.
9. When should you use implicit primaries through Enterprise Integration Manager?
A.any time you have more than one child record in the dataset
B.when you need to have multiple primaries associated with a record
C.when the external system defines which child record should be the primary
D.when the external system does not define which child record should be the primary
10. Your Accounts.ifb file appears as follows:
[Siebel Interface Manager]
USER NAME = "SADMIN"
PASSWORD = "SADMIN"
PROCESS = Import Accounts
[Import Accounts]
TYPE = Import
BATCH = 100
TABLE = EIM_ACCOUNT
After running the import, you find that the IF_ROW_STAT for all of your accounts is PARTIALLY IMPORTED, yet you can see the accounts in the Accounts Administration view.
What is the most likely cause of this?
A.Not all of the required flags were set.
B.The EIM job generated an internal error.
C.Some of the required flags were set incorrectly.
D.Not all of the base tables that EIM_ACCOUNT maps to were populated.
E.EIM_ACCOUNT did not contain required information for the S_ACCOUNT base table.
Answers
1. C
2. A
3. AB
4. ACF
5. BC
6. C
7. B
8. BC
9. D
10.D
A.Siebel.exe file
B.Siebel template files
C.Cascading style sheets
D.SQL scripts to change the data model
2. Which Link property must be populated for a MVG with a M:M relationship, but is not populated for a MVG with a 1:M relationship?
A.Inter Table
B.Destination Field
C.Child Business Component
D.Parent Business Component
3. You have enabled the Workflow Management component group on the server through the Siebel user interface, but you are unable to run workflows using Workflow policies. Which step might have you forgotten to execute? (Choose two.)
A.restarting the Siebel Server service
B.running a Generate Triggers batch job
C.enabling the Generate Triggers component
D.setting the Workflow Policy properties in Tools
E.specifying the triggering event in the detail applet for the workflow step branch following the Start Step
4. Which three are true about a task in Siebel task UI? (Choose three.)
A.It implements process automation.
B.It must be invoked by a run-time event.
C.It consists of a sequenced set of views.
D.It does not support conditional processing.
E.It does not support transactional processing.
F.It is designed for novice users performing complex tasks.
5. Business rules consist, in part, of concepts. Which two are examples of concepts? (Choose two.)
A.Field
B.Entity
C.Value
D.Object
6. Which describes the role of Assignment Objects for Assignment Manager?
A.to identify the people that will be assigned to records
B.to describe when a record should be assigned to candidates
C.to identify the types of data to assign using Assignment Manager
D.to evaluate all people for a matching skill in order to assign records
7. Which statement is true regarding making changes to assignment rules?
A.To make changes you must first deactivate the rule.
B.If you make changes to a released assignment rule, you must release the rule again.
C.Changes to a released assignment rule take affect automatically when the record is saved.
D.Once an assignment rule is released it cannot be changed, it must be revised before it can be edited.
8. Which two statements concerning interface tables are true? (Choose two.)
A.An interface table can populate only one base table.
B.An interface table may populate more than one base table.
C.A base table may be populated by more than one interface table.
D.A base table is always populated by one and only one interface table.
9. When should you use implicit primaries through Enterprise Integration Manager?
A.any time you have more than one child record in the dataset
B.when you need to have multiple primaries associated with a record
C.when the external system defines which child record should be the primary
D.when the external system does not define which child record should be the primary
10. Your Accounts.ifb file appears as follows:
[Siebel Interface Manager]
USER NAME = "SADMIN"
PASSWORD = "SADMIN"
PROCESS = Import Accounts
[Import Accounts]
TYPE = Import
BATCH = 100
TABLE = EIM_ACCOUNT
After running the import, you find that the IF_ROW_STAT for all of your accounts is PARTIALLY IMPORTED, yet you can see the accounts in the Accounts Administration view.
What is the most likely cause of this?
A.Not all of the required flags were set.
B.The EIM job generated an internal error.
C.Some of the required flags were set incorrectly.
D.Not all of the base tables that EIM_ACCOUNT maps to were populated.
E.EIM_ACCOUNT did not contain required information for the S_ACCOUNT base table.
Answers
1. C
2. A
3. AB
4. ACF
5. BC
6. C
7. B
8. BC
9. D
10.D
17 December 2010
Pre Default & Post Default
Post Default Value:
The value used for an empty field when the record is initially written to the database. This value is not used if the field is left empty on subsequent updates to the record. The post-default value for the field is used even when the field is not exposed in the user interface.
This property is not validated for a calculated field.
Pre Default Value:
The value used for an empty field when a new record is created through an Add New Record or Copy Record operation. The value can be changed by the user before the record is written to the database. The pre-default value for the field is used even when the field is not exposed in the user interface.
This is true for Copy Record operation only if the No Copy property is set to TRUE.
This property is not validated for a calculated field.
Long List:
A TRUE or FALSE value that specifies whether the Siebel application should attempt to position the cursor on the current value in a long list of values.
When you specify Long List = TRUE for a picklist list, the Siebel application does not keep focus on the current record.
A value of TRUE means that the picklist returns a large set of values, so to scroll through that list of values and position the cursor on the current value in the field could be very costly from a performance standpoint. For this reason, Long List does not keep focus.
TRUE = Recommendation is to set this attribute to TRUE if pick list is expected to contain more than 500 records.
The value used for an empty field when the record is initially written to the database. This value is not used if the field is left empty on subsequent updates to the record. The post-default value for the field is used even when the field is not exposed in the user interface.
This property is not validated for a calculated field.
Pre Default Value:
The value used for an empty field when a new record is created through an Add New Record or Copy Record operation. The value can be changed by the user before the record is written to the database. The pre-default value for the field is used even when the field is not exposed in the user interface.
This is true for Copy Record operation only if the No Copy property is set to TRUE.
This property is not validated for a calculated field.
Long List:
A TRUE or FALSE value that specifies whether the Siebel application should attempt to position the cursor on the current value in a long list of values.
When you specify Long List = TRUE for a picklist list, the Siebel application does not keep focus on the current record.
A value of TRUE means that the picklist returns a large set of values, so to scroll through that list of values and position the cursor on the current value in the field could be very costly from a performance standpoint. For this reason, Long List does not keep focus.
TRUE = Recommendation is to set this attribute to TRUE if pick list is expected to contain more than 500 records.
16 December 2010
Extension Tables
What is Extension table?
Base table has default columns. Preconfigured extension tables are called Static extension tables and includes generic columns ATTRIB_01 ATTRIB_02...., are the customizable columns which you can use for your purpose other than given by Siebel (ATTRIB_) that you can use to store custom attributes. Static extension tables are already part of the data model so using them does not require updating the physical database. Is it possible to add base and extension table for the same BC? You can also create your own extension tables using the New Table Wizard. Extension tables that you create are changes to the logical schema and therefore must be also be applied to the physical database. Creation of base table is not possible.
Base table has default columns. Preconfigured extension tables are called Static extension tables and includes generic columns ATTRIB_01 ATTRIB_02...., are the customizable columns which you can use for your purpose other than given by Siebel (ATTRIB_) that you can use to store custom attributes. Static extension tables are already part of the data model so using them does not require updating the physical database. Is it possible to add base and extension table for the same BC? You can also create your own extension tables using the New Table Wizard. Extension tables that you create are changes to the logical schema and therefore must be also be applied to the physical database. Creation of base table is not possible.
Difference between MVG and Dynamic Picklist
What is the difference between MVG & Dynamic PickList?
MVG applet displays the related child records for the parent record. MVG uses link object.
Dynamic picklist displays all the child records for the parent record. It uses join object.
MVG applet displays the related child records for the parent record. MVG uses link object.
Dynamic picklist displays all the child records for the parent record. It uses join object.
Subscribe to:
Posts (Atom)