Release Automation

 View Only
  • 1.  "Unshare" a component?

    Posted Apr 28, 2016 06:21 AM



    we have an application where we assigned several shared components, we now have another application that uses most of the stuff from the shared component but also needs some specific stuff build to it as well, that we don't want to have in the shared component


    so I was just wondering, if we're able to "unshare" a component within an application without losing the component itself. all I see is an "unassign" .


    or in other words, this would be more like a local duplicate of the shared component


    I know that I could add a local component and assign the shared and local to the same server type and build the flow in the process itself, but this might lead to a lot of rebuilding.




  • 2.  Re: "Unshare" a component?
    Best Answer

    Broadcom Employee
    Posted Apr 28, 2016 08:54 AM



         Your correct the only option is to "unassign" a shared component there is no option to make a local copy of a shared component. Perhaps this can be added to the ideation system so it can be considered for a future release.




  • 3.  Re: "Unshare" a component?

    Posted Apr 29, 2016 12:57 AM

    too bad, I was afraid that is the case, I will post an idea for that

  • 4.  Re: "Unshare" a component?

    Broadcom Employee
    Posted Apr 29, 2016 02:50 AM

    Thanks Michael,


         I have voted for your idea.