10.3 Announced features missing?

From BoardVille 2018 it was clear that 10.3 was going to be an important milestone release leading to 10.5 and beyond. Now it has been released there are some great new features delivered, but there are also features that were promised that are not mentioned in the release notes. Notably:

Parallelism of data readers and data flows (10.2)
Subscribe - self-service function for scheduling emails of capsule screens/presentations in PDF or XLS format (10.3)
Sent-to - delivers scheduled email of a Board Presentation to list of other users (10.3)

Can anyone confirm whether a) they are there but not documented, or b) they have been postponed. If it is the latter, are we to expect another 'point' release before 10.5?

A revised roadmap and timeline would be appreciated by many I think.

Robert

Find more posts tagged with

Accepted answers

All comments

Björn Reuber

Hi Robert,

I can only give you a feedback about the DR, not about the two other points.

There was an decission taken, that "standard" 10.3.0 is released without concurrency of the DR, cause this feature willl lead to an higher testing for "racing conditions" on a migration project.

Cause if you have User A running a DR on Cube Sales (with Replace) and User B who is running a DF with Cube Sales as a Source in non High concurrency versions the DF will only start when the DR has finished (so both won't run in parallel).

In new version they will run in parallel. Due to the replace the Sales cubes is empty for a short time period (you can see this in every board version, if you run a DR with replace the cube get "cleared" and then filled step by step). If the DF is running in at the exactly same time it might be, that the DF is using an empty/not 100% filled cube (from a technical point of view this is correct cause of the parallel execution).

I hope you understand why this changed behavior will lead to an higher testing effort.

Cause of this our HQ decided to publish 10.3 without the new HC Engine, BUT there is also an Version available having the HC feature (if you need it). For this please get in touch with your local BOARD Office.

Regards

Björn

Paul Wyatt

I really would like to see a revised roadmap. With external clients, we have to consider training requirements not only for the business but for them too, along with a standard upgrade plan considerations.

Peter van Bennekom

Is there a (technical) white paper about how parallelism is implemented in board? When I read your example I get this underbelly feeling that something is not right. If there is no protection (DBMS term ROW/PAGE/TABLE LOCK) of data this could go horribly wrong if two DF work on the same cube with highly unpredictable results. I am sure the architects thought about this. If this is not available can this be shared with the community?

Björn Reuber

Hi,

Dataflowsand DataEntry have been already in Parallel and there is allways one component which is mostly overseen, when talking about parallelism. It's the time (I'll gebt back to this later). I had this discussion several times (with several customers/Partners).

Furthermore in a planning process different users should be (from security point of view) seperated. So User A is allowed to change Figures for Customers C1-C4 and User B is allowed to change Figures for C5-C9,

If two users are allowed to change the same part of a cube (or have a common intersection) the planning process would be unpredictable (not cause of the software, it's more because of the users), cause with figure would be the correct one?

And here we'll have the time again, BOARD allways works with Last Win. So if User A is changing a Value for Customer C99 to 100 and 10 Minutes later User B is changing it to 50, we'll got the 50 as a cube value. Now you can reduce the time, but the 2 users won't be able to enter data in the EXACT same moment (there will allways be a millisecond difference).

In addition, this is the job of the BOARD Developer, to design the processes in a manner, that they can be run by multiple users at the same time (cause it's not a problem in the software, if the application design is not the best).

Regards

Björn

Federico Cazzalini

Hi,

"subscribe" and "send to" functionalities have been released with Board 10.5 (now we're live with 10.5.1); the High Concurrency engine has been released with Board 11 (now we're live with Board 11.1).

federico