Sample XML Data for Custom Templates (Custom Prints and Reports)

In case of a Custom Print, the sample data contains data elements that will be used in the layout files to capture information about a business process (BP).

Some data elements are specific to the business process selected as they map to the standard and custom elements included in the BP forms.

If you have an image picker Data Element (DE) on your BP form, the sample data includes the XML element, which provides the data for the ID that corresponds to the image as well as the name of the image.

Example

If the image picker DE "AE_Image" is placed on the BP form, the generated data XML will have the "AE_Image" DE, which provides value for the uploaded image name, and the "k__AE_Image" DE, which provides value for the uploaded image ID.

You must use the image ID in the Oracle Analytics Server template for the custom print of the BP.

There are some data elements present in the sample data for all the BPs because they apply to all. These data elements provide information such as record attachments, attachment comments, line item attachments, workflow steps, and so forth.

Notes:

In the Internal Multiple Data Model Type, the top-level data set is the project_company_info. This must be the first grouping because the Internal Multiple Custom Print template can be selected for multiple business process records from the Tasks log, Business Processes log, or Master log. These pages display business process records from multiple shells that the user has access to (permission). This data set has fields providing information of the company and project with which the BP record is associated.
All other data sets are children to this data set.
If the Data Model includes multiple levels, you must add each level to the path; for example, use: ./<level1>/<level2>.../<PROJECTIMAGE>
Each XML Data Element Group represents a unique data set in the data model uploaded to the Oracle Analytics Server and has a field that its value uniquely represents the record.
The unique field in each data set is the field to be used as a group-by field on the template for rendering the data grouped under the BP record.
The unique fields are important to the template designers because of the layout and the data that needs to be displayed on the Oracle Analytics Server Custom Print output.
The unique field in each data set can be suffixed by a number. This applies to other data sets as well as a similar field.
The number suffix is added automatically to maintain the uniqueness of the field across the data sets. This is used by the Oracle Analytics Server for the correct grouping of the data. For example, for multiple ID fields in different data sets, the ID field appears as: <ID_3></ID_3>.

The following is a list of data elements and their descriptions:

<li_attachments>

Unique Field: <ID_<<no>>>..</ID_<<no>>>
The sub-elements under this provide information about line item attachments for the business process when the business process has line items.

<lic_attachments>

Unique Field: <ID_<<no>>>..</ID_<<no>>>
The element is a child of <la_comments> and its sub-elements provide information about attachments linked to the comment of line-item attachment.

<li_ca>

Unique Field: <ID_<<no>>>..</ID_<<no>>>
The element is a sub-element that provides information about cost allocation line item element for Summary Payment Application of SOV type BP.

<la_comments>

Unique Field: <. Unique Field: <COMMENT_ID_<<no>>>..<COMMENT_ID_<<no>>>
This element is a child of <li_attachments> and its sub-elements provide information on the comments associated with the line-item attachment.

<standard_elements>

This is applicable to Custom Print of Data Model Type Internal.
The sub-elements of this group element provide information about company name, project name, project number, and so on.

<general_comments>

Unique Field: <. Unique Field: <COMMENT_ID_<<no>>>..<COMMENT_ID_<<no>>>
The sub-elements of this group element provide information about general comments on the business process.

<gc_attachments>

The element is a child of <general_comments>and its sub-elements provide information about attachments linked to the general comment.

<record_attachments>

Unique Field: <ID_<<no>>>..</ID_<<no>>>
The sub-elements under this provide information about record attachments for the business process.

<ra_comments>

Unique Field: <COMMENT_ID_<<no>>>..<COMMENT_ID_<<no>>>
This element is a child of <record_attachments> and its sub-elements provide information on the comments associated with the record attachments.

<rac_attachments>

Unique Field: <ID_<<no>>>..</ID_<<no>>>
The element is a child of <ra_comments> and its sub-elements provide information about attachments linked to the comment of record attachment.

For workflow business processes, there are additional elements that provide information about the workflow process and its details. The following is a list of data elements:

Unique Field: <ID_<<no>>>..</ID_<<no>>>

<workflow_steps>

<WF_PROCESS_ID></WF_PROCESS_ID> Process Id
<SOURCE_ID_1></SOURCE_ID_1> BP record Id
The sub-element of this element provides information about the workflow steps associated with the business process. Details like step name, step assignees

<task_assignees>

<WFTEMPLATE_ID></WFTEMPLATE_ID>
<OracleAnalyticsServer_SOURCE_ID></OracleAnalyticsServer_SOURCE_ID>
<OracleAnalyticsServer_WF_PROCESS_ID></OracleAnalyticsServer_WF_PROCESS_ID>
The sub-element of this element provides information about task and assignee details. Information like Task name, Task Status, Assigned From, Assigned To and more

<workflow_progress>

<WF_PROCESS_ID></WF_PROCESS_ID> Process Id
<SOURCE_ID_1></SOURCE_ID_1>
The sub-elements of this element provide information about status of the workflow.

<group_assignment_notes>

<PROCESS_ID></PROCESS_ID>
<STEP_ID></STEP_ID>
The sub-elements of this element provide information about the notes sent when a task is assigned to the group in the workflow process.

See Also