Versions Compared

Key

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

Configure Access to the Forms

Step-by-step guide

Enter transaction /IQX/FAB_CONFIG

...

  1. Roles: Roles are freely defined and assigned to individual forms. A class /IQX/CL_FORMS_WORKLIST_CLASS or its subclass can be assigned to a defined role as shown above.

  2. Forms for Roles: Assign the form to a Role/s


  3. Roles for Users: Assign users to the Roles. Only users assigned to the role, assigned to a form will have access to the form.

    If Admin? is ticked the user gets access to an extra tab in MyForms - which says Administrator. 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 separate administrators.
     
    It is 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 form is visible in the Administrator tab of MyForms. 
     

  4. Approvers (defined): Define approvers here when
  5. Auto-Generated Forms: A form can be started from another form.
     The form that can be automatically generated is entered here and set to active
  6. General Configuration: Maintain the Servers and URL for the landing page of the form tiles here during initial setup or subsequent change.


Info

Filter by label (Content by label)
showLabelsfalse
max5
spacesIFAB
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("roles","configurations","transactions") and type = "page" and space = "IFAB"
labelstransactions configurations roles

...