The SPWorkflowTask.AlterTask() method is handy dandy. It allows us to alter task details from outside of the workflow itself. I was using it in a couple of custom task forms I had created to update the task based on some user input. It's pretty simple. You get a reference to the active workflow task item, create a hashtable that you populate with the data you want to change, then use AlterTask() to update the task.
This is pretty much exactly what I was doing, except I threw in an item.Update() after my SPWorkflowTask.AlterTask() call for good measure. I wasn't sure if the AlterTask() actually did an Update() internally so I figured it couldn't possibly hurt, right?
I'm working on a project where I need to create some custom task forms for a workflow. I've been looking into a few different ways of doing it and I ended up deciding on using custom aspx pages to do the job. I figured I should share how to do it although it's not all that hard.
But hang on... Why aspx pages? Why not InfoPath? You'd think using InfoPath would be a no-brainer, considering creating custom forms is it's entire purpose in life.
We recently put a rather complex SharePoint workflow into production. Our workflow is creates a lot of tasks, and each time a task is created a custom email is sent to that user with a link to the task. We create the body of this email ourselves, including the link to the task. The user clicks on the link and the task opens up in Internet Explorer and they can do whatever they need to do. We always want the forms to open in the browser and to begin with everything was peachy.
However after a few pilot users had been upgraded to Office 2010, which included the InfoPath client, it came to our attention that when they clicked on the link in the email it would open it up in the InfoPath client rather than opening it up in the browser. We would want the experience to be consistent so obviously this was not desirable.
Yesterday I was helping a colleague of mine setting up her SharePoint 2007 virtual machine, and at one point she needed to make some changes in Central Administration. Problem was, when she clicked the "OK" (or "Cancel") buttons after having put in her new settings nothing happened. No page load, no error, no nothing.
How to set the content type of a new file in a document library, when uploading said file through code (aka longest and most convoluted blog title to date)
I'm on a project that's very close to being implemented in production. For the final go-live we will be uploading a bunch of files (about 700) into a document library. There are two content types in our document library, SPI Documents and SPI Drawings. Uploading the files directly into the document library will pick the default content type. How do we change it to use the second content type, instead of the default, for some of the files?