User properties in siebel are as thrilling as gadgets in bond movie. Yes, we can define visibility view modes at integration object level. "ViewMode" user property defined at IC level does the magic. This user property can take different values, as defined by LOV type " REPOSITORY_BC_VIEWMODE_TYPE" . However,as i keep saying the beauty of siebel is the flexibility it provides. One can even use "ViewMode" input argument in the Query/Query Page methods of " EAI Siebel Adapter " business service. However this argument is not exposed in the tools but one can use it. We can see presence of this argument in Query method of another business service " XMLP Siebel Adapter ", which is used in the BIP reporting. This BS can also be used to extract the siebel message. Happy Crunching!!
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to set Profile Attributes from browser-side script. But getting them is not a problem, since the GetProfileAttr function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position: returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of ...
Applies to: Siebel Reports - Version: 8.1 [21039] and later [Release: V8 and later ] Information in this document applies to any platform. Symptoms When running a BI Publisher report from the Siebel web client and having selected an output format for the report an error message is returned : XMLP Report Generation time exceeds the Threshold time. If you then navigate into the Site Map > BIP Reports Server > My Reports and try to drilldown on the generated report a different error is returned : SBL-SVC-00155: No file has been attached to this record. Please attach a file. Cause Having increased the logging levels on the XMLP Report Server component, restarted it, and then re-tested the behavior it was evident from a review of the log file that the timeout errors were occurring because the XMLP Report Server component was unable to connect to the BI Publisher Server within the Timeout period. Evidence of this can be seen in the log file excerpt below : EA...
תגובות
הוסף רשומת תגובה