workflow

I am responsible for a team of developers who will are about to start development of a light weight insurance claims system. The system involves a lot of manual tasks and business workflows and we are looking at using Windows Workflow (.NET 4.0). An example of the business domain is as follows: A policy holder calls the contact centre to lodge a claim. This “event” fires two sub tasks which are manually actioned in parallel and may take a lengthy time to complete; Check customer for fraud – A manual process whereby an operator calls various credit companies to check and assess the potential of

Sight is one of the senses most programmers take for granted. Most programmers would spend hours looking at a computer monitor (especially during times when they are in the zone ), but I know there are blind programmers (such as T.V. Raman who currently works for Google). If you were a blind person (or slowly becoming blind), how would you set up your development environment to assist you in programming? (One suggestion per answer please. The purpose of this question is to bring the good ideas to the top. In addition, screen readers can read the good ideas earlier.) Jared I am a totally blind

This has been bothering me since I started working with this webapp last year (I had no experience with web development) I don't know if this app is structured incorrectly or if this is just the way it is . My welcome page is really a login page, and after the user logs in my app goes to a main page, where they have a menu to go to various other functions. This is struts.xml : <action name="Welcome"> <interceptor-ref name="newStack" /> <result name="success">Login.jsp</result> </action> <action name="actLogin" class="actionLogin"> <interceptor-ref name="newStack" /> <result name="success"

Folks, I'm building a pretty standard workflow that I want exposed via a WCF endpoint - I'm using the "WCF Service Application" project template and I've got a .xamlx service. This is a very simple document interchange workflow service - I want consumers to POST me a blob of XML as the body of an HTTP post (with HTTP headers containing authentication tokens). In response, these consumers will get a blob of XML containing the reply. 2 goals for me using REST/POX here are the document/message-based nature of the interaction AND I want to make client development easy for non-.NET environments

I have a closed source project that is built on my open source framework. I want to know how I should structure my workflow. Below is my best guess using git with submodules. I create a public framework repo on github with submodules that are separate git repos. I purchase a "micro" account on github ($7) so I can have a private repo. I create a private repo and clone the public framework repo. From here I can make changes to: My private code and push to my private repo on github The public framework code and push to my private github repo and then send a pull request from the public framework

I have a web app under source control in git. I have different css files for different customers as well as images and other theme specific things. And also custom reports... Beside the theme things every other aspect of the app stays the same. What would be a recommended way to keep the app as well as the theme information under source control in git. Should I use branches for the theme and the reports or submodules... During development I would like to like my customers theme to to my dev branch and do changes that I commit to my customer specific theme... Is something like the possible with