Skip to main content

How to get Siebel attachment as file in Workflow

You might need to extract a specific file from Siebel Attachments or want to attach that file in Email as attachment. To achieve that Siebel provide a vanilla business service which will get file and return its path.

  • Prepare the workflow and drag drop the Business Service step on workflow canvas.
  • Open properties and set the as below:
    • Business Service Name: FINS Industry BC Facility Service
    • Business Service Method: GetFile
  • Now go to "Multi Value Property Window" and add the below Input Arguments:
    • AttachmentId > Row Id of specific attachment which you want to get as file.
    • BusObjName > Business Object name in which Attachment Business Component is present.
    • FileBusCompName > Attachment Business Component Name.
    • FileNameField > Attachment Name Field. If you are not sure which field is in your case, query "FILE_NAME" in Business Component Column and use that Field Name which query will return.
    • RootBusCompName > If Attachment Business Component is child set the name of Primary Business Component of Business Object defined previously.
    • RowId > If Attachment Business Component is Primary Business Component of Business Object pass the Row Id of specific attachment otherwise Row Id of Parent Business of Attachment Business Component.

gf01
 

  • Now add the Output Arguments:
    • create or use existing process property and set as below shown in screen shot:
gf02


  • When runing the workflow on Web Client (Server) attachment this Business Service will save the attachment on below path:
    • C:\Siebel\xx.0.0.0.0\ses\siebsrvr\temp\S-WEB-APP_8364_9620_0_Attachment Name.pdf
  • On Dedicated Client path will be:
    • c:\Siebel\xx.0.0.0.0\Client\temp\S-WEB-APP_9928_5760_0_Attachment Name.pdf


You might get error: Field "FileExt" does not exits in Attachment Business Component. For resolving your need to query "FILE_EXT" in Column. Either make clone of that field and set name to "FileExt" or rename that field to "FileExt".

Comments

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...