CUBA Platform Roadmap 2018

Announcements
#22

Thanks. I look forward to hearing more about it.

#23

Great features on the list.
Is there any possibility to bring visual designer for Polymer 3, something similar to currently available for generic UI designer today in CUBA?

1 Like
#24

Is there any possibility to bring visual designer for Polymer 3

Having one is one of our initial goals since Polymer has an official designer and more lightweight wizzywid. However both are not production ready and not up to date since Polymer team is busy on Polymer 3 release preparation. We keep an eye on the progress of both projects and will consider integration as soon they are more polished.

1 Like
#25

I see what you mean: Designer hasn’t been touched in quite some time.

#26

Hi Konstantin,

Thank you for clarifying my concerns with Vaadin/IntelliJ.

Are you able to provide any details regarding my (and Ryan’s) concerns with the new BPM?

Thanks!

#27

Hi Keith,

At the moment, I cannot add anything to what I wrote in the comment above. I hope it clarifies our general approach.

#28

Whoops. Sorry, I missed that comment. Thanks!

#29

Hi @knstvk
Camunda BPM looks interesting. It also has extensive email integration.
Anyways, will this be possible in the enhanced version as follows which is used in any enterprise environment:

-put on hold by approver with specified number of days and if not actioned within that duration it reminds by email notification automatically
-automatically escalated to the manager of approver if not actioned within certain numbers of days which will be configurable
-option to build reusable workflow across different entities
-task list by users grouped by task type. This task list would be a gateway to display and action (approve, reject, forward).
-Count of such pending actions can be displayed on a badge for respective users notice
-option to display workflow node from task list and it’s approval status
-option to trigger reminders to immediate approved on adhoc basis apart from notifications

#30

Hi Mortoza,
Thank you for your feedback. We’ll consider it in the future.

1 Like
#31

Is there any idea to add Apache Jackrabbit or Alfresco Document Management System to the Cuba 7? Because it is very much needed for the enterprise applications…

#32

It’s a good task for an add-on. Hope it will be implemented sometime.

#33

Can we expect any add-on between the Cuba Platform and THESIS (ECM) of Haulmont, anytime soon? And why there is no connection between the THESIS DMS and Cuba Platform, it seems the software is very much isolated from the Cuba Platform. But the software is actually built on Cuba platform…

#34

Hi Lakshmi,
You are right, Thesis is actually built on CUBA Platform, so I am not sure what kind of integration do you mean? Could you provide a sample case?

#35

Going back to the new datasource API:

Is it going to be compatible with the old one, or will we need change the code to use it? If it will mean a lot of code changes, will the old API still be supported in new release?

#36

The new API will be very different, but all existing code will continue to work as is on the old API. So there will be two parallel APIs, and for the new code you will be able to choose how to write your screen: using the old or the new API.

1 Like
#37

Hi there. I have a question concerning the planned multi-tenancy module. I don’t know how far you are down the line with it, but I’d rather hope that it would allow for multiple databases by attaching a connection (or rather, pool of connections) to each tenant, then use a lookup to decide which pool should be used. I think this would be a lot better than having every tenant’s data stored in the same database.

1 Like
#38

The same question regarding multi-tenancy with multiple database connections, avoiding the current solution with additional datastores which has some limitations.

#39

Hi @ray1,

The addon we are developing implements an approach of single DB for multiple tenants, using discriminator tenantId column to split data between tenants. This column will be automatically hidden for tenant users, so that they will see a standard CUBA screens with only their data. Data filtering is also happening automatically, modifying JPQL queries on the fly.

To sum up, the main idea of the component is to dramatically simplify development of multi-tenant applications over single database. Developers just should implement the HasTenant interface for their entities, which should be divided by different tenants and the rest will be done by the component itself.

Regards,
Aleksey

1 Like
#40

Hi @stukalov, this was the same approach that I gave my application a single storage for multiple clients, the problem that I have found is when using FTS since I still can’t solve that does not show me the information of other customers. This would be solved with this new addons?

Regards,

Nelson F.

#41

Hi @nelsonflorez,

Could you please attach a sample project, as when I try this case it works perfectly for me. And it should work for your case as well as we always reload found entities via DataManager which applies access groups permissions on top.

Regards,
Aleksey