Applies to:
Siebel Tools - Version: 7.7.2 SIA [18325] to 8.0 [20405] - Release: V7 to V8z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.7.2.4 [18365]
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1
Symptoms
Hi,In the ‘Service Request Detail Applet’ for ‘Assigned To’ field we were introduced the new personalization Rules. As per the rules it is displaying the records in the Pick Applet .But when users are typing it manually it is allowing the data though the records are not displaying in the pick applet.
Could you please advice to resolve it?
Ex: when CSA1 logins the application in the Assigned to Field should not allow CSA2 to CSA13.It is happening when user clicks the pick applet and selects. But when the user types manually CSA2 and click save it is allowing.
Details of the configuration.
Applet Name: Service Request Detail Applet
Business component: Service Request
Field: Owner
Pick List: PickList SR Owner
Pick Applet: SR Owner Pick Applet
Properties of the Pick list:
Bounded: TRUE
LongList/NO Insert/No Delete/No update/ No Merge: TRUE
PFA the personalization rules, Service Request BC sif and Service Request Detail Applet sif.
Thanks,
Cause
On looking through the personalization.xml file (thank you for adding this) and found only one entry for the 'SR Owner Pick Applet'. The expression for this is GetProfileAttr('Is Anonymous') = 'FALSE'. Can you confirm that this is correct and is the only personalization rule that is relied on for this issue please? I also checked the Service Request Detail Applet and found no rules for this.The reason I ask is the expression of GetProfileAttr('Is Anonymous') = 'FALSE' only checks that the user is logged in and not any of their responsibilities or user rights.
Solution
Thank you for using SupportWeb. I have taken ownership of the service request you recently submitted to Siebel Technical Support .
I have loaded in your sif files for the Service Request BC and the Service Request Detail Applet and noted that you have changed the 'Owner' field to be the 'Assigned To' field. I then compiled the BC and applet in to a standard test environment. Unfortunately the error message of 'Multi valued link 'SR PC Enabled' refers to nonexistent business component 'SR PC Enabled' in business component definition for 'Service Request'(SBL-DAT-00465)' was displayed. Rather than ask for the MVL, I will set this up using the standard environment.
As you have mentioned, the 'Owner' field is a standard field. The pick applet on this field is the 'SR Owner Pick Applet', which is also standard.
I had a look through the personalization.xml file (thank you for adding this) and found only one entry for the 'SR Owner Pick Applet'. The expression for this is GetProfileAttr('Is Anonymous') = 'FALSE'. Can you confirm that this is correct and is the only personalization rule that is relied on for this issue please? I also checked the Service Request Detail Applet and found no rules for this.
The reason I ask is the expression of GetProfileAttr('Is Anonymous') = 'FALSE' only checks that the user is logged in and not any of their responsibilities or user rights.
This would then not sort or show different values for the SR Owner Pick Applet as you describe for different users. Can you let me know the steps to re-create your issue please as this would help greatly?
In addition to the suggest I gave you, I have also requested an Enhancement Request (#12-1D3YNWP) for this issue. I hope that this is helpful.
Kind regards,
Siebel Technical Support
Applies to:
Product Release: V7 (Enterprise)Version: 7.5.3 [16157] CSY Cons Sec
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Compaq Tru64 UNIX
This document was previously published as Siebel SR 38-1612393501.
Symptoms
SBL-DAT-00465We have a custom piece of code that converts a Product Bundle into individual Order Line
Items. If a new Order Line Item is required, a new record is created, the PickList Business
Compenent is instantiated for the product, a query is performed to search for the particular
product and then executed. If the product is located, it is picked.
The problem we are
having is that the query only intermittently locates the Product.
Sometimes, it will not find
the product on the first occasion, you go to another screen and
come back and it works fine.
Other times when I've tried that, it doesn't work. Sometimes it
works on the first occasion,
other times it doesn't. If it doesn't find it the first time,
trying it again and again
doesn't make any difference, it still doesn't work.
The code in question is a custom
function called 'CreateOLIs' in the Order Entry - Line Items Business Component. This is invoked
from the PreInvokeMethod code for the 'Unbundle' method, which is itself invoked from a button on
the line items applet.
The Products exist in the appropriate organization and are
Orderable.
The search expression used in the query for Products in the PickList Business
Component is
formed correctly, resolving the Product name appropriately.
I have been
testing this on a dedicated client with a local srf on the server database.
I have
attached sifs of the Order Entry Line Items business component and applet, the Internal Product
business component and the picklist under the Line Item's Product field.
This is a key
area of our order managment process and as such we cannot go live without it. Your help to
resolve this is most appreciated. Please feel free to ring me on the number below.
ALEX
MAKEPEACE
07958 978 396
Solution
Message 1
For the benefit of other users.The customer was using some scripting that queried a customer BC for a particular record. Even though the record existed in the Business Component the query did not find the record. The customer’s script was correct. After some investigation and generating the SQL that was used to query the Business Component it was found that the customer had SearchSpecs defined at the applet level and the BC level and also the picklist level. These SearchSpec criteria was been concatenated onto the query that was been generated buy the script. When the picklist query was removed the script query returned the correct information.
Thank you,
Siebel Technical Support
Keywords: ExecuteQuery, ClearToQuery
No comments:
Post a Comment