Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TagExample / Visual effect

<b></b>


Defines bold text


<i></i>


Defines italic text

<u></u>


Defines underlined text

</br>


Inserts a single line break
Moves cursor to new line

</line>


Inserts a custom line break (with visual line separation)

<a href='URL' 'Text' ></a>

Defines a hyperlink.

Where URL placeholder is a target URL and Text is a string of text to be displayed as clickable hyperlink.

${}

Inline placeholder represented by customer defined field. Customer defined field must be first configured in appropriate field configuration of MSA before using it as a placeholder.

Each placeholder must be individually handled via custom BAdI implementation (similar to customer defined fields).

Example placeholder definition:

${/DBE/VBAK_DB-/PACG/TEST}


  • CHECKBOX – slider (used in multi selection forms)

Any number of checkboxes / sliders can be defined as an element of a handover screen. Each slider can be supplemented with text element (SO10).

Image Added

Checkbox - multiselection
  • RADIO – slider (used in single selection forms)


Any number of checkboxes / sliders can be defined as an element of a handover screen. Each slider can be supplemented with text element (SO10). Sliders of this type offer single selection (one out of a group).

Image Added

Checkbox - Single selection


  • YES_NO – single choice field in form of button with Yes / No answer

Image Added

Yes/No Question
  • SIGNATURE – Signature area including name and email fields


Signature area supplied with name and email field. Multiple signature areas can be included in one handover screen.

Signature is brought in focus when tapped to make signature capture easier.

Name and email fields are free text fields supplemented with type ahead function. Type ahead function takes under consideration customer and contacts included in the order.

Image Added

Signature element

Selection of mentioned screen elements brought together compose handover screen. All elements are displayed right above list of jobs allowing to summarize the content of the order and move forward with i.e. legal agreements and signature.

After data transfer to SAP, data collected on handover screen are saved in dedicated database table with reference to the order number.

It is important to mention that configuration / layout of the screen is derived from MSA configuration only for the first time. Once its saved, it gets retrieved from the database table assuring that any change to the configuration does not affect the screen content approved and signed by customer during order processing.

Example of handover screen:

Image Added

Handover screen example