Nintex – Why get a Demo
If you go to the Nintex web site today (October 2015), you’ll find a nice orange button that says “Get a Demo”.
Why would you want a demonstration rather than installing a trial of the software and just messing around with it? Well, the two options are not mutually exclusive. You can do both. But there’s a good reason why the Get a Demo button is at the top of the other buttons. A demo consists of one of the following:
1. A Nintex Partner and usually someone you have already worked with, who is a trusted adviser performing the demonstration to you.
2. or it could be a Nintex person/people who are performing the demo.
Either way, the result is that with usually an hour, you get to see as much of what Nintex products can do as you can. But is that all? If that is, why not watch a video on youtube? That’s not it. This demo can be in person, if the person performing the demo is local, or it could be a call and some screen sharing. Regardless of which way it is done, you have the ability to ask question and make the demo interactive. The goal is for you to learn what the products can do, but also what you can do with the products. Wow, that sounds a like JFK-esque. Apologies for that.
If you really want to get the most out of a demo, have some questions lined up. Have an idea of business processes you are trying to automate, or forms you’re trying to build. Come armed to a demo knowing what you would like to be able to do.
Or, if you can provide some of those questions beforehand, the person performing the demo will be better prepared to help you with your needs.
Now that you’ve had a demo performed to you and you know what the products can do, what’s next?
Go get a Trial. Install it into a test or Q/A environment and see what it can really do. Think of a process that you would like automated, and try to build it out with Nintex Workflow. Your workflow will most likely run on a list. Try to customize the form experience for that list with Nintex Forms.
Don’t pick an extremely complex business process during a trial. The aim of a trial is for you to get a good feel for the product you are trialing. By picking a large and complex business process, you are going to get yourself in weeds and it may get hard to get out. During the trial process, pic one or two processes that you can build out relatively quickly. Once done, you’re in a better position to extend those processes and make them more complex.
When looking at Nintex Workflow, there are so many actions that you can use, there’s not necessarily one best way of building some business process logic. If you look at the on-prem version of Nintex Workflow, we’re looking at 250 actions you can use. There are definitely multiple way to do things. Start simple and build on that. That will allow you to build on the knowledge you learn from building those simpler workflows.
Here’s an example of a very simple workflow:
Notice there are only 4 actions in this workflow. It’ll be fairly easy to build and if you have anything weird going on when you run, it’ll be easy to debug.
If you go all out with the first workflow and build something like this, then it’s going to get frustrating from the onset.
You won’t have the experience of building workflows using this designer. Knowing which actions are available and what configurable options they have. Although the learning curve for building workflows using Nintex Workflow is small, diving straight into the deep end is fraught with danger. Now you’re looking at the workflow above, and some of you may think it’s complex. From my experience, workflow can get a lot more complex that the design you see above. But complex means different things to different people.
I could look at this workflow and see a bunch of action and branches and think, “Wow this is some complex process. It has so many actions and branches, it must be doing a lot.”. But depending on what actions you are using, even though visually, it may be a large workflow, as compared to the previous one, a workflow like this may only go down one path. So when you see what the workflow did as it ran and completed, it may have only run a subset of the actions you see in the entire workflow design.
On the other hand, you could build a workflow with 7 actions workflow that visually may look very simple, but is actually quite a complex process that jumps back and forth between approvals based on different conditions.
Get a Demo from a Nintex expert is a great place to start, as you grow your business and find that automating your business process and forms will really give you that time saving and allow your employees to focus on growing that business.
If you’re looking for a Demo, request a demo here : Request a Demo
If you want a Trial, go to this link : Request a Trial
If you’re interesting in Drawloop by Nintex and you want to do Document Generation in Salesforce: