Nintex is best suited when processes are drawed by the business and then can be furter enhanced by IT professionals. When only used by business units we see that there are some lose ends in processes and some bagic process knowledge is needed. Therefore it is wise that the persons in the business who will use Nintex have some basic knowledge on how to set up business processes
Using it in the application support team is worth it as it is capable of carrying a lot of information. But using it for a Service Desk operation might not be of much use as it won't be used up to its full potential and will be costly as compared to other alternatives available in the market.
Adding Machine learning features like the "Image and Text Automation" component, which allows bots to extract data from unstructured sources like scanned documents or PDFs.
Natural language processing (NLP) features to understand and interpret human language, which can be useful for tasks like customer service or data entry. mostly for middle east countries where Arabic language is used.
Integration with external systems where many industries uses their own legacy systems and they need RPA bot to interact with their systems as well.
Adding More OCR tools for Document data extraction and dynamic content.
Providing admins/devs with easier mechanisms for providing businss stakeholders with self-service admin capabilities across the platform
Tutorials on how to be the best at reporting in servicenow
Guided tour functionaltiy is a bit rigid and could use more workflow capabilities
Making it easier to push form variables to the user so there is more context when providing an approval. The out of box approval UI/form is terrible in my opinion.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
Everybody in the company is happy to use ServiceNow. All people are happy to use a user-friendly web tool in order to open IT incidents. IT people can easily support people with a stable and solid tool.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
As a regular user of the ServiceNow platform, including the incident management, change management and enterprise application management modules, I find that I am able to competently use the platform with minimal training and assistance. User guides are available from the vendor if required. The customisable front-end that we use in the organisation as an ordering tool for internal IT services is very easy to use, and makes searching for the required IT service simple for business users.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
We have many levels of interaction with ServiceNow. The first line of support sometimes is not equipped to resolve more complex issues, but the escalation process is clearly defined and followed with limited friction. Our account team is very responsive and willing to brainstorm ideas to improve and increase usage. We also have direct interaction with product teams to see previews of new features and at times to provide input to influence implementation details.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
test runs for key persons to insure the system is set up prior to rolling out I think the platform is good, I think the roll out and the local implantations is where we are failing as a company in using Nintex
It's much more reasonably priced and we were able to actually experience the platform for a bit before we made a decision. And by the time our demo was finished we had already started depending on it for some of our processes so it would've been very hard to separate from it
ServiceNow is by far a better tool over Remedy. Its ability to integrate so seamlessly to so many tools allows for plenty of opportunity to streamline and improve processes. Servicenow has intuitive flows that allow you to quickly pivot if process change. Its adaptiveness is what makes it far better solution over Remedy
1. It is not great when they can't seperate apps/products from a particular sku, forcing you to make a business case for a larger portion of functionlity than your current business case seeks to address. 2. ServiceNow reps are able to work with you when economies of scale are projected out. They are willing to start at a desired tier and provide pricing at applicable upgraded tiers
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
Very easy to use. Capture more data from the Incident and problem management. Easier to escalate and following the change management process to resole the issues.
We have saved our company thousands of dollars by creating our own customer support system rather than using a 3rd party tool.
The ability to generate documents/PDFs in workflows has solved a great number of process issues for us and groups who had previously been using paper documents.
Automating many permissions updates through workflows has been a huge time saver for repetitive processes.
Ensuring good service support internally and externally has triggered opportunities to sustain good links with everyone and opened the door to more sales and successful business and ServiceNow has been key in all this, so the investment came back to us faster than expected.