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

As an App Adm, I want to delete an existing fieldset and keep fields on the instances

    Details

      Description

      Design Deliverable:

      Mockups

      Context

      It is very common for users to find themselves in need of using the same group of fields in different objects and forms views (e.g. address). Without fieldsets, the users would have to create those same fields over and over for each object, even when all the parameters and configurations are exactly the same for all objects, there is no way to reuse. To solve that, we need to implement the fieldsets, which will offer them a way to save, update and reuse those groups of fields that are commonly used by many of their objects.

      This Story aims to allow users to delete an existing Fieldset without propagating the deletion to the Objects/Views that are using it.

      That being said, according to the scope of this Story, users should be able to:

      • Check the list of saved fieldsets available to be deleted
      • Delete a existing fieldsets;
        • The propagation of the field's deletion is the scope of the Story LPS-107637 .

      Acceptance Criteria

      • 1- Given that a user is creating a Form View for an Object, when he clicks on the "Fieldset" tab of the right sidebar, then the system should list for the user the available fieldsets to be update and show buttons to remove each fieldset.
        • Fieldsets should not be object scoped, users should be able to share fieldsets across objects of the entire DXP instance.
      • 2- Given that a user is creating a Form View for an Object and clicked on the "Fieldset" tab of the right sidebar, when a user clicks in the button to delete an existing fieldset, then the user should be prompted for a confirmation to proceed with the deletion of the fieldset;
        • If the user doesn't confirm, the fieldset should not be deleted.
      • 3- Given that a user is creating a Form View for an Object and clicked on the "Fieldset" tab of the right sidebar, when a user clicks in the button to delete an existing fieldset and confirms that he wants to proceed with the deletion, then the fieldset should be deleted and the fields of the fieldset should be kept in any Object/Forms that was using it, but they should not be a link to a fieldset anymore (once the fieldset no longer exists).

      Definition of Done (DoD):

      • All Acceptance Criteria were passed;
      • Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
      • Verify if the test labels were added;
      • 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

        Attachments

          Activity

            People

            Assignee:
            pt-app-builder Product Team App Builder
            Reporter:
            felipe.pires Felipe Pires (Inactive)
            Recent user:
            Leide Mangueira
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package