As you may know, you can build custom steps to do anything that you want them to do, and use them within workflows. Many of our customers build custom steps to perform certain functionality within workflows, but what about the validation of these step inputs? We explain how it works here.
Lately, it seems like software organizations have been focusing on merging and stream-lining their multiple code bases into a single, flexible, and more manageable base. A good example of this is Microsoft Windows 10. Before Windows 10, Microsoft had multiple operating system code bases such as Windows XP, Windows Vista and Windows 7. With the growing demand for multi-device support, Microsoft saw the need to stream-line their code base toward a single operating system that could run on any device – enter Windows 8. Now with Windows 10, the same OS will run on a mobile device such as the Lumia, a tablet device such as the Microsoft Surface 3, and of course on personal computers, laptops, and servers.