7 - Nintex Promapp

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Change description: Ability to amend wording prior to publishing

    When a change is submitted for approval, the wording in the change description is locked from that point onwards during the PAW. If the change description wording does not accurately reflect the changes made, the Process Expert/Process Owner/Publisher currently must decline the submission entirely and the submitter has to resubmit the changes with an accurate description. It would be helpful to have the option for roles in the PAW to be able to amend the wording in the change description up until the point of publishing.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Training tags - allow use of existing system tags

    Allow existing system tags in Promapp to be used for Training Tags

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Open for voting  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add version number in the "to approve" and "to publish" list

    Having the version number in the "to approve" and "to publish" list enables the publisher and approver to establish whether or not this is the first time a process is coming though the approvals process and as such prioritise these above ones which are just being changed.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Open for voting  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Customise Menu item

    I would like to be able to change Help> Contact Promaster to Contact (My company name) Promaster.
    Staff have said they thought that by clicking the Contact Promaster option it would send a message to Promapp / Nintex. They did not realise it would contact the in house SME, which is what they wanted to do.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Streamline @todo's

    Currently to type it up and assign to someone else, it's a 3-step process. this frustrates our editors and owners/experts. Prefer it to be single step similar to how this is done within Google docs

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  6. Ability to configure the message bulletin to be limited within the Process Group

    For relatively large organisations, it could be chaotic when everyone starts posting messages on the bulletin board. Would be great to have the ability to limit the visibility of the messages to the process group level so users only see messages that are relevant to them.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Open for voting  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. QR codes

    Are there any plans to introduce QR codes for processes?

    We’ve got a request to set up a promapp process for charging an electric vehicle, and I’m thinking of best ways to set this up for users.
    Having a QR code on the dashboard that links to the process would be a very useful option!

    Rather than all promapp users producing their own QR codes, I wonder if Nintex could set this up for all to use

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Option to make feedback only visible to Owner/Expert

    An option (like a tick box) for the person submitting feedback to only make it visible to expert/owner (and promasters).

    This may encourage more honest feedback if they know it's not going to be seen by the rest of the Promapp community (in our case, all employees).

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Display when Improvement Restricted

    You can restrict an entry in Promapp Improvement Module, however you cannot see if an entry is restricted unless you go into the entry. Display on the register summary when an entry has been restricted. Make it easily identifiable when an entry/improvement has been resticted

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Open for voting  ·  1 comment  ·  Improvement add-on  ·  Flag idea as inappropriate…  ·  Admin →
  10. Promapp Courses linked to Promapp user Access Levels

    Loving the Learning Central Promapp content and currently using this as a method of onboarding our users and writers.
    Would be great to have an Adfmin User visibility to see who has logged in, completed courses etc.
    Would be handy as a way of gauging competency when providing users with access.
    Even better if it could then link to the users in Promapp only allowing higher access once relevant courses have been completed.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. When process is in progress the default view should be the published rather than the draft

    We have had feedback that if person has editing status, they would still like to see the published version as the default view when they click on a process. because there is a risk that unapproved process is used rather than the published. Although you have editing rights, does not mean you are the one actually doing the editing.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Open for voting  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. More control over glossary tagging

    Currently, words will automatically tag from the glossary which is a feature we love until it doesn't quite make sense for the context of the process.

    It would be good if you could un-tag a definition similar to how you can untag a system when a keyword is mentioned within your edit page.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Option for numbers only field type in improvements form fields

    When setting up form fields there is a list of options to choose from for field type. If we could have a number field type that would force numbers only input it would guide users to enter the correct type of information and cut down on fix-ups.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Improvement add-on  ·  Flag idea as inappropriate…  ·  Admin →
  14. Change an Activity to a Process (at the cick of a button)

    I would like to be able to change an activity in a process into a separate process? So if I already have the activity listed and realise this should actually be a separate process, an option to create a process out of this activity would be awesome.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Open for voting  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enable feedback to be lodged against a document

    Currently, feedback cannot be lodged directly against a document, it must be lodged against the process the document is linked to. While I understand the thinking that changes to documents often affects changes to processes, there is also the scenario where one document is linked to multiple processes (possibly owned by different Process Owners). In this scenario, there is a risk that the feedback is lodged against the 'wrong' process resulting in either delays to approval while correct authority is being sorted, or the feedback is approved without proper authority.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. More dynamic dashboard reporting

    Overdue dashboard items for Promaster and Portfolio Managers show only overdue incidents and not overdue actions. If only 2/5 actions in an incident is overdue then the incident will not be reflected on the Promaster / Portfolio Managers Dashboard. Promaster's / Portfolio Managers can currently only overcome this by downloading the excel report to identify the 'real' number of actions overdue. This is inefficient for reporting to senior management and audit committee's.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Dashboard notification for archived processes

    Currently when a process that uses the ALL STAFF role gets archived all users get notified via their dashboard. This causes unnecessary confusion among users.
    Could the notification for archived processes be changed so that only the Process Owner and Process Expert are notified, or if that cannot be done then no notification is sent.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Improve User data for filtering / reports

    Suggest adding user start date and phone contact to data points collected, and maybe even some open fields which could be used for the specific business needs to further categorise / filter users. Then ensure that this is reportable.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Open for voting  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Cancel Process System Tags from the System Tab under admin

    From the System Tab, Select the System Tag and be able to remove the System From Processes, eg: Top. Top is a common word that is used outside the System it is referencing and it would be made simpler if we could deselect the Process it has indexed in.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. eliminate doubling up of linked processes in Procedure and Outputs

    refer to customer support case "Nintex Support Case #00292307"

    if the user wants to show a linked process on the map, there should be a function within the outputs tab to choose "yes" or "no" as to whether the linked process should appear on the map view. At this point, it has to be added in the procedure and also in the output tabs.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Open for voting  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base