I’m new to InfoPath 2003 and am trying to implement it using a workflow (our first one) in SharePoint 2007. I inherited the InfoPath form with 2 views (data entry and a report). I’ve already had to delve into the XML components to fix some validation issues, etc.
Currently, I have several problems, and though I’ve read a number of messages on this forum, I’m not sure where to start first.
I published the form to a form library in SharePoint. I followed some directions given to me, that removed the “save” option from the form and replaced it with a “submit” option. To insure unique filenames, I used the “now” with the concat() function in the filename in the “main submit” [data connections]. After publishing to SP, I created an Approval Workflow. The approvers are defined using distribution groups in Active Directory.
Question 1 - How do I ensure a unique filename for new forms, yet, retain the filename as it proceeds through the workflow? Everytime, someone edits the form and saves it with the submit button, a new workflow is started. I understand why, but I don’t know how to create a “save” button, that retains the original unique filename.
Question 2 – As the form proceeds through the Approval Workflow, anyone can make changes to the workflow. For example, in a 5 step process, while my form is at step 4, user 1, 2, and 3 can still make any change to the document. If user 1 changed it, while at step 4, user 2 doesn’t know it’s been changed. Moreover, once the workflow is done (100% and approved), anyone can modify the document. It appears that InfoPath and Workflow work independently of one another. How do I remedy this?
Do I need to create additional views for each type of reviewer group and programmatically change the view, depending on where the form is in the approval process? And, once the form has reached the 100% done stage in Workflow, change it to readonly?
Thanks, Bill