Two Tidbits By Request
In follow-up to my previous post regarding the ability to set custom status column fields for Sharepoint workflows, I've been asked about the inability to drop the "SetState" activity onto a Sequential Workflow in Visual Studio. Most likely, if you are having the problem that you can't drag and drop the SetState activity onto your workflow canvas, you are selecting the wrong SetState activity. It is confusing because there are two SetState activities. One belongs to the Windows Workflow Foundation. This SetState is for changing the physical state of a State Machine workflow. The other SetState belongs to the Sharepoint Workflow activities and it sets the "state" which is really the status (ie., "In Progress" or "Completed" or, better yet, "Failed To Start") column text for a Sharepoint Workflow.
-------------------------
By client request, I'm adding a little blurb on CSS for Sharepoint 2007 design. I handed off the master page and custom stylesheet to my client but I had left the global links buttons with a darker font than they wanted. They couldn't get the font to change appropriately to white no matter how many times they changed ms-globallinks. This is because it isn't ms-globallinks :)
.ms-HoverCellInActive a, .ms-SpLinkButtonInActive a{
color: #FFFFFF !important;
}
