I noticed the minimode links seem to display unpublished changes too, i dont recall seeing this before.

Is it because you’re a process editor and therefore would see the pending changes?

I’d like some clarification on this too, thanks for raising!

Eddie

Good day, @TaniaS and @EddieThomas -

I’ve raised this internally with the Process Manager team so we can update both Nintex Help and the How-to Center with the correct minimode functionality. I’ll update this post as soon as I get more info. 
 

-Sam

Good day, @TaniaS and @EddieThomas -

Thank you for bringing this to our attention and for sharing your experience with the minimode functionality using Process Manager. Please see below explanations for each publishing state:

• Unpublished processes

  • An unpublished process is any process that has never been published. For example, version 0.X. A minimode link generated for an unpublished process shows the latest version of the process until it is published. Once the process is published, the minimode link shows the latest published version of the process.

• Published

  • A published process is any process that has been published. For example, version X.0. A minimode link generated for a published process shows the latest published version. In other words: The URL will always show the latest published version, not the specific version you shared.

• In Progress

  • An in-progress process has been previously published and has some new changes saved to it.  For example, version X.X. To generate a minimode link for an in-progress process, a Process Editor should view the in-progress version of the process and then select the Share Process Link option. This link will always show the most recent version, regardless of the publishing state. In other words: The URL will always show the most recent version, regardless of state.

My apologies for any inconvenience this may have caused. These explanations have been updated in our How-To Center article and will reflect accordingly in our Help Documentation. Once again, thank you for reaching out and we hope this answers your questions relating to minimode links.​​​​​​

-Wasim​​​​​​

Is there any way of knowing which of the 3 methods described above was used to generate the link?

We now have a situation where multiple processes are being shared across hundreds of SharePoint pages (and elsewhere) that may display unpublished changes depending on the version of the process when the minimode link was generated. This isn't ideal!

How do I know if a change to a process will be visible to someone who has a minimode link?

Thanks for responding @Nintex_Sam and @Nintex_Wasim 

The way I read this is regardless or what status the process is in, the minimode will now display the most current version, and additionally, once a process is published and edits are made, the end user can toggle between the most current version and the latest published version, is that correct?

No, that is incorrect.

For minimode links created when a process has unpublished changes, the link will show unpublished changes, even after the process is next published (i.e. v1.1, v1.2, v2.0, v2.1, v2.2, v3.0).

For minimode links created when a process is published (vx.0) it will only show published versions (i.e v1.0, v2.0, v3.0).

The issue here is that you may have a published process (say version 5.0) that is being displayed via a minimode link that may/may not display any unpublished changes depending on the process version when the link was created.

There is no way of checking a given minimode link to determine the version of the process when the minimode link was generated. The only way to ensure the user doesn't see unpublished changes (which is how I thought minimode worked) is to either:

• Test it by making a change to the process and see if it changes the version in the minimode link (and then fix it) or
• Fix it by recreate the link from the published version

It looks like this issue has been raised before Viewing processes using minimode links | Community (nintex.com) @Penny highlighted the ‘trick’ to make it perform as you described in her response, i.e.

“So in summary - the trick is - the make sure you are viewing the published version of the Process for any minimode links where you want the minimode link to always show the latest published version of the process. “

Thanks @EddieThomas 

The trick makes sense, I just tested minimodes created on an in progress version vs a published version in my tenant and it behaved as you described, thanks, I’m clear on how to explain this to my client now