The base product provides the C1-FormUploadStagingType business object. This object maps all of the fields on the maintenance object plus additional fields (in the CLOB) for the suspense To Do Type and To Do Role. Since the form upload staging type does not have a soft status, C1-FormUploadStagingType does not have a lifecycle.
Use the base BO if the structure suits your form upload staging types. Otherwise, you can either subclass the BO or create an entirely different BO. Refer to existing help on configuration tools for more details on configuring business objects.
When opting to use the C1-FormUploadStagingType BO and your chosen mapping technique is not XSLT, you need to do the following:
Inactivate the base algorithm C1-FUST-XSLT (FUS Type - XSL Transformation) by adding a BO option to C1-FormUploadStagingType with:
BO option type = Inactivate Algorithm
BO option value = C1-FUST-XSLT.
Plug in your CM algorithm on the Map Form Upload Data to Target Form plug-in spot on the C1-FormUploadStagingType BO.
C1-FormUploadStagingType also has BO options for automatic rendering of raw XML data on the UI.
Display HTML Generator XSL Stylesheet = @SPLEBASE@/splapp/resources/xsl/c1FormUploadStagingUIMapForDisplay.xsl
Schema Extractor XSL Stylesheet = @SPLEBASE@/splapp/resources/xsl/c1FormUploadStagingSchemaForUIMap.xsl
Maintenance HTML Generator XSL Stylesheet = @SPLEBASE@/splapp/resources/xsl/c1FormUploadStagingUIMapForInput.xsl
If your implementation needs to render the raw XML data in a different way, you simply add option values for these three option types, using a higher sequence number. (For 'single' BO option types, the framework knows to get the highest sequence number.)
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]