Sometimes, the cloud version provides slow responses. The documentation must be more technical. Sometimes, we need to work with massive external data. We might have 10 to 20 million lines of data that must be imported into our system. Mendix is the only product that provides such features in the market. It enables us to virtualize and work with our data. Studio Creatio should provide such features to virtualize external data.

Within Spanish group service agents, we often encounter issues with translations. When implementing solutions, we noticed that certain parts, like K2 or case text, are sometimes inaccurately translated by our local partner responsible for Spanish translations. While some translations are excellent, others can be confusing. It appears that at times, our partners might be using Google Translate, resulting in translations lacking context and not being entirely understandable.

Studio Creatio can be used as a SaaS model, however, our customers are asking for the on-premise version. Creatio needs to stabilize their marketplace. When customers share their experience with the platform, the solutions should be easily added for global usage. 

Another improvement would be with integration. It is difficult to integrate particular technologies inside our customers' IT environment. 

Studio Creatio is a new product in the market, making its lack of maturity an area of concern. From an improvement perspective, the tool requires focusing on achieving a state of maturity.

In future releases of the product, it should be made more intuitive.

The solution does not allow extensive customization of the UI. I would like to have much more control over the UI when I build a process. Currently on the UI where the fields are placed and the layout is set in place and you cannot change it. Your experience is going to be the same throughout whatever use case that you are building from customer to customer. You can not have much control over how it looks for each customer. This is an area where they can improve on.

They can improve the business rules for defining the type and quantity of the business load. They already seem to be working on this improvement. 

Integration with the social networks will be very appreciated by the companies. It will be very useful for communication between the company and customers, that is, B to C relationships. Most of the customers or users have smartphones, and they use a lot of social networks. Companies need to stay connected with the customers. They have enabled integration with WhatsApp and Telegram in recent releases, which has been very useful.

I can have several types of contacts, customers, employees, partners, and so on, and I would like to have a different view for each type of contact in the list view. Currently, there is no way to configure this. This is something I would like Creatio to improve.

It does not have the ability to run one single large process. When you run very large processes, it runs into some problems. We found a way around it by breaking it up into smaller processes. 

They have limits on the number of characters allowed to run processes. You have to come with a workaround, by segregating it.

If they could make the screenshots of the steps a bit easier and more intuitive on the back-end for the administrators, similar to the way it is created for the users, and like the rest of the tool.

The mobile version of the solution could be improved. It's harder to customize.

My biggest concern is the lack of a multi data source on a page.

The way bpm's infrastructure works, you can only have one data source on a page. It connects to a object and you're locked in at that point. You can use virtual fields, but the problem is you can't edit - again, our company has a complex structure. If you need to connect fields from different objects, you would create it in that object and sync it. 

For instance, in our sales cycle we have an object called Project - this is our outer shell, our container - then Scopes and then Opportunities. These are three different objects containing different levels of information. Now if we wanted certain functionality to work for a field from a higher level in a lower level object, we then would have to create a home for it in the Scope and the Opportunity objects.

It would be that much more powerful if we could have a multi data source linked to a single page. That would really clean up a lot of things.

I rate the solution, overall, at nine out of ten.

It would be great if the product included a process design tool like Visio inside Process Designer. That would avoid us using an extra tool to do that.

HRM is an area where Studio Creatio lacks and needs to improve. The solution needs to have more customization options.