We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Install Community plug-in (Admin Setting)
The list of customizations goes on and while the Community Uploads area is a great place to store these. It'd be even cooler if there was a more dedicated function within customer's deployments of the Cireson portal to either:
- Pull this content and deploy (i.e. Cireson hosts these in some central location)
- Allow some mechanism of "loading" plugins into the portal (i.e. nothing changes about the way we fetch plugins, just their mechanism for loading)
It goes without saying that the first point of mine is rendered a bit useless in air gapped environments and/or will make your security team flip tables if there isn't some kind of Cireson vetting process happening first (think SCOMs 2012 R2 Administration -> Partner Solutions)
The second point however I think really helps streamline the process. Furthermore, this could be built into an Admin GUI pane that allows the addition/removal/enabling of select plugins. In doing so, accidental changes to the custom.js are at the very least curbed. This could also be useful in load balanced environments where the changes could get distributed to all portal servers. Finally, it may in turn create the need to standardize what plugins look like (i.e. zip files contain some common folder structure)
Here's a quick sketch of what I'm getting at from a GUI perspective: