This post was to be the final post of our "The iPhora Journey" series and summarize our entire journey and what we created. However, as I was preparing the final post I realize there was one item that I hadn't discussed. That is the experience of purchasing a product and installing it onto a Domino server. So, Part 14 will be the final post of this series. Whether you are purchasing a product that you really want or paying bills online, purchasing services or products online has become the norm. For a new product launch we wanted this easy-to-buy and deploy experience. Depending on the version of our product, different features are enabled. If a customer wants to upgrade the product to a more advanced version, the experience should be as easy as signing up for the upgrade, paying and the new features should available in the customer's installation. This is expected for most public cloud-based solutions. However, not so easy for private cloud/on-premises solutions. N
Public vs Private In the digital automation market, which includes workflow and business process automation, there are literally dozens of no-code or low-code platforms available as public cloud solutions. They range from products like Zapier to Tray.io. In general, they all provide easy-to-use interfaces for assembling cloud services together in order to automate processes. Some are geared towards individual users and some towards enterprise businesses. However, aside from the ones intended for individuals or very small businesses, they may require some significant setup, configuration, and administration. Public cloud-based solutions have a number of advantages for process automation. You can sign up and get access to these services within minutes and have a new process up and running in a relatively short time. However, the majority of these solutions operate by routing your data (and the subsequent responses) through a series of different cloud services. Not only is your process de