Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-132622

As a form creator, I want to easily map my Search Location child fields API connectors and Name

    Details

    • Type: Story
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Forms
    • Labels:

      Description

      Context:

      This story was created as an iteration of As a form creator, I want my users to fill their addresses directly from Google Maps, when refining with the team, we decided to break the previous story in 3 pieces. The core value, the settings/mapping value and the interface customization value.

      The current story aims to deliver the value of mapping the API connectors their Search Location field.

      Design Deliverables:

      Mockups

      Acceptance Criteria

      1 - Given a power user in DXP,
      when in site and global menu,
      then I must be able to see the default map of my Search Location field

      2 - Given a power user in DXP,
      when in site and global menu,
      then I must be able to edit the mapped API of my Search Location field

      • Be able to edit the Child field name and API key

      3 - Given a power user in DXP,
      when in site and global menu,
      then I must be able to add and delete new calls from the API

      • I must add the Key and Field Title

      4 - Given a power user in DXP,
      when when configuring in my site settings,
      then those settings must override the global settings

      5 - Given a power user in DXP,
      when when configuring the Search Location in site and global settings,
      then I must be able to import and export the settings (from DXP to DXP)

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Code with peer review completed;
      • Validated by QA, Product Designer and/or PM;
      • No critical bug related to Story scope (ex.: similar of FP4, FP5);
      • Make sure that all system documentation were updated (if necessary)
      • Make sure that it has the extensions points needed to allow GS and customers to customize the feature (If applicable)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              luiz.jardim Luiz Jardim
              Reporter:
              luiz.jardim Luiz Jardim
              Recent user:
              Mariana Huggins
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:

                  Packages

                  Version Package