Best Of

Hi,
it is not possible to disable the entire menu. What you can do is disable some of the features contained in that menu:

• the select window can be disabled from the user security profile: enable the "Deny selection editor" option
• Show screen list can be disabled using the "Hide screen list" option editing the WinClient capsule property (as you already mentioned)
• the presentation part can be removed disabling the entire presentation feature. See below instructions

Disabling the presentation feature can be done in the HTML5 app config file you can find in the WebApi Server folder (usually installed under C:\Program Files (x86)\Board\Board WebApi Server).

Opening the AppData>Config folders you will find the "appSettings.config" file.

Editing that file you will find the parameter

<span class="token tag"><span class="token tag"><span class="punctuation token"><</span>add</span> <span class="attr-name token">key</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>presentationEnabled<span class="punctuation token">"</span></span> <span class="attr-name token">value</span><span class="attr-value token"><span class="punctuation token">=</span><span class="punctuation token">"</span>true<span class="punctuation token">"</span></span> <span class="punctuation token">/></span></span><span class="line-numbers-rows"><span></span></span>

This parameter should be set to false. (the BoardWebApiEngine service needs to be restarted after this change).

Please let me know if this helped,
Best regards,

Michele

Hi there,

BOARD comes with an automatic feature that compiles the SQL statement for you when configuring datareaders using ODBC drivers.

If you want to load daily data into an InfoCube structured by month, you can map the day field to the BOARD Month entity. BOARD will automatically aggregate the information at monthly level thanks to the native BOARD time hierarchy.

Hope this helps

Regards,

Michele

Hi interested typ,

You need to install the Mobile Server in case you are using our native BOARD Mobile app for IOS, that you can find at this address: BOARD Mobile on the App Store. Note that you will need a Mobile license type in order to access capsules from the mobile app.

The mobile capsule feature that you mention is specifically built to create capsules that can be consumed from our BOARD Mobile App. Opening them directly from the BOARD HTML5 WebClient on your mobile / tablet won't show any difference.

Using the BOARD mobile app on a IOS tablet gives a quite sleek experience, and in case of a corporate installation you can manage installation on company devices through MobileIron - but there are limitations to what you can do in terms of objects and configurations.

The mobile app is not deprecated but given the fact that you can use the HTML5 client on any mobile or tablet device, it's not as used as before BOARD 10 came out. Your approach at point 3 is what most developers prefer nowadays.

In the future versions of BOARD, an option for the automatic resizing of capsules (responsive rendering) will be made available, this will semplify even more using BOARD on mobile devices.

Hope this helps,

Michele

Hi Sebastian Gurt and Emanuela Dolce,

Just want to drop in a couple of lines about this topic as it's a very common scenario, so I thought i might add some context - as a general design principle, doing a DE on the total of a column algorithm will not be ideal as it generates a circular reference in the dataview calculation when "simulating" the change before saving the dataentry.

I tried to explain it in the graphical flow above.

When you execute the change in the HTML5 client, on the total of the column algorithm, the dataentry will return a "weird" value in the total itself. If you then save the dataentry, the BOARD engine will perform the correct split and splat on the cube where the values are reversed, and the total will match your data-entry value. (see the short video i've attached).

It might be confusing for the user to see their data-entry value change and then reappear, that's why i would go for the additional "total" dataview as mentioned before, it's a neat solution and doesn't require a lot of effort!

Hope this helps

Michele