New Capabilities on Dashboards

In this new version, the development paths of the dashboard ecosystem have been improved, ranging from their simple and immediate use, to the distinction of different profiles within the creation lifecycle.

Of great support to this process is the use of new capabilities incorporated into the platform.

Adding header libs (or header fragment) to gadget templates

It will be possible to include the necessary dependency libraries, allowing testing and having a complete development cycle of complex gadgets. These libraries must, however, be incorporated into the dashboard.

Open

Editing header libs in the dashboard

It will no longer be necessary to edit this section from the outside the dashboard. You can now edit easily from within the dashboard.

Open

Types of templates in gadget templates

You can generate gadget templates easily in VueJS or even ReactJS (the old templates are linked to the "Angular JS" type). From the gadget template creation menu, select the base template type:

With this base template, the header libs and the initial code snippets of the different technologies will be assembled. After that, you need to start coding from this point in order to generate your final gadget

Using parameters in the JavaScript section of the gadget template

Parameters have been included in the JavaScript section of the gadget template, making it possible to retrieve parameters in a much simpler and more powerful way. The syntax allows parametry, by default, in this way:

var key = /*param*/ "value"

For example:

var key = /*label-osp name="Key Select" type="ds_parameter"*/ "value"

Which will replace, when overwritten, the parameter by something like:

var key = "keyval" || "value"

Retrieving the value "keyval" in the case of having parametry as "value" without parametry.

This parametry is retrievable as many gadget states from the "vm" context structure by accessing "params".

“vm.params“

Linking gadget templates with origin

The use of templates associated with the source is allowed, both in copy mode and in linked mode, on the dashboard. Thus, if a dashboard copies the gadget (as it has been done up to now), it can be edited inside, but if the original gadget changes, there will be no way to update the changes. On the other hand, if a linked gadget template is used, only its parameters can be edited in the dashboard; but if the template is edited, all the references will be updated.