There needs to be an app-level setting to allow that app to show up in the design library objects collection. Otherwise when you add an interface to the library, suddenly you're seeing every app that object has ever been added to, including apps for individual tickets, hotfix packages, etc. I'd prefer there to be a way to just have a single global app called "design library" (or at most one per application in the system, meaning several dedicated ones at most, whereas mine is currently cluttered with maybe dozens).
@mike.s.605 thank you so much for the feedback. I will forward this to our product managers, but in the meantime, we do recommend that you create a dedicated application to manage your design library-specific interfaces. See our article with specific guidance here: docs.appian.com/suite/help/23.2/working_in_design_mode.html#using-the-design-library . Also please join us during our next live stream to watch use of the design library in action.
@@AppianCommunity - well, I did that right away, actually. The issue is that the "dedicated application" merely shows up in the list showing *all* of the other applications that any of the DL components happen to already be in, which in my case, regarding a system that was built 4 years ago and has been under active use and ongoing development for the past 3+ years, still consists of dozens of individual applications of various sorts. And of course, adding the individual DL objects to a new consolidated app does *not* automatically remove them from past ones (and i wouldn't necessarily want to in all cases).
There needs to be an app-level setting to allow that app to show up in the design library objects collection. Otherwise when you add an interface to the library, suddenly you're seeing every app that object has ever been added to, including apps for individual tickets, hotfix packages, etc. I'd prefer there to be a way to just have a single global app called "design library" (or at most one per application in the system, meaning several dedicated ones at most, whereas mine is currently cluttered with maybe dozens).
@mike.s.605 thank you so much for the feedback. I will forward this to our product managers, but in the meantime, we do recommend that you create a dedicated application to manage your design library-specific interfaces. See our article with specific guidance here: docs.appian.com/suite/help/23.2/working_in_design_mode.html#using-the-design-library . Also please join us during our next live stream to watch use of the design library in action.
@@AppianCommunity - well, I did that right away, actually. The issue is that the "dedicated application" merely shows up in the list showing *all* of the other applications that any of the DL components happen to already be in, which in my case, regarding a system that was built 4 years ago and has been under active use and ongoing development for the past 3+ years, still consists of dozens of individual applications of various sorts.
And of course, adding the individual DL objects to a new consolidated app does *not* automatically remove them from past ones (and i wouldn't necessarily want to in all cases).