Wouldn't it make sense for the 'Triggers and Inputs' section to be at the top rather than at the end of the procedure. They are supposed to support the user experience by providing information on what triggers the process yet most users would not know to scroll to the end of procedure to see them. A trigger starts the process, so it makes sense for it to be at the beginning.

It would be fantastic if we could make Key search words editable without needing to get additional approval from Process Owners and Process Experts, similar to when we change Process Review Dates.

We want to be easily be able to update Key Search Terms against a process with mimal red tape, this way we can action feedback regarding navigation and discovery of processes immediately without having to go through and approval workflow.

It could be made similar to Process Review Dates and cycles, where the change is logged in the chat log but it doesn't need explict signoff.

When a current owner/expert leaves and a new owner/expert is allocated, the historical open feedback does not carry through to new owner on the dashboard.

Please can this information be made transferable.

Provide the ability for Promapp to automatically create overview (end to end) process views from process that are linked together instead of having to manually create that overview.
Refer to the attached document for a mockup example (the last page shows the auto generated overview process created from the processes shown in the preceding pages

It would be great to set default print options for the company to have a standard when generating a PDF for a process.

As a Promaster I can set the default print options to what the company agrees on e.g. Flowchat ticked, Timeframe unticked, Colums 1, etc...
The users can individually select other print options if they need to when printing the individual process.

We notice that staff rarely look at the inputs and outputs because in the map view it doesn't show what the specific input/output is, and in the procedure view the input is listed at the end of the process activities. Therefore our inputs/trigger information is mapped as Activity 1 in most processes.

Suggestion to improve this: the green input/trigger box show the activity name - as it does for each activity in the body of the process. Likewise for the output box.

Hi
It would be good to be able to set permissions on checklists.
At the moment checklists are open to anyone – they can’t be locked down – anyone can edit them.
It would be good to have the option to have set users/groups to be able to view/edit/create checklists.

It would be great to pull a report on the words users search so that we can see if the process titles or key words need to be changed to help users find the right processes.
Would also be good if the search didn't find any matches to provide suggested search terms (similar to Google)

Having the ability to alter the colours of Promapp would be a useful feature for organisations to customise it to their own branding.

You can currently do this for the emails, which is great. However being able to do it for the general site would also be very helpful with embedding the system within the business.

Even a small change such as allowing Promasters to customise the blue bar, buttons and font would be a significant change.

The 'Process Approval Workflow Status' report currently provides a published/unpublished status for processes. It would be helpful if this report could include more detail of the exact stage of approval that the process is in, rather than 'unpublished', and also who has provided what approvals and whose are outstanding (see example attached of our manual workaround).This is particularly useful information for onboarding clients who will have a large amount of unpublished processes at first.

It's very difficult to set up viewing permissions... several steps that are tough to follow and remember. Plus even looking at the indented folder structure just below is nearly impossible to do with naked eye. Plus I think I saw inconsistencies in how parent-child indentation was displayed.

Allow me to hide the Contact Support under the Help menu. I don't want the general user contacting Nintex Support. Many times they are asking a question about a process that Nintex can't answer or they are reporting an issue that should be vetted through the Promasters or our internal help desk first.

Please integrate the sub-process details in the printing (PDF) of a (main-) process. The result should be a single document for the process, its details plus the integrated sub-processes and their details.
Thank you.

As Promaster when publishing processes, process changes to acknowledge states "process has been changed by [promaster name]", it would be preferable to state "process has been published by [promaster name]", I find employees think I am changing the process, where in fact as promaster I am publishing the process, not making the changes.

Hello,

we use brands for e.g. our project management framework, including a logo. Therefore it would be great to have different 'branding options', so we can e.g. include the project management logo into all related processes.
This is quite important for us, we strive to map all our processes in Promapp, but without branding option our marketing team will still recreate thosel processes in InDesign and we lose quite a lot of ability...

Thank you!

It would be great if the Trigger/Starts, Inputs and Outputs text boxes were larger/longer. It's difficult to type in, particularly for people learning to use Promapp, after typing a few words you can't see your sentence in full.