workflow-foundation

In Sharepoint designer's workflow editor I wish to retrieve the username/name of the work flow initiator (i.e. who kicked it off or triggered the workflow) - this is relatively easy to do using 3rd party products such as Nintex Workflow 2007 (where I would use something like {Common:Initiator}) - but I can't seem to find any way out of the box to do this using share point designer and MOSS 2007. Update It does not look like this rather obvious feature is supported OOTB, so I ended up writing a custom activity (as suggested by one of the answers). I have listed the activities code here for

I have a custom sharepoint workflow that I'm developing in Visual Studio. The workflow is running against a document library which has a custom content type connected to it. The content type includes a user lookup field ("owner"). I'm trying to have my workflow assign a task to the "owner" lookup field. However, I've only been able to get the display name for the user, not the account username. Can anyone help? Kusek Refer to this Article on how to get the User Details from the Field. public static SPUser GetSPUser(SPListItem item, string key) { SPFieldUser field = item.Fields[key] as

I have recently posted a question regarding the Windows Workflow running in a web application. Granted it was a fairly technical question that contained terms like ManualWorkflowSchedulerService, HandleExtrenalEvent, etc... it got about 15 views over the course of 20 days. While it is most likely a matter of me not asking the question the right way, it got me thinking about the adoption of windows workflow in real world applications, especially in web applications. Have you successfully implemented real world internet applications with WF and looking back, has the investment of your time

I am currently in the process of searching for a rules engine that works in .NET. Our logic is pretty simple, +, -, *, /, and, or, basic order of operations stuff. However we are going to need to store this information in the database and then generate the rules file when a new version is pulled from the database. So the common UI editors are going to be useless to us, unless one of them has a web version UI editor. So my question is, given what I have said, which is going to be the best rules engine for us in terms of programmatic configuration and integration with ASP.NET. My experience with

I'm starting to think that I should ditch Windows WF in favor of something simpler. I don't necessarily need to pause workflow execution for extended periods of time and restore them later. I would like a simple state machine framework that does have basic suspend / resume / abort (without serialization), however. I've downloaded the Stateless framework from Google Code and am going to start playing with it, but would love to hear what the other .NET programmers out there are using. EDIT Stateless seems really simple to implement, but I do wonder if it's the right thing for a candy machine. In

I am looking for a few books, blogs or articles on WWF. I've read the books below; however, I need resources that cover the topic in more depth. I am especially interested in local services, persistence, tracking and viewing Workflows from a website. Any suggestions?? Pro WF: Windows Workflow in .NET 3.0 Essential Windows Workflow Foundation IMHO, the best books are Essential Windows Workflow Foundation and Programming Windows Workflow Foundation: Practical WF Techniques and Examples using XAML and C# . Blogs that I read: Keith Pijanowski's Blog Kirk Allen Evans's Blog Matt Winkler Matt's

MS CRM Dynamics 4.0 incorporates the MS WF engine. The built in designer allows the creation of sequential workflows whos activities have native access to CRM entities. Is it possible to: Create a state machine workflow outside of CRM (i.e. in visual studio) and import it into CRM? Have this workflow access the CRM entities? It is NOT possible to create a state machine workflow for use in MSCRM. It is also not supported to create any workflow outside of MSCRM and import it. As a work around you could write either all the logic you need into a custom workflow activity and import that into MSCRM

I have got a Visual Studio Solution containing several projects and have set up the references between the projects as project references. When a reference to an assembly is added, the references' properties contain a setting for Specific Version = True|False This property is missing for project references. How can it be set? I'd like my solution to load any available assembly (no matter what version) in the bin folder. I've had a problem when a workflow instance (Workflow Foundation) was deserialized and the dependencies were updated meanwhile. I think the problem is that what you are asking