We use the Nintex Process Platform to connect internal users across different departments, streamlining workflows and collaboration. As an international organization adhering to evolving standards, Nintex provides a flexible and scalable platform that integrates seamlessly with the Microsoft ecosystem to build a comprehensive collaborating environment. It serves as a fundamental layer, enabling efficient communication and data exchange among our teams.
There are a few workflows, including one of the recent workflows we failed to deliver for a client, Jazz, a telecom operating in Pakistan. They sought to automate their HR processes through a finance solution. As an example, we developed an insurance claim workflow for them. With approximately 10,000 employees within their territory in Pakistan, they aimed to streamline the insurance claim process. For example, if someone lost their laptop. The normal process takes so much time, the manual effort, and the paperwork to get different information from peers. Our solution centralized the process, allowing the finance team to monitor the status of claims and their dependencies on external entities, such as vendors. We integrated a specific step within the workflow to track the progress of claims with the vendor. The workflow facilitated seamless communication with the vendor, providing updates on the status and estimated time. This data, combined with inputs from different department heads and finance, enabled a comprehensive evaluation of each request, leading to informed approvals or rejections based on predefined parameters. The workflow consisted of seven to eight steps, each incorporating approvals and developer oversight. This is a high-level overview of our engagement with Jazz for their workflow automation.
So we have a process flow for which we wanted to use Nintex Workflow. So in SharePoint currently, we have set up that Nintex Workflow. So users used to submit and raise requests in the solution, and that is used to trigger the automatic workflows on the fact that a ticket is raised. Then, the approvals are taken. So all those things we had coded in Nintex Workflow. So, the solution was for some kind of an approval process within our company because there are multiple stakeholders, so it goes to multiple stakeholders for approval, and they approve it. All that happens when working with Nintex Workflow.
Business Automation Developer at Polaris Bank Nigeria Plc
Real User
Top 5
2023-05-12T14:47:00Z
May 12, 2023
We primarily use K2 in conjunction with Kaltura within Teams. We use Kaltura for expenses, email cases, cash advances, retirement, and company management. For company management, it involves addressing issues with account numbers by coordinating with the bank. The login use cases help log those requests and assign them to the responsible users for resolution. We also use K2 for FX services, making subpoenas, and handling hard decisions or licenses. File onboarding requests are not as frequent.
We use K2 as a business process management tool in our company that is connected with our applications. Also, we are using an American-based workflow engine besides K2. We also use ELSA, an open-source platform. Mainly, we use the tool for automation and workflow. So, we are using ASP.NET for development. Also, we are connected with K2 tool.
System Development Analyst at Saudi Electricity Company
Real User
Top 20
2023-03-09T21:55:03Z
Mar 9, 2023
We primarily use the solution for workflows we develop them and deploy them so they appear in the K2 Workspace. We have smart objects and smart prompts as well as views of everything.
Our searches are automated for the approval process, and we have automated our dual management process with K2. We have 41 processes automated within K2. It was only a process automation tool for workflows and approval, but now since being bought out by Nintex, we will have many other products available to use. For example, the RPA part of Nintex can plug into K2 and be used together.
We are currently using K2 Five classic. We have several use cases. The main use case is the vendor request. We process all requests that come in from existing or new vendors through K2. Our legal department uses it for checklists and other things. The approval process, onboarding, and all other related things are also done through K2. It is used for onboarding, termination, suspension, access, and many other things. All these things are automated.
Technology Unit Manager at a tech services company with 501-1,000 employees
Real User
2020-09-09T06:28:55Z
Sep 9, 2020
We primarily use the solution for government and public e-services. We always deal with K2 in these areas. We use the solution to mostly deal with workflows.
Program Manager - Intelligent Automation at a engineering company with 10,001+ employees
Real User
2020-09-08T09:10:01Z
Sep 8, 2020
We have predominantly been using the solution as the front end for automation solutions. I'm a program manager. We don't have a direct link to K2, but we work closely with them and carry out a lot of maintenance and other work through them. So it's quite a deep-rooted relationship.
Chief Information Officer at a construction company with 51-200 employees
Real User
2020-05-10T08:06:04Z
May 10, 2020
Our use case of the solution is to help the sales people in the field, enable them to have all the information from the backend and to more easily put together a proposal for management regarding new tenants of shopping centers. There is a process that flows to the works department, the legal department, the asset manager, and the project manager. They are able to make suggestions, comment, discuss numbers, and make some declarations. It provides good feedback to the management who then need to make a decision. We provide this service for both internal and external clients. We're a customer of K2blackpearl and I'm the company chief information officer.
Nintex Process Platform automates processes such as approvals, vendor requests, and leave management, optimizing workflows in sectors like government, banking, and HR.
Nintex Process Platform streamlines collaboration and integrates seamlessly with Microsoft tools. It supports account management, loan origination, claims reimbursement, and public e-services, while also assisting with onboarding, resource management, and compliance workflows. Users benefit from its ease of maintenance,...
The main use case is accounts payable. We also implement it for human resources processes like onboarding and insurance plan changes.
We use the Nintex Process Platform to connect internal users across different departments, streamlining workflows and collaboration. As an international organization adhering to evolving standards, Nintex provides a flexible and scalable platform that integrates seamlessly with the Microsoft ecosystem to build a comprehensive collaborating environment. It serves as a fundamental layer, enabling efficient communication and data exchange among our teams.
There are a few workflows, including one of the recent workflows we failed to deliver for a client, Jazz, a telecom operating in Pakistan. They sought to automate their HR processes through a finance solution. As an example, we developed an insurance claim workflow for them. With approximately 10,000 employees within their territory in Pakistan, they aimed to streamline the insurance claim process. For example, if someone lost their laptop. The normal process takes so much time, the manual effort, and the paperwork to get different information from peers. Our solution centralized the process, allowing the finance team to monitor the status of claims and their dependencies on external entities, such as vendors. We integrated a specific step within the workflow to track the progress of claims with the vendor. The workflow facilitated seamless communication with the vendor, providing updates on the status and estimated time. This data, combined with inputs from different department heads and finance, enabled a comprehensive evaluation of each request, leading to informed approvals or rejections based on predefined parameters. The workflow consisted of seven to eight steps, each incorporating approvals and developer oversight. This is a high-level overview of our engagement with Jazz for their workflow automation.
So we have a process flow for which we wanted to use Nintex Workflow. So in SharePoint currently, we have set up that Nintex Workflow. So users used to submit and raise requests in the solution, and that is used to trigger the automatic workflows on the fact that a ticket is raised. Then, the approvals are taken. So all those things we had coded in Nintex Workflow. So, the solution was for some kind of an approval process within our company because there are multiple stakeholders, so it goes to multiple stakeholders for approval, and they approve it. All that happens when working with Nintex Workflow.
We primarily use K2 in conjunction with Kaltura within Teams. We use Kaltura for expenses, email cases, cash advances, retirement, and company management. For company management, it involves addressing issues with account numbers by coordinating with the bank. The login use cases help log those requests and assign them to the responsible users for resolution. We also use K2 for FX services, making subpoenas, and handling hard decisions or licenses. File onboarding requests are not as frequent.
We use K2 as a business process management tool in our company that is connected with our applications. Also, we are using an American-based workflow engine besides K2. We also use ELSA, an open-source platform. Mainly, we use the tool for automation and workflow. So, we are using ASP.NET for development. Also, we are connected with K2 tool.
We primarily use the solution for workflows we develop them and deploy them so they appear in the K2 Workspace. We have smart objects and smart prompts as well as views of everything.
It is used to automate all business applications.
I primarily use the solution as a development platform.
Our searches are automated for the approval process, and we have automated our dual management process with K2. We have 41 processes automated within K2. It was only a process automation tool for workflows and approval, but now since being bought out by Nintex, we will have many other products available to use. For example, the RPA part of Nintex can plug into K2 and be used together.
We are currently using K2 Five classic. We have several use cases. The main use case is the vendor request. We process all requests that come in from existing or new vendors through K2. Our legal department uses it for checklists and other things. The approval process, onboarding, and all other related things are also done through K2. It is used for onboarding, termination, suspension, access, and many other things. All these things are automated.
We primarily use the solution for government and public e-services. We always deal with K2 in these areas. We use the solution to mostly deal with workflows.
We have predominantly been using the solution as the front end for automation solutions. I'm a program manager. We don't have a direct link to K2, but we work closely with them and carry out a lot of maintenance and other work through them. So it's quite a deep-rooted relationship.
Our use case of the solution is to help the sales people in the field, enable them to have all the information from the backend and to more easily put together a proposal for management regarding new tenants of shopping centers. There is a process that flows to the works department, the legal department, the asset manager, and the project manager. They are able to make suggestions, comment, discuss numbers, and make some declarations. It provides good feedback to the management who then need to make a decision. We provide this service for both internal and external clients. We're a customer of K2blackpearl and I'm the company chief information officer.
Our primary use for this solution is for automating workflows in business applications.