Starting with version 7.0.0 of Forms for Confluence, it is now possible to create form configurations if a user is a space administrator. This allows not only Confluence administrators to manage forms, but also space administrators. Since every user can create his or her own personal space, everyone can create form configurations.

The concept is similar to what is explained in Setup Form ID Configuration. This section is going to highlight the main differences between a Form Configuration created by a space administrator, and a Form Configuration created by a Confluence administrator.

Email Relays and ScriptRunner form configuration types are purely a Confluence administrator functionality, hence form configurations created by space administrators are all of type: Internal Database.

Instructions

  1. When the space administrator is the relevant space, click the Space tool menu in the bottom left corner of the page, and then click the section Forms for Confluence.
    Space tools menu.
  2. The Forms for Confluence space section will appear.
  3. Click Add a New Form Configuration.
  4. Complete the Create New Form ID Configuration fields.
    1. Provide a unique identifier in the Form ID field.
    2. Set Destination type to Email Relay.
    3. Enter the email address(es) to receive results from the configuration.
    4. Select the Jira Application Link that will be associated with the Form ID from the available Jira Application Links in the drop-down list. See the Atlassian documentation for more on setting up an application link between Confluence and Jira.
    5. The ScriptRunner Endpoint, identifies the specific endpoint (contact point) configured using ScriptRunner REST endpoints in Jira. This is simply the exact point to where the form will be sent. The ScriptRunner REST endpoint will be responsible for processing the submitted form. One form can be submitted to multiple Jira instances, and each Jira instance can have several endpoints. See the ScriptRunner documentation for setting up a REST endpoint. 
      1. Optional: Select the Single Submission checkbox, if you want to send an email only once to the provided email addresses.
      2. Optional: Check the Submission Override checkbox, if you want to allow the user to override his submission.
      3. Optional: Provide a message to users after the form has been submitted in the Additional Information HTML field. This might be useful if the form submitted was used to created an issue in Jira. The message received could contain a link to the newly created issue or any other information deemed useful. 

        Provide a message

        The Additional Info HTML field in the ScriptRunner Form Configuration is customizable and at present Info HTML supports the following placeholders:

        $endpoint: Input value of the ScriptRunner Endpoint text box.

        $formID: Input value of the Form ID text box.

        $response: Received response of a successful call.

  5. Click Save, to create the Form ID Configuration.

    The new Form ID will appear in the Forms Configuration list.

    The list contains only the Form ID configurations relevant to the space in use. 

    If a user does not have the "Space Admin" permission and tries to access the Space Tools Forms for Confluence configuration, the user will get a "Permission Denied" page.

    Forms for Confluence allows Confluence administrators to manage form configurations they've created, and form configurations that were created by space administrators.

    In the Form Configuration screen of a Confluence administrator, a new column was added that specifies if a Form Configuration is Global or to what space it belongs. This makes it easy to identify if a specific Form was created by the Confluence administrator or a space administrator. Here is how it looks:

    If a space administrator is administering more than one space, he/she would need to go to a specific space to manage the configuration of that space.

    A Confluence administrator can edit Form configurations that were created by space administrators, so they still hold control over all configurations. The space administrator configurations are restricted to type Internal Database, and this cannot be changed by the Confluence administrator.