Does process design or implementation always have to be complicated and require a high level of programming effort?

In my last blogs I have reported on the topic of process optimization and pointed out what should be considered here. Today it is not about optimizing processes, but much more about implementing them. Exactly this point is always considered the most difficult one. Why is this so? I can answer that quite simply. When you talk about process modeling and later automation, you quickly get into the direction of programming. From my point of view, this does not have to be the case, since today there are very excellent and easy-to-use solutions in the field of process automation. Such as our low or no code platform Nintex Workflow Cloud (in the further course of the blog called NWC).

With NWC, processes can be modeled in a very simple way, but also configured without the need to get into programming. Now you'll probably think to yourself or others "yes, no, it's clear", but that's not possible. Just like you, I used to think the same way, but since I joined Nintex, my thinking has changed completely. 

The times for lengthy process or project implementations are over, as processes can be implemented much faster with the No code or Low code solutions. One reason for this is that you have a simple drag & drop design, process rules are super easy to configure and that you can carry out the implementation from any location.  

In the next section I would like to briefly explain how I approached a "vacation request" workflow and how quickly I was able to implement it. 

The implementation did not actually take much time, as the process should not be complicated. Therefore I have limited myself to the essentials. You should do that from time to time, otherwise you can get lost in many small details and the workflow becomes complex again 😉.

The first step is to design a start form where your employees can request their vacation. 

For this purpose, we also provide a simple drag & drop interface with many design elements in NWC. Form-based rules can also be easily set, for example. 

After completing the form, we will look at the actual workflow and how to configure it. One thing to be said in advance, I have not done any programming here. 

For our example I used the following workflow actions:

- Assign a task

- Send to email

- End this worklow

With exactly these three actions, this workflow could be implemented in less than 2 hours. Most of the time is not used for modeling the workflow, but much more for designing the forms. Yes, forms. In the beginning I pointed out that you start with the form for the vacation request. However, you can also use the action "Assign a task" to store individual forms for the respective release. 

Finally, you configure the respective e-mails with the individual texts. These can also be configured with simple board means. Likewise the possibility of the use of "variables" exists around contents from the form of the vacation request there again to use. This may look a bit technical at first glance, but it is not, because you only have to click on the variables. 

Now your workflow for the vacation request is finished and can be used by all employees after publishing. Vacation is the most beautiful thing for an employee 😊

Of course, I have also provided you with exactly this workflow in our Nintex Gallery (https://gallery.nintex.com/), so that you can perhaps use it as a basis for your vacation application. Furthermore, there are more workflow examples available in the Nintex Gallery. 

I hope that I was able to show you that workflow modeling does not have to be complicated and can also be resource-saving. 

Should you have any further questions, please do not hesitate to contact me. 

It only remains for me to say, have fun modeling and stay healthy.