RELATED IDEAS
Approval process
1. Currently if you need to change the Owner, Expert, add/remove key words you need the process to go through the approval process. You should be able to update this information without impacting the published version version as this realistically shouldn't impact the user.
Most users don't look at the information at bottom of procedure view and certainly don't do this on map view.
It also doesn't make sense that a new version needs to be published when an expert, owner are changed, these should be able to be changed without needing a process to be published. Especially when this doesn't impact the front end user and sometimes an owner or expert could have draft changes they don't want published and the only way to remove this is to publish the process.
2. Additionally if a Promaster declines or rejects an item in the approval/publishing queue, the item should be returned to draft/revision state, preferably with a notification to the owner/expert on why.
Current state is that ALL Promasters must decline/reject item before it disappears from approval/publishing queue. This leaves the item open for accidental approval or publishing.
3. There should be an option to bulk publish and delay publishing. Sometimes a change is happening on a certain day and everything need to change on that day. I shouldn't need to manually approve them all if they have been reviewed, i should have the option to request bulk publishing for a certain date.
4. Ability to filter Processes Awaiting Approval by Approver in order to facilitate sending a report to each approver. Ideally, an automatic report that would be sent to each approver after x number of days.
Most users don't look at the information at bottom of procedure view and certainly don't do this on map view.
It also doesn't make sense that a new version needs to be published when an expert, owner are changed, these should be able to be changed without needing a process to be published. Especially when this doesn't impact the front end user and sometimes an owner or expert could have draft changes they don't want published and the only way to remove this is to publish the process.
2. Additionally if a Promaster declines or rejects an item in the approval/publishing queue, the item should be returned to draft/revision state, preferably with a notification to the owner/expert on why.
Current state is that ALL Promasters must decline/reject item before it disappears from approval/publishing queue. This leaves the item open for accidental approval or publishing.
3. There should be an option to bulk publish and delay publishing. Sometimes a change is happening on a certain day and everything need to change on that day. I shouldn't need to manually approve them all if they have been reviewed, i should have the option to request bulk publishing for a certain date.
4. Ability to filter Processes Awaiting Approval by Approver in order to facilitate sending a report to each approver. Ideally, an automatic report that would be sent to each approver after x number of days.
1. There is a similar idea here https://nintex.uservoice.com/forums/919189/suggestions/40680556 so please vote for this if you would like to see this implemented
2. We are planning on implementing this functionality with our sequential approval feature
3 and 4. We don't have plans to implement these changes right now so we'll monitor interest from other customers for now.