/IQX/FAB_CONFIG - FAB Configuration

Configure Access to the Forms

Step-by-step guide

Enter transaction /IQX/FAB_CONFIG

1. Roles
Roles are defined based on the process flows for each individual app, groups of apps or for the entire organization. A role is assigned to a form. A class /IQX/CL_FORMS_WORKLIST_CLASS or its subclass can be assigned to a defined role.

2. Forms for Roles

Assign forms or apps to roles.

Sequence – is used for arranging the app as a tile in the launchpad.
Footer – is used for grouping apps. This is displayed at the bottom of the app's tile.
Sub Header - displayed under the app's description in the tile.

3. Roles for Users
Assign users to roles. Only users assigned to the role that is assigned to an app will have access to that app. If Admin is ticked the user gets access to an extra "Administrator" tab in MyForms. It becomes available even if the user is not the actual agent of the form and allows a supervisory view of the particular form compared to a standard user. If a user is an administrator but it is required that they be limited a certain region or some other attribute of the form then further limitations can be implemented to qualify the administrator's access. It can be achieved by creating an implementation of sub-class of /IQX/CL_FORMS_WORKLIST_CLASS and then entering this in the "Roles" configuration area where it says "Implementing Class for Worklist". Method FILL_WORKLIST_FOR_ROLE can then be used to further fine-grain whether a particular App is visible in the Administrator tab of MyForms.

4. Stand-Alone Apps Launch URLs

When the app is specified as Stand-Alone, their launch URLs can be specified here.

If a FAB App has been converted to a stand-alone application, and it is desired to launch it from the FAB Launchpad or FAB My Forms, then it should be launched via it's own URL which will depend on the name of the stand-alone application.

For example, if a stand-alone application is created with 'UI5 App Name' = 'ZMY_APP', then the URL will be http(s)://server:port/sap/bc/ui5_ui5/sap/ZMY_APP.

Therefore if it is to be launched as a stand-alone application from the FAB Launchpad, then it should be configured here with an entry.

5. Approvers (defined)

Definition for approvers determination.

6. Auto-Generated Forms

An app can be started from another app. The app that can be automatically generated is entered here and set to active.

7. General Configuration

Maintain the Servers and URL for the landing page of the form tiles here during initial setup or subsequent change.

8. App Configuration
This shows the version of FAB installed and the background image.

9. Additional Libraries
This is a repository for additional Javascript libraries that can be accessed by apps.

10. UI Component Reference
This is used to reference UI5 classes instead of default values in case older (<7.40) SAP Systems are used or if you are using SCP with OData provisioning services.

Enter the following details:

Version: 002
Repository API Class Name: /IQX/CL_UI5_REP_DT
Repository API Interface Name: /IQX/IF_UI5_REP_DT
Utility API Class Name: /IQX/CL_UI5_REP_UTILITY

11. Global CSS
This specifies the styling that is applied and can be accessed globally within FAB.

12. Editors

The FAB Editor configuration can be accessed in transaction /IQX/FAB_CONFIG → Editors. It is used to configure the URL of different editors and stand-alone UI5 applications used by the FAB workbench and the FAB Data Report.

13. Documentation URL
This specifies the configuration of the FAB documentation accessible from the workbench. The URL of the latest online documentation is http://fioriappbuilder.com/documentation.

14. App Templates
This allows you to create a template application that can be used as a starting point for new applications.