Hi isabelle, Thanks for your input. Yeah, in this case we are focusing to have end-user related operations which are not really a devops/admin related operations, in dashboard it self.
And in the context of doing analysis on the collected data is basically enduser operation in BAM, and he/she might be interested on some metric of collected data, and plug into some graph visualize the KPI. In order to do this, if we have these operations in the dashboard application itself, then the UX will be smooth. By this way, the enduser will remain to work with dashboard application, and not necessarily need to switch to admin or management console to do their some of their task. Similarly the devops will continue to work on management console which will facilitate to configure the server, but not necessarily to see dashboards, etc. Thanks, Sinthuja. On Mon, Mar 9, 2015 at 6:19 PM, Isabelle Mauny <[email protected]> wrote: > +1 as long as you have a clear user's role separation of the UIs you're > creating - Don't mix managing/configuring the product with consulting > dashboards in the same applications (i.e. URL). > > I feel that over the platform we have a key need for high-level > configuration tasks that do not belong in the traditional admin console. > Either that , or enhancing/segmenting the admin console to again clearly > separate the tasks that are conducted by different roles. > > Isabelle. > > ------------------------------------------------------------------------------------- > *Isabelle Mauny* > VP, Product Management - WSO2, Inc. - http://wso2.com/ > > > On Mon, Mar 9, 2015 at 8:07 AM, Sinthuja Ragendran <[email protected]> > wrote: > >> Hi, >> >> BAM dashboards are used so far to visualize the graphs, etc for >> presenting the data, but we are thinking of moving some of the operations >> from admin console to dashboard for a seamless user interaction. Basically >> in BAM 3.0, the users would like to execute some queries on the console, >> and then he/she can export as script and schedule it. And then within same >> application he/she can switch the tabs, and visualize the graphs. Since >> these are end user related operations and more frequently performed in the >> run time, IMHO it's more better to have it in the dashboard so that the >> user can stick into one context, rather switching back and forth to >> management console and dashboard. >> >> But we do have other UIs such as streams, input/output adapters etc will >> remain in the management console as those are actual devops related >> operations. >> >> Please share your thoughts in above approach. >> >> Thanks, >> Sinthuja. >> >> -- >> *Sinthuja Rajendran* >> Senior Software Engineer <http://wso2.com/> >> WSO2, Inc.:http://wso2.com >> >> Blog: http://sinthu-rajan.blogspot.com/ >> Mobile: +94774273955 >> >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Sinthuja Rajendran* Senior Software Engineer <http://wso2.com/> WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
