FLM Form Manager (UI5 Portal) Features

Overview

This document describes the features of the FLM Form Manager. 

To allow for better use the following features can be accessed directly.

  • Viewing Inbox
  • Viewing Draft FLM Forms
  • Viewing Template Library
  • Viewing History
  • Starting a New FLM Form
  • Opening an Assigned FLM Form

Main URL: http://<SERVER>:<ABAP Port>/sap/bc/bsp/flmui5/portal/entry.htm

Mobile Client URL: http://<SERVER>:<ABAP Port>/sap/bc/bsp/flmui5/dispatcher/entry.htm

Latest Updates

For the latest updates and bug fixes see the Form Manager Notes.

 

FLM Form Manager Dispatcher

As can be seen by the urls in section 1 there are two paths that can be used to access the FLM Form Manager.  The first url links directly to it and does not inspect the user-agent of the web browser making the connect.  The second 'dispatcher url' inspects the user-agent and allows certain aspects of the interface to be customized. For this reason it is recommended that the ‘dispatcher url’ is allways used.

Maintain Device Characteristics

This IMG activity can be found in Cross-Application Components -> General Application Functions -> Forms Lifecycle Manager -> Initialize Customer Code -> Advanced Settings

It allows an administrator to create a set of characteristics for certain device types. The system uses the 'user-agent' from the device browser to identify which type of device is making the call to FLM.  In order to recognise a certain device enter a unique section (or all) of the device's user-agent into the key field and then maintain the other characteristics as you require.  Please note that these settings will affect both the FLM Multi-UI Portal and the FLM Form Manager.

The following settings can be made:

  • UI Types Supported: Here you can set whether a certain device supports PDF forms, HTML forms or both. If a device is set to support HTML forms only for example, all form types for which an html template has not been maintained will not appear in the portal.
  • Disable SSL: Here you can indicate whether a device supports SSL or not. If SSL is supported the portal will be launched in https, otherwise it will be launched in http.
  • No tabs: This setting is for the MultiUI portal only.
  • MUI Portal Design: This setting is not applicable to the FLM Form Manager.
  • SAPUI5 Login Screen:  Here you can specify whether users will be presented with the standard desktop login screen or the mobile one.
  • Device Block: Indicates whether certain devices are blocked from accesing the portal or not.

Requirements

If no entry is made for a particular device, FLM will assume standard settings as follows:

  1. that the device supports the use of both HTML and PDF templates
  2. that the device supports SSL
  3. that the device supports tabbed browsing in htmlb
  4. that the device is not blocked

Standard settings

In order to recognise a certain device enter a unique section (or all) of the device's user-agent into the key field and then maintain the other characteristics as you require.  Give the device a human-readabe name simply to aid maintainance, this name has no functional impact. Only maintain 1 entry per device type. A blocked device will not be able to access the FLM Portal at all.

For further documentation for each characteristic please consult the F1 help in the IMG.

 

Authorizations and Clients

The normal SAP and FLM authorization model applies the FLM Multi UI Portal.

SAP Clients

If FLM is installed on multiple SAP Clients access to different Clients can be controlled by adding the SAP &sap-client URL parameter.

http://<SERVER>:<ABAP Port>/sap/bc/bsp/flmui5/dispatcher/entry.htm?sap-client=800

Passing Users

Adding the &user parameter initiates another authorization check within FLM to ensure that the user logged in is the user accessing the form via the URL.  If this value is left blank the logged in user is used. This would be used in an offline (email) group access scenario where multiple users may be authorized to access a form. It is assumed that the FLM URL encryption/scrambling setting in the Customer Code will be used so that the &user parameter can't simply be removed from the URL.

http://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/dispatcher/entry.htm?user=USER1

Enterprise Portal Integration

The FLM Form Manager can be integrated with the SAP Enterprise Portal via URL or BSP iViews.   To ensure you aren't asked to reauthorize when connecting to the Multi UI Portal you must have Single-Sign-On (SSO) configured.

URL Encryption

When using encrypted URLs as defined in the FLM Customer Code settings if a key is maintained but an unencrypted URL is received by the Portal it will be considered a security breach and an authorization error will be generated.

Generated URLs

From 295 SP3 onwards any form generated via the Form Wizard for use with the BSP transport mode 'B' will have the URL of the new Multi-UI FLM Portal derived.  Older forms will continue to derive the URL of the original BSP application /flm/pdf_viewer.  The system detects at which release a form was generated by inspecting the form class attributes.  Hence the situation can be forced either way simply by altering these two attributes as required.

Customizing Logon Screen

The FLM Form Manager Portal Logon screen and default behavior can be customized by accessing the appropriate SICF Node.

For more detail see the FLM Authorizations and Security Guide.

 

Viewing Pages Directly

The ‘New Form’, ‘Inbox’, ‘Draft Forms’, ‘Template Forms’ and ‘History’ pages can all be accessed directly by the end user and this will show the pages as standalone views. After launching a form from one of these views and submitting (or closing) it users will be returned to the view the form was launched from. This allows customers to integrate the FLM Form Manager into their own SAP Enterprise Portals and also other web sites as seamless content. The below image shows an example of how this might look.

For the four view options below the FLM Logo, Logout Button and navigation panel can be suppressed with the URL parameter no_head=X (i.e. inbox.htm?no_head=X) and the user will be locked into the referenced section of the Portal.

The Portal also recognizes the "No Logo Section" and "No Logout Button" options defined in the FLM Customer Code.

  • New Form View

To directly launch the New Form View, the following url can be used:

http://<SERVER>:<ABAPPort>/sap/bc/bsp/flmui5/dispatcher/directview.htm?flmtask=SHOWNEWFORM

  • Inbox View

To directly launch the Inbox View, the following url can be used:

http://<SERVER>:<ABAPPort>/sap/bc/bsp/flmui5/dispatcher/directview.htm?flmtask=SHOWINBOX

  • Draft Forms View

To directly launch the Draft Forms View, the following url can be used:

http://<SERVER>:<ABAPPort>/sap/bc/bsp/flmui5/dispatcher/directview.htm?flmtask=SHOWDRAFT

  • Template Forms View

To directly launch the Template Forms View, the following url can be used:

http://<SERVER>:<ABAPPort>/sap/bc/bsp/flmui5/dispatcher/directview.htm?flmtask=SHOWTEMPLATES

  • History View

To directly launch the History View, the following url can be used:

http://<SERVER>:<ABAPPort>/sap/bc/bsp/flmui5/dispatcher/directview.htm?flmtask=SHOWHISTORY

 

Launching Forms Directly

Starting a New Form

To directly lanch a new form, the following parameters must be added to the url:

  • flmtask=NEWFORM
  • ccode=<Customer Code>
  • ftype=<Form Type>

So the url will be of the following format:

http://<SERVER>:<ABAPPort>/sap/bc/bsp/flmui5/dispatcher/directview.htm?flmtask=NEWFORM&ccode=<CUSTOMER CODE>&ftype=<FORM TYPE>

Launching an Existing Form

To directly launch an existing form, the following parameters must be added to the url:

  • flmtask=SHOWFORM
  • ccode=<Customer Code>
  • ftype=<Form Type>
  • fver=<Form Version>
  • toption=<Template Option>
  • id=<Form ID>
  • id_var=<Form Variant> (if this parameter is not specified, or has a value of 0000, the latest variant will be retrieved)
  • fmode=2 to render the form in “edit” mode or 3 to render the form in “display” mode (ie the form will be read-only)

So the url will be of the following format:

http://<SERVER>:<ABAPPort>/sap/bc/bsp/flmui5/dispatcher/directview.htm?flmtask=SHOWFORM&ccode=<CUSTOMER CODE>&ftype=<FORM TYPE>&fver=<FORM VERSION>&toption=<TEMPLATE OPTION>&id=<FORM ID>&id_var=<FORM VARIANT>&fmode=2

UWL Integration

Forms can also be launched via the UWL. In this case the flmbokey parameter will be used, so the url will be of the following format:

http://<SERVER>:<ABAPPort>/sap/bc/bsp/flmui5/dispatcher/directview.htm?flmtask=UWL&flmbokey=<CUSTOMER CODE><FORM TYPE><TEMPLATE OPTION><FORM VERSION><FORM ID><FORM VARIANT>

Additional Optional Parameters

When launching forms directly via a url, the following optional URL parameters can be used:

  • DOC = <IMDocument>  - can be used to pass additional values with a maximum of 40 characters which will become available in the user-exits (import parameter im_document).
  • user=<USER> - Adding in this parameter initiates an extra authorization check within FLM to ensure that the user logged in is the user indicated in the URL. (It is assumed that the FLM URL encryption/scrambling setting in the Customer Code will be used so that the &user parameter can't simply be removed or changed from the URL)
  • PrevPage=<URL for after form Submit> - If prevpage is used with one of the following options, the form launch is treated as a ‘portal launch’ rather than a ‘url launch’. This means that a ‘Close button’ (  will be made available above the form (unless specified otherwise in the ‘Render Control IMG’) and that if that is pressed, or if there is an error during form render, or if the form is succesfully submitted, the user will be redirected to the page indicated by the prevpage parameter:
    • TONEWFORM
    • TOINBOX
    • TODRAFTFORMS
    • TOTEMPLATEFORMS
    • TOMYHISTORY

If prevpage is not used (or is used and has none of the above values) there will be no ‘close button’ and upon submission the user will be directed to the ‘Submission page’ or a  custom submission page if the “Portal Exit Text” field is maintained in the customer master.