Form definitions are in a sense shared between self service application and the base product. Both systems rely on the metadata when rendering forms on screen and applying various business rules on the form data.
The solution provides the ability to import form type definitions into the self service product.
The self service product operates with generic form data model. The requests originated from the self service product contain the form data in this format:
<formData> <id/> <name/> <section type="list"> <id/> <name/> <sequence/> <line type="list"> <field type="group"> <id/> <name/> <dataType/> <value/> </field> </line> <table type="list"> <id/> <name/> <tableRow type="list"> <sequence/> <field type="list"> <id/> <name/> <dataType/> <value/> </field> </tableRow> </table> </section> </formData>
The form processing integration flow assumes that for the form of a certain type the names of the elements on the generic form data model (sections, lines, tables etc) exactly match the business names of the elements on the form type definitions. This assumption allows an automated transformation of the generic form data XML into form business object XML based on the form type definition.
The base product provided with the business services C1-TransformFormToGenericWeb and C1-TransformGenericWebToForm for the form data conversion.
Fastpath: Refer to the Import Form Definition for more information
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]