Process maturity is an indication of how close a developing process is to being complete and capable of continual improvement through qualitative measures and feedback. Thus, for a process to be mature, it must be complete in its usefulness, automated (where appropriate), reliable in information and continuously improving.
In order for an organisation to understand it’s process maturity, having the ability to audit and tag a process to categorise it to show what stage, tier or level of maturity a process is at. This will provide visibility and reporting on the organisations process maturity. This also provides focus for improvement teams to identify low maturity processes that require continuous improvement to lift maturity levels based on the organisations chosen Process Maturity Model. (i.e., Levels 1 through to Level 5)
Keeping the Maturity Level or Tier generic as 1,2,3,4,5 will allow usability across all Promapp users regardless of the Process Maturity Model adopted by each organisation.
The Process Maturity Tag could be similar to the current Lean Tagging. It will need to be at a process level (rather than at an Activity or Task level) and have associated reporting to assist organisations understand Process Maturity and drive Improvement focus.

The Promasters can see all the processes and documents that need to be Reviewed but if the Promaster wants to search for a process they are the Owner or Expert, they have to scroll down the full list of processes to find it and then review it. If a Search option could be provided in this area it would make the search much easier. OR alternatively, provide a Review button in the overdue process map itself so the process can be reviewed and the notification be cleared from the Dashboard. This will be useful when the process does not require to be edited.

Hi,

I generate the Process Changes not Yet Viewed by User report every month to monitor compliance within the business. I have just found out that Nintex has changed the report and now it can only be generated for one role at a time, not for all roles. As a business with 44 roles, this will be a time consuming process. Promapp is meant to assist us in streamlining processes, not create lengthier time consuming processes. I have raised this with the Support team, because initially I thought the report wasn't working for me.

We have been a long-term, reliable, and low maintenance client for Nintex Promapp. As a business we rely on the core functions of Promapp in order to write and publish new processes and documents and monitor compliance. Without compliance monitoring, Promapp as a tool isn’t a complete package for us and is no longer suitable for our business. I doubt that Nintex is only offering Promapp to small businesses with low staff numbers, where selecting one role at a time would be acceptable.

Please reinstate the functionality of the report so that it can be generated for all roles. I can't be the only customer who has raised this issue.

Regards
Natasha

Not really a feature but more highlighting a current issue we are experiencing (but was asked to post it here by Nintex Support).

Currently Promapp has Autocomplete enabled on the site, so whenever a user tries to create a new process the 'Process Owner' and 'Process Expert' fields are both mapped to 'name' for autocomplete.
If the user ends up clicking their name when autocomplete is shown, this causes Promapp not registereing the user as it was entered as plain text.

This is something we come across every single training session we hold (as part of the training session we have the users create a process). The temporary workaround is to type the last name first which won't trigger the autocomplete. The more permanent (though not ideal) workaround is to ask users to disable their autocomplete on the browser.

This may not be as big of a problem if the organisation only has a handful of process editors. However for our organisation, we upskill every process owner and expert so that they are able to write a process, so we have a lot more users creating processes on a regular basis (currently we have 200+ users that are trained).

Disabling Autocomplete on a website from the developer's end is possible. Here is one (of many) articles outlining how it could be done:
https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion

Currently hits by users on embedded processes do not show up in "Process hits by user" or any other report.

To explain further

What I am interested in is “Process hits by user” as this gives a feel for who is viewing and using what in terms of Promapp processes - this gives a picture on the buy-in from staff i.e. are they accessing and using Promapp appropriately or is it being bypassed or ignored.

Because we have a shared Quality Management System manual with the “Simpli” instance of Promapp a large number of Process variation instances (Wellington City Council variations) are embedded into the “Wellington City Council” instance of Promapp in the “Building Compliance and Consents” Process Group. These embedded processes do not show up in the “Process hits by user” report.

Other “Simpli” users will find this feature useful.

I appreciate that other customers of Nintex may not currently be using Process variations and embedded processes – however I am confident that this is a feature that they will want when they do.