Search the Community
Showing results for tags 'WidgetTokens'.
Looking for a simpler way to create standardized dashboards during onboarding process. Use case: I am an MSP who builds three (three is arbitrary but this story gets worse if this number grows) default dashboards for any customer who signs up for my service. As an initial step the provider creates these dashboards using widget tokens and place them in a non-customer facing group so that the provider onboarding operators can clone them. Today this means that the operator must: 1. Go into the dashboard section of the UI 2. Create a new dashboard group for the new customer, 3. Clone dashboard 1, update the group, and then update widget tokens for dashboard 1 4. Clone dashboard 2, update the group, and then update widget tokens for dashboard 2 5. Clone dashboard 3, update the group, and then update widget tokens for dashboard 3 6. Wash, rinse, repeat Request: UI: Move widget token metadata definition to the group level as an option and then allow dashboard cloning at the group level. This changes the process above to look like below regardless of how many dashboards exist. 1. Go into the dashboard section of the UI 2. Create a new group 3. Clone the dashboard group, change the widget token, change the group, and then go about their business. API: This process would then simplify the onboarding code dramatically as there would be no need to iterate through the existing group to gather data before the code could continue with the cloning process.