InfoPath Forms with managed code with Workflows

InfoPath Forms with managed code with Workflows

• yazoox

  Thanks for your help. After looking through the logs I realized I had to add the form dll to the FEATURES folder. Adding this line to the Install.bat file fixed the problem:

  xcopy /s /Y <full path>\myEditTask.dll "%programfiles%\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\My Workflow\"

  -Cynthia

  
  

• Soumya B

  Thanks for the reply. I have an IP form that I am using as my EditTask form. It has a button that, when clicked, executes code to open a new document from a specific template in a specific document library on Sharepoint. I granted the form full trust and signed it with a certificate issued by our certifcate server. I publish the form to the host environment (the workflow) and then deploy the workflow. I also added the form's assembly to the GAC. The workflow will start, but when I try to edit the task, the form won't open (or opens and closes v. quickly - the screen flickers) and I get the message "The form has been closed"

  -Cynthia

  
  

• The_Nod

  Can you provide details on the error message
  
  One thing to consider is that your form MUST have full trust and be digitally signed with a trusted certificate. You can grant yourself a temporary certificate for development purposes if need be from within infopaths forms settings.
  
  
  

• The Markus

  Were you able to figure this out I'm trying to do the same thing and am having the same problem. Thanks,

  Cynthia

  
  

• Alex-MyRpg

  I have found a number of things cause this, I struggled for a day or two trying to figure out how to properly deploy a workflow. First, go into your sharepoint central administration. Under application management you should see manage form templates. Check there to see if it lists your form as ready and workflow enabled.
  
  If it's not listsed, most likely you have a problem with your install.bat, workflow.xml or feature.xml file. Workflow forms must be registered at the time the feature is installed. make sure you edit the script and uncomment these lines and edit as needed:
  
  xcopy /s /Y *.xsn "%programfiles%\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\featurename\"
  
  stsadm -o deactivatefeature -filename featurename\feature.xml -url http://localhost
  stsadm -o uninstallfeature -filename featurename\feature.xmlstsadm -o deactivatefeature -filename featurename\feature.xml -url http://localhost
  stsadm -o uninstallfeature -filename featurename\feature.xml
  
  The are needed to copy the .xsn file to the appropriate directory and properly re-register the feature. Also, you need to edit the feature.xml file. Make sure it has the following elements, specifically, the RegisterForms line:
  
  <Properties>
  <Property Key="GloballyAvailable" Value="true" />
  <Property Key="RegisterForms" Value="*.xsn" />
  </Properties>
  
  Also, when you have your form prepared, you need to publish it to a network location. Publish to the same location as your install.bat, workflow.xml and feature.xml files. When asked for an access path during the publish process, make sure to clear the line.
  
  You should also check out the sharepoint logfiles, which can be found in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS. Look for "Workflow Infrastructure" to find your error message.
  
  Hope this helps. I wish the documentation on this was better. I had to piece it together from various blogs.
  
  
  
• InfoPath Forms with managed code with Workflows