Integration Platform Technologies: Siebel Enterprise Application Integration > Siebel Virtual Business Components > About Virtual Business Components >

Usage and Restrictions for Virtual Business Components

The following are the uses and restrictions of VBCs:

  • You can define a business object as containing both standard business components and VBCs.
  • When configuring applets based on VBCs, use CSSFrame (Form) and CSSFrameList (List) instead of specialized applet classes.
  • (Optional) Using the same name for the VBC field names and the remote data source field names can reduce the amount of required programming.
  • VBCs cannot be docked, so they do not apply to remote users.
  • VBCs cannot contain a multivalue group (MVG).
  • VBCs do not support many-to-many relationships.
  • A pick applet based on a VBC instantiates the VBC without any parent reference (no link is used). As result, the VBC business service does not receive the source field value from the parent component If the VBC business service must access the current parent business component context, then you can use the ActiveBusObject method of the TheApplication object in a business service server script to do the following:
    • Obtain the current business object instance (assuming this is the instance with this VBC).
    • Instantiate the parent business component (assuming the name of the parent BC is known).
    • Obtain the parent business component field for referencing it as a source (the field must be active in the current parent business component).
  • VBCs cannot be loaded using Enterprise Integration Manager.
  • Standard business components cannot contain multivalue groups based on VBCs.
  • VBCs cannot be implemented using any business component class other than CSSBCVExtern. This means specialized business components such as Quotes and Forecasts cannot be implemented as VBCs.
  • You cannot use Workflow Monitor to monitor VBCs.
  • You cannot execute queries against VBCs when the search specification uses a function that is normally supported for Query mode against regular business components, such as ParentFieldValue().
Integration Platform Technologies: Siebel Enterprise Application Integration Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.