Skip to main content
Nintex Community Menu Bar

We had Infopath previous which allowed us to paste the form in the notification email as a pdf for quick review. Given that the email link directs users straight to the approval form without viewing the document that they are approving, this is a necessary feature!

Otherwise our team members are having to click the link (one click) which takes them to the approval form which they then have to click a link (one click) to see the form they are being asked to approve and then having to click back or navigate back to the email to approve. (one click... a total of 3 clicks)

Ideally the workflow is:

1) Email received with full form and can approve or reject with comments from email (one click solution)

if not then

1a) email received with full form and routed to approval form (one click) to approve or reject (one click.. total of 2 clicks)

1b) email received and routed to form (one click) to approve or reject from that form (one click... total of 2 clicks) .... NOT rerouted to the approval/reject form.

If you are using a FlexiTask action in the workflow to generate the email, you may be able to do this:



1. Edit the FlexiTask action.



2. Edit the Task Form using Nintex Forms.



3. Expand the form canvas vertically and insert a Page Viewer control below the buttons.



4. In the Page Viewer control, set the Source to the Common variable Item URL.  We also add '&IsDlg=1' after the variable, though I don't recall why at this moment (it may be to help hide the ribbon in the displayed item).



 



That allows the users to see the approval form as well as the item the approval is tied to.  Hope that helps.

Hi there,



 



@donald_mcnally is correct you can use the page viewer to preview the start form using classic forms.



 



There are actually a few options here to improve the UX.



 





  1. Using responsive you can fill task fields with workflow variables to manifest the original form in the task (essentially showing both in the same form)



  2. You can use any of the start workflow variables in the email to the task assignee, place them in a table to be readable if the information isnt too extensive and if they are only required to provide approval then change to a lazy approval this will allow them to not have to ever open a form and can view all of the information in the email and respond to the email with approval.



  3. If the information is too extensive you can use document generation with lazy approval to achieve the same but this time create a PDF print out to email with the task. 



  4. Another option would be not to use tasks at all and to instead use the workflow to direct people to respond to the original Sharepoint item, instead of using a task use an email with a link to the item and then immediately after place a wait for an item update action to react to the person updating the original Sharepoint item, this would require you to use rules to segregate the form to react to a 'task state' and who is looking at it but in general it is very good for user experience but perhaps not the easiest to set up.




hope this helps.



Jake

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings