Sharepoint 2009 Workflows initiation forms
Sharepoint 2009 workflows create xsn forms to launch respectively to add content to workflows. Is there any way to substitute this with a skybow solution?
-
Hi Raoul,
You can use Standard forms instead of the XSN to do this. I think you want to use a SharePoint 2010 workflow. Unfortunately we need to kick off an SharePoint 2013 workflow first, but in this article you dan find a workaround for that: /hc/en-us/articles/360012039940-Start-SharePoint-2010-workflow-by-using-Rich-Forms-How-to-do-this-
Hope this will help you out!
Bart
0 -
Hi raoul dobal,
if you use skybow rich forms to customize your list form, simply double click the default Save-Button or add a button with Actions to kick off a Workflow. There is one action type to start a workflow.
Watch this video at minute 2:37 and see how to add actions to the save button:
https://youtu.be/JVB-GdvSZgU?t=2m37s
Kind regards
Matthias
0 -
Sorry, 2010, of course
To be more specific. When you for create a workflow with an approval process, you have the option to edit the form, the user is sent to via a link in a notification email resp. in Outlook via the Task button in the email. For instance they can add comments or whatever you require them to fill out. That particular form is the XSN that is of concern. This form is part of the workflow. The results are stored in the task list that is assigned to this particular workflow.
When I look at the form in such a task list, I believe that these are the forms that store the info and that I would need to replace with your rich forms. So far so good.
However, these workflows are setup as reusable that are assigned to individual libraries in this site - and that includes the XSN that is deployed with the instance of the workflow. All Updates to the form are of course inherited down. A solution that "only" edits individual forms could not be practical if you have dozens of libraries with inherited workflows.
0 -
I just tested with editing the forms in the target task library. The forms do not match the ones that are sent through the workflow.
0 -
Hi raoul dobal,
since we do not use/edit this xsn forms the inheritance should not be a problem. You can use our export/import functionality to copy a form e.g. from New to Edit or from one list to another.
With SPDesigner you can create additional forms and modify them individually with Rich Forms.
If you want to use these forms in the workflow you need to point to them manually.
Regards
Matthias
0 -
Good Morning
I do not think that this applies here, since the 2010 approval workflow creates his own forms in xsn and I have not seen any way how to add different forms to it. Please let me know if you know how. Then of course it would be possible to use your solution which is by far superior.
Raoul
0
Please sign in to leave a comment.
Comments
6 comments