Section - 1 : Understanding Mobile Processing


Oracle Documaker Mobile provides the ability to render output for devices such as iOS, Android, and laptops. It does so by leveraging the existing capabilities in Documaker to define content, triggers, and data mapping elements while adding in new elements that allow Documaker to render output for various device targets, including mobile, instead of page based targets such as print or PDF.

These new elements, snippets, scripts, widgets, etc., combined with the document content provide the responsive user experience.

Documaker Mobile processes each object of document content through a snippet file.

Image represents Oracle documaker mobile processing.
Figure 2.1.1 - Oracle Documaker Mobile Processing

The snippet, or layout file, contains presentation markup and keywords that are replaced by the properties and values of the document content being processed. For example - each field in the document content will be processed with the field snippet designed to output the name of the field, the font used for the field, and the value populated into the field using keywords as shown here:

<FLD N="documaker.name" F="documaker.font.id">documaker.text</FLD>

When a field in the document content is processed through this snippet by the Mobile Responsive Output (MRO), all the snippet content is written as output and the keywords, also known as replacement tags, such as: "documaker.name", "documaker.font.id" and "documaker.text". These will be replaced with field's name, font ID and content text respectively. By default, similar snippets are defined for objects other than fields and the output from Documaker Mobile represents processing of all objects within the document via this snippet transformation technique. Note that the format of the final mobile output is dependent upon the snippets used to process the document content.

Once the mobile output is ready, it can be delivered to the recipient through one of many channels. Mobile output can be placed / stored on a file system, pushed to the Oracle WebCenter product or to other targets such as FTP, or returned to a calling application using Documaker Enterprise's DWS web service interfaces. For more information about possible delivery options, see the topic on Delivering Mobile Output.

Image represents Oracle documaker mobile processing.
Figure 2.1.2 - Oracle Documaker Mobile Processing

As discussed in the overview, generating mobile output relies on the contents of snippet files to determine the final output format. Let's take a closer examination of how snippets are used by the system.