CASE: add info-tag to a standard Silverfin template

[sven]

It is now possible to add an info-tag to a standard Silverfin-template, like this:

Just go to the template on office level, and add this in the extra configuration:

You can use this code for example:

{% ic %}
{::infotext}
{% if period.reconciliations.omzetvergelijking != blank %}
{% linkto period.reconciliations.omzetvergelijking %}{% t "Click here to go Sales Comparison" %}{% endlinkto %}
{% else %}
{% t "Template Sales Comparison missing- please add to the working papers if needed" %}
{% endif %}
{:/infotext}
{% endic %}

More info here as well:

CASE: use infotext and warningtext tags

There’s new functionality you can use in templates now : {::infotext} test info {:/infotext} {::warningtext} test warning {:/warningtext} This will give a nice looking text like this : [57] In export however, it will not look like that (only the text and color will be exported), but this is only meant for input-mode (so be sure to use {% ic %} ... {% endic %} If you wish to create an info text that displays through the whole width of the page, like this: [12] you can easily do by this c…

and here for generating a link to another template:

CASE: link to a recon template

In a template you make, it could become handy to have a link to another template. This way, an user doesn’t have to click on the working period and search for the desired reconciliation template. To create in what we call a “linkto-tag”, you need for the template where you want to linkto, a handle : [handle] In custom templates, you can easily add this. For a Silverfin template, a handle should already be existing. A handle is basically sort of a ‘shortcut’ you can use for a linkto. To crea…

[olga.salamanca]

@CASE: use infotext and warningtext tags

{::infotext} test info {:/infotext}

Is there a way to show the info icon and only show the comment if they hover the mouse over the icon?

[Romy_Vermeeren]

Hi @olga.salamanca

Definitely, you can specify that an info- or warningtext should be as=“hover”.
You can find more information on the topic here.

{% ic %}{::infotext as="hover"}test info{:/infotext}{% endic %}

[olga.salamanca]

@Romy_Vermeeren

{% ic %}{::infotext as="hover"}test info{:/infotext}{% endic %}

Thanks, that works perfect but if we want amend the wording on this boxes that they are just informative as well to add " fixed £" and “rate %” I am not sure when we need to change it as I think it is a placeholder but I don’t see the placeholder in the code for fixed & rate.

[Romy_Vermeeren]

Hi @olga.salamanca

You’re indeed looking to add a placeholder to these inputs.
Placeholders are not mandatory, which could be the reason you don’t currently see them in the code.
You can just add one as you please.
It’s important not to change the name of the custom variable though, as that’s where users store data. (custom.namespace.key)

Example:

Mark up rate {% ic %}{::infotext as="hover"}The following rates are informative{:/infotext}{% endic %}

{% input custom.mark_up.fixed as:currency placeholder:"Fixed £" %}
{% input custom.mark_up.rate as:percentage placeholder:"Rate %" %}

[olga.salamanca]

That works thanks, but adds new boxes to the ones we already had. As we cannot find the placeholder for the original ones, we cannot amend them or remove them. Do you have any idea how we can identify them?

[Romy_Vermeeren]

Hi @olga.salamanca

there’s no need to add the new inputs from my example to your own code.
You can add the new placeholders to the existing inputs (or as you call them “boxes”), that will not break anything.
You see “fixed” and “rate” because no placeholders were used yet, in which case the system defaults to showing you the key of the custom variable. (custom.namespace.key)

If you need more assistance adding the placeholders to your existing code, can you please paste the code here so I can assist you further?