What is our primary use case?
We use the mobile application, the Lightning application. We use it with consulting and integrating the different products like vCloud or integration with Google. There are some that we do production also. Everything is on mobile now. So we use mobile apps and then we develop those applications. It's a Cloud browser and device support that we are doing the programming. So basically now we are developing that in the Lightning Application, where we can. That is based on the event architecture and by the company's controller, we write those according to that. We develop the programming that will go to the software, we need to have the APEX programming materials for the IBM system, or with Lightning RAWC, who with integration we need to go with other configuration tools. So there are a lot of things that need to be captured in developing the project.
What is most valuable?
They also have features they are integrating to the other services or managing the technical management or you can go with the integration point of view and you can able to, in the build tool, do the configuring of those things in terms of other approvals or like customization. And you can include the time bond overflows for the emails. So all these parts come from the Salesforce only. So Appian does not have it, it comes with that only and now we are able to do it.
What needs improvement?
If you compare it with Appian, there are business rules that you are dealing with. With less code, we are making a higher standard. So maybe, in the future, Salesforce can make it a more integral part of the application. And they are also strategic partners with multiple companies, so maybe that is the reason they are sustainable and they the four versions every year. These things likely depend upon robotics programming and they use the latest technologies for a more stable portal. So we need to be more cautious about the coding and so data file would be more stable. But as a partner, there will be some time-taking process to make it up in the implementation. When you compare with Appian, they have to improve more on configuration and more systematic care, configuring by itself and if they are making other things in the area that they update.
The process should be automatically approved. They should also configure the maps that we initial use. I think the alerts can be used differently, or customize the targeted content mills can also be automated. Those things can also be included in Salesforce. I was looking at this map that needs to be included. Like a world map. An easy way of getting those details and then adding to it and then being able to do it in a more simplified way, visually.
For how long have I used the solution?
I have used Salesforce App Cloud for two years.
What do I think about the stability of the solution?
Stability is more than adequate. It takes a number of developers to handle that currently. Most of the people don't know that a lot of features are developed with rules. Unless you are a developer you won't be able to design it currently. So it's easy to do a mini-platform now with Salesforce. That may be the strategy, but if it is having combined information within one platform, it is stable.
How was the initial setup?
At first, the setup can be difficult. But once we get it deployed and get our tools implemented it is more automated. We have now set up a solution that allows us to easily deploy quickly. So once you understand the coding program, then it was easier for them to deploy. It usually takes about a month to deploy.
What other advice do I have?
I would rate the Salesforce Cloud App at an eight out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?