Skip to main content

Mobile Forms Document Design Notes

Updated over 2 months ago

Document designs for mobile forms can be complex or simple. You can choose to link the document to a specific mobile form. Doing this means you can set up document forms (Header and Body) for each section of the form. It also allows you to have Images and Workflow forms against sections if you want to have these next to the section they pertain to. The alternative is to have Image and Workflow sections at the end of the document (or not at all).

Simple

A simple document could be configured with a HEAD form only, and not be linked to a specific mobile form.

RW_smk_field can be used to pull values from the fields of the form. By default it gives the field value, but it can alternatively return the values of associated checklist, comments on the field, or the field label.

Parameters are either:

<Section#>|<element#>|<field#> [|<alternative field>]

or

<FID> [|<alternative field>]

Alternative field options are

  • Blank to get the field value (sme_value)

  • sme_text to get the field comments

  • sme_xlist for checklist values (code and description)

  • sme_xlist_codes for checklist (just codes)

  • label for the label from the mobile form

Complex

Even with a complex mobile form you could use a single HEADER form and use RW_smk_field to access values from fields. You have full control of field placement, but it does mean you need to define every field you use. If you use the section HEAD and BODY forms you can define less and use the same definition repeatedly.

The HEADER form for a section can use field smg_title to show the section title.

The body table for a section will be elements if they are used, otherwise the fields of the section.

RO_RowFile^<section#>|<field#> can be used to print images like signatures.

BODY - Section Using Elements

Field smy_desc gives the element text and the RO_sme_* fields used to access fields of the section and element.

  • RO_sme_value__n with return the value for the nth field in the section.

  • RO_sme_text__n returns field comment

  • RO_sme_xlist__n returns checklist (code and description)

  • RO_sme_xlist_codes__n returns checklist (codes only)

BODY - Section Without Elements

When the body table is the fields you can use sme_value, sme_text, etc.

Workflow

For a workflow BODY form – of a section or the overall – the body table is sy_mobcwf and you can use fields:

  • wfp_code - the workflow template

  • smw_due the due date

  • smw_text – comments

  • RO_smw_origin – combined section and element the workflow belongs to

  • RO_smw_smy_desc – the element the workflow belongs to

  • RO_smw_smg_title – section the workflow belongs to

Image Sections

The dm_pagelist and dm_document RSP are primed for each document or image linked to this mobile form, with the exception of those that have already been displayed with RO_RowFile^.

Images

You can use RO_ImagePic^ and RO_ImageDesc^ to have multiple images and their descriptions on a row.

Did this answer your question?