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.
Director of IT Operation at Credit Guarantee Company
Real User
2022-04-29T15:19:04Z
Apr 29, 2022
Nintex creates forms and digital workflows to automate processes. There is a decision-making engine built using business rules. We specifically use this solution for remittance processes for a bank.
Digital Solution Engineer at a tech services company with 1-10 employees
Real User
2021-05-11T20:42:07Z
May 11, 2021
One use of the solution is for the leave request process end to end. Someone submits a request, there is verification, and then depending on the answer of the monitor of the human resources, a document is generated for a digital signature where the item is stored in SharePoint.
We have implemented an end-to-end workflow solution for a private bank for their loan origination system. We have also implemented a claims reimbursement system, and item-level permissions for SharePoint lists using Nintex workflows. For end-to-end approval workflows, Nintex workflows are deployed on the SharePoint front-end servers. The claims reimbursement workflows are end-to-end workflows for approvals of claims within the organization. Those for financial services include loan origination, legal and compliance, and core banking system workflows. Resource management and employee onboarding workflows have also been created to automate the employee onboarding process.
Technical Architect at a manufacturing company with 1,001-5,000 employees
Real User
2019-05-16T16:17:00Z
May 16, 2019
In our company, we have different deals, each with a small number of workflow processes. They were primarily using email for approvals that followed. So, we replaced this with Nintex wherever possible. Through Nintex forms, we were able to customize these as well.
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,...
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 use the solution for SharePoint on-prem and SharePoint online. The solution is deployed both on the cloud and on-prem.
We use it for internal process automation.
Nintex creates forms and digital workflows to automate processes. There is a decision-making engine built using business rules. We specifically use this solution for remittance processes for a bank.
One use of the solution is for the leave request process end to end. Someone submits a request, there is verification, and then depending on the answer of the monitor of the human resources, a document is generated for a digital signature where the item is stored in SharePoint.
We use the solution for a lot of things. However, one of the main things we use it for is approval workflows.
We have implemented an end-to-end workflow solution for a private bank for their loan origination system. We have also implemented a claims reimbursement system, and item-level permissions for SharePoint lists using Nintex workflows. For end-to-end approval workflows, Nintex workflows are deployed on the SharePoint front-end servers. The claims reimbursement workflows are end-to-end workflows for approvals of claims within the organization. Those for financial services include loan origination, legal and compliance, and core banking system workflows. Resource management and employee onboarding workflows have also been created to automate the employee onboarding process.
We are using Nintex Workflow for internal reviews between banking groups, and automating the workflow.
We implemented this product for a client. We have done quite a good number of workflows in connection with SharePoint.
In our company, we have different deals, each with a small number of workflow processes. They were primarily using email for approvals that followed. So, we replaced this with Nintex wherever possible. Through Nintex forms, we were able to customize these as well.
We use Nintex for processing workflows and forms for SharePoint 2010. Moslty for approval workflows and tracking requests.