Add Custom Button below Create Fragment Option | Community
Skip to main content
A
ashish_mishra1
Level 3
June 16, 2022
Solved

Add Custom Button below Create Fragment Option

  • June 16, 2022
  • 2 replies
  • 1391 views

I am looking for some resources, on how I can add a new button below the Content Fragment Option on /assets.html page. Once the user clicks on that button a popup should open asking for an id input, with that input I will call a servlet which will create the fragment in the backend and redirect the user to the edit screen for that content fragment.

The reason for this setup is, that we have multiple fragments, and based on the input id we want to decide which fragment model should be used, so this task we want to automate.

 

Appreciate any help regarding this.

@arunpatidar 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

Hi,

You can write an event listener to move CF as soon as it is created to the new folder.

Author may confused with this but you can add instruction on create screen.

 

And make sure listener acts only act on outside certain folder.

2 replies

Bhuwan_B
Community Advisor
Bhuwan_BCommunity Advisor
Community Advisor
June 17, 2022

@ashish_mishra1 Please check for the below location for adding the button. you can overlay and then add logic to your button.

"/libs/dam/gui/content/asets/jcr:content/actions/secondary/create/items"

    ShaileshBassi
    Community Advisor
    ShaileshBassiCommunity Advisor
    Community Advisor
    June 20, 2022

    @ashish_mishra1 As per the reply from @bhuwan_b you can overlay "/libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items" and then add the logic.

    But just check the granite:class which you can utilize to accommodate your business use case, otherwise there will be a lot of effort required to meet the custom business needs.

     

    Just demo the feasible option and get confirmation about the best that can be achieve using the OOTB granite:class.

     

    If there is any requirement for the permissions to be implemented then check with that as well, as there "granite:class" have specific "granite:renderconditions" being handled. Later on implementation of both becomes a bottleneck i.e. if you want to hide OOTB and show the custom one.

     

    Thanks

      A
      ashish_mishra1Author
      Level 3
      June 20, 2022

      @shaileshbassi @bhuwan_b 

      Thanks, for the reply.

      I was thinking of another solution too, as this one seems a little complex.

      As per my requirement, need to create fragments in a specific folder.

      For example - The author will go to  "/content/dam folder" then click on create a fragment, and then select the dynamic product modal from the list of fragment modals. 

      Now post this in the title field, he will add the title as "colorful-slate-246", (alphanumeric product category code) so the task is to move this fragment automatically in the /content/dam/colorful/slate/246 folder and then create this fragment there, without asking the author to manually move there. 

      kind of a weird requirement, but we are trying to segregate our product fragments based on category ids.

      let me know if you guys can think of any solution here. How can we intercept the create fragment logic and add ours.

      cc- @arunpatidar 

       

        arunpatidar
        Community Advisor
        arunpatidarCommunity AdvisorAccepted solution
        Community Advisor
        June 21, 2022

        Hi,

        You can write an event listener to move CF as soon as it is created to the new folder.

        Author may confused with this but you can add instruction on create screen.

         

        And make sure listener acts only act on outside certain folder.

        Arun Patidar
          Terms & ConditionsAccessibility statement

          Loading footer...