Automate

Does anyone have pointers/tips on how to transition to updated forms? There are 2 recent instances that we have had: one where I kept the form name the same, but made a small change to one of the workflow transitions to allow cancelling the form.  The other is 3 forms where there were major changes to the workflows of the forms so I changed the names and put links on the old forms to the new versions.  I can't delete the old forms as there are still some in progress that need to be completed.  I have added a link to the new form and removed the buttons on the originator views for the old forms. 

In both instances, it seems that the browser--likely Chrome--has cached the old forms so users can still submit them. I've had some users successfully refresh forms, but wondering if there is a better way to handle this other than working individually with originators.

Thanks,
Sue Jarvis
Louisiana Pacific Corporation

------------------------------
Sue Jarvis | Analyst
General Motors Company (GM) | 6143296304
------------------------------

Hi Sue -

Are all the forms being launched via link (from button) from within another form?  

If the web part is used, it always runs the new version of the form, as each version has its own URL. If a link is being used, you'd need to make sure it's using the latest version's URL (which would need to be updated, as needed) or use a version-agnostic URL. 

Here's an example of a version-agnostic URL: 
http://winshuttle.site.net/Formsite/_layouts/new_form.sharevis.aspx?type=AJ%20The%20Date%20Format%20Test%20v1

The above is based on the name of the form: AJ The Date Format Test v1
So the latter end of the URL would need to show: AJ%20The%20Date%20Format%20Test%20v1

Thank you!

------------------------------
JENNIFER HWANG | SE
Winshuttle North America
------------------------------

Original Message:
Sent: 10-09-2020 09:17
From: Sue Jarvis
Subject: Transition to new versions of forms

Does anyone have pointers/tips on how to transition to updated forms? There are 2 recent instances that we have had: one where I kept the form name the same, but made a small change to one of the workflow transitions to allow cancelling the form.  The other is 3 forms where there were major changes to the workflows of the forms so I changed the names and put links on the old forms to the new versions.  I can't delete the old forms as there are still some in progress that need to be completed.  I have added a link to the new form and removed the buttons on the originator views for the old forms.

In both instances, it seems that the browser--likely Chrome--has cached the old forms so users can still submit them. I've had some users successfully refresh forms, but wondering if there is a better way to handle this other than working individually with originators.

Thanks,
Sue Jarvis
Louisiana Pacific Corporation

------------------------------
Sue Jarvis | Analyst
General Motors Company (GM) | 6143296304
------------------------------

Hi Sue,

Late to the game here. 

Jennifer is correct that Foundation/Evolve will launch the newest version of the form based on either clicking on it from the webpart/process list or based on a URL that you build.

The only time I've had to clear cache in my browser was after either a new install or any patches made to the backend. 

Please let me know if you still have questions.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------

Original Message:
Sent: 10-09-2020 09:17
From: Sue Jarvis
Subject: Transition to new versions of forms

Does anyone have pointers/tips on how to transition to updated forms? There are 2 recent instances that we have had: one where I kept the form name the same, but made a small change to one of the workflow transitions to allow cancelling the form.  The other is 3 forms where there were major changes to the workflows of the forms so I changed the names and put links on the old forms to the new versions.  I can't delete the old forms as there are still some in progress that need to be completed.  I have added a link to the new form and removed the buttons on the originator views for the old forms.

In both instances, it seems that the browser--likely Chrome--has cached the old forms so users can still submit them. I've had some users successfully refresh forms, but wondering if there is a better way to handle this other than working individually with originators.

Thanks,
Sue Jarvis
Louisiana Pacific Corporation

------------------------------
Sue Jarvis | Analyst
General Motors Company (GM) | 6143296304
------------------------------

Original Message:
Sent: 12/10/2020 12:01:00 PM
From: sigrid kok
Subject: RE: Transition to new versions of forms

Hi Sue,

Late to the game here. 

Jennifer is correct that Foundation/Evolve will launch the newest version of the form based on either clicking on it from the webpart/process list or based on a URL that you build.

The only time I've had to clear cache in my browser was after either a new install or any patches made to the backend. 

Please let me know if you still have questions.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------

Original Message:
Sent: 10-09-2020 09:17
From: Sue Jarvis
Subject: Transition to new versions of forms

Does anyone have pointers/tips on how to transition to updated forms? There are 2 recent instances that we have had: one where I kept the form name the same, but made a small change to one of the workflow transitions to allow cancelling the form.  The other is 3 forms where there were major changes to the workflows of the forms so I changed the names and put links on the old forms to the new versions.  I can't delete the old forms as there are still some in progress that need to be completed.  I have added a link to the new form and removed the buttons on the originator views for the old forms.

In both instances, it seems that the browser--likely Chrome--has cached the old forms so users can still submit them. I've had some users successfully refresh forms, but wondering if there is a better way to handle this other than working individually with originators.

Thanks,
Sue Jarvis
Louisiana Pacific Corporation

------------------------------
Sue Jarvis | Analyst
General Motors Company (GM) | 6143296304
------------------------------