Section - 3 : Mobile Output Management Workflow

We have reviewed a number of possible use cases for managing mobile output. The following presents the possible workflows from the end user experience:

  1. Customer signs on to the company portal.
    1. This could be triggered by a notification that a document is available.
    2. This notification can be sent by or triggered by Oracle Documaker and can occur when the mobile output is generated or when the data is available to generate the mobile output
  2. Portal authenticates customer and presents customer with options to view available mobile documents
  3. Customer selects a mobile document, or activity if the mobile document is not yet created, for viewing
  4. The portal can then do one of three things:
    1. If the mobile output is already generated and stored in the content repository serving the portal, the portal can display the mobile output from its own repository.
    1. If the mobile output is already generated and still available in Documaker's Assembly Line tables the portal can use Documaker Web Services.
    2. If the mobile output is not generated, the portal can use Documaker Web Services to generate the mobile output on demand.