Multi-UI Portal Features

Overview

To allow for better use and direct control over the FLM Multi UI Portal the following features can now 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: https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/Default.htm

Mobile Client URL: https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/dispatcher/Default.htm

FLM Multi-UI Portal Dispatcher

As you can see from the links above there are two paths that can be used to access the Multi-UI Portal.  The first URL links directly to the FLM Portal and does not inspect the user-agent of the web browser making the connect.  The second 'dispatcher' does inspect the user-agent and allows certain aspects of the interface to be customized.

Maintain Device Characteristics

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

This activity allows an administrator to create a set of characteristics for certain device types (when using the new multiUI portal). The system uses the 'user-agent' from the device browser to identify which type of device is making the call to FLM.  The 'user-agent' for a particular device can be determined by navigating to the FLM Portal and then clicking the 'about FLM' button, and then the 'more info' button.

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 Multi-UI portal only.
  • MUI Portal Design: Determines whether the Multi-UI Portal will be launched with deisgn2003 or design2008. This determines the look and feel of the HTMLB elements used in the portal. It is possible that depending on the device used to access the portal, users will require a different "design variant", as design2008 isn't supported for internet explorer 8 for example.
    • If the user base is using broswers versions older than IE11 then design2003 should be set as default.
  • 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 accessing 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 MultUI 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.

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/Default.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.

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/Default.htm?user=USER1

Enterprise Portal Integration

The Multi UI Portal 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.

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/Default.htm

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 'A' 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 MUI 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 FLM Multi UI Portal Pages Directly

For the four view options below the FLM Logo, Logout Nutton 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 BSP Portal also recognizes the "No Logo Section" and "No Logout Button" options defined in the FLM Customer Code.

Viewing Inbox

To directly launch the FLM Multi UI Portal and Show the Users Inbox the following  URL can be used.

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/inbox.htm

Viewing Draft FLM Forms

To directly launch the FLM Multi UI Portal and Show the Users Draft FLM Forms the following  URL can be used.

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/draftforms.htm

Viewing Template Forms

To directly launch the FLM Multi UI Portal and Show the Template Forms the following  URL can be used.

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/templateforms.htm

Viewing History

To directly launch the FLM Multi UI Portal and Show the Users History the following URL can be used.

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/myhistory.htm

 

Working with FLM Forms Directly

When working with forms the following optional URL parameters can also be used.

  • DOC = <IMDocument> - can be used it pass additional values with a maximum of 40 characters.
  • PrevPage=<URL for after form Submit> - Default is users FLM Inbox.  Do not include protocol (ex: www.google.com).
    • When the form is submitted the user is directed to Exit.htm and the "Exit" button on this page will contain the URL defined in PrevPage.
      • The Exit.htm page is customizable and can be found in SE80 -> Repository Browser  BSP Applications /FLM/Portal -> Pages with Flow Logic
    • If PrevPage is used with one of the following options it is treated as a "portal launch" versus a "url launch" and the back button will be made available and after the form is submitted the user will be redirected to the indicated page by the option within the FLM Portal.
      • TOINBOX
      • TONEWFORM
      • TODRAFTFORMS
      • TOMYHISTORY

 

Starting a New FLM Form

To directly launch the FLM Multi UI Portal and Start a New FLM Form the following parameters can be added to the URL.

  • CCode=<Customer_Code>
  • FType=<Form_Type>
  • FMode=<Mode> - 1 (Create), 2 (Change), 3 (Display Read-Only)

So the URL would be like this:

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/form.htm?ccode=<CUSTOMER CODE>&ftype=<FORM TYPE>&fmode=1

Additionally if you want to launch a New FLM Form and pass in additional information you can use the IM Document parameter to pass this information using the below parameter

DOC=<CHAR40>

So your URL would be like this:

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/form.htm?ccode=<CUSTOMER CODE>&ftype=<FORM TYPE>&fver=<VERSION>&toption=<TEMPLATE OPTION>&fmode=1&DOC=USER1

This additional information can then be picked up in the FLM Form Pre-pop User Exit as normal.

Opening an Assigned FLM Form:

To directly launch the FLM Multi UI Portal and Start a New FLM Form the following parameters can be added to the URL.

  • CCode=<Customer_Code>
  • FType=<Form_Type>
  • FVer=<Version>
  • TOption=<Template Option> - Language (E) or Language + Device (E1) for use in Template User-exit
  • ID=<Form ID>
  • ID_Var=<Form Variant> - if 000 is used as the Variant the latest variant will be returned.
  • FMode=<Mode> - 1 (Create), 2 (Change), 3 (Display Read-Only)

So the URL would look like this:

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/form.htm?ccode=<CUSTOMER CODE>&ftype=<FORM TYPE>&fver=<VERSION>&toption=<TEMPLATE OPTION>&id=<FORM ID>&id_var=<VARIANT>&fmode=2

 

Opening a Read-Only version of a Form:

To directly launch the FLM Multi UI Portal and open an existing FLM Form the following parameters can be added to the URL.

  • CCode=<Customer_Code>
  • FType=<Form_Type>
  • FVer=<Version>
  • TOption=<Template Option>- Language (E) or Language + Device (E1) for use in Template User-exit
  • ID=<Form ID>
  • ID_Var=<Form Variant> - if 000 is used as the Variant the latest variant will be returned.
  • FMode=<Mode> - 1 (Create), 2 (Change), 3 (Display Read-Only)

So the URL would look like this:

https://<SERVER>:<ABAP Port>/sap/bc/bsp/flm/portal/form.htm?ccode=<CUSTOMER CODE>&ftype=<FORM TYPE>&fver=<VERSION>&toption=<TEMPLATE OPTION>&id=<FORM ID>&id_var=<VARIANT>&fmode=3