Last post Dec 11, 2009 05:59 AM by eshivakant
Aug 27, 2009 04:49 PM|niravparekh|LINK
Hi, I am new to .net 3.0 workflow programming.
But I want to know one thing if this is suitable for my application. I am just describing my requirements in very brief. I will appreciate if someone can tell me if I can use WPF for this project and if yes, Please just tell me steps because I never used
ok, Here my brief requirements.
I need to develop an intranet web application using Windows Authentication so that my users can enter Purchase Requests. Once logged in, there will be a webform with textbox, dropdown and so many other stuffs, also there should be file attachments.
Once user filles out this form, and attach files if any, and submit this, this should go to his manager automatically for approval. Manager should be able to view the details and should be able to approve. If he approves, it goes to his upper level manager,
this hierarchy is already defined. Once finished, it goes finally to Finance department.
Now I want to know is this kind of application possible through workflow? I mean will be beneficiail if I use workflow or better to develop using my own logic?
Thanks in advance
Aug 28, 2009 02:53 AM|shabirhakim1|LINK
Better is one's own path,rather than well made by others.
i just want make you clear about what you are going to do if it is workflow.true bit change you want in your logic from your previous experience like
as per you,application is just about purchasing some thing and should pass through different levels and at last should get approved or rejected by last state[finanace in ur case].Right?
Now just make it simple,create below listed tables[agian depends on your requirement)
ID int Unchecked
InstanceID int Checked
ReasonForVendorSelection varchar(3000) Checked
Status int Checked
TextValue ntext Checked
IsCancelled int Checked
IsAmendment int Checked
ReasonForAmendment varchar(1500) Checked
TextValueForAmendment ntext Checked
NameoftheProduct varchar(1500) Checked
NameoftheProductForAmendment varchar(1500) Checked
InstanceID int Checked
CreatedDate datetime Checked
Yourref varchar(200) Checked
VID int Checked
Amountsinwords varchar(200) Checked
Total float Checked
PaymentTerms varchar(200) Checked
TaxesandDuties varchar(200) Checked
DeliveryTime varchar(200) Checked
DeliveryMode varchar(200) Checked
WarrantyTerms varchar(200) Checked
DeliveryTerms varchar(200) Checked
Others ntext Checked
Comments varchar(1500) Checked
PurchaseOrderNo varchar(50) Checked
CurrencyType varchar(50) Checked
InstallationTime varchar(500) Checked
Note :create status field in purchase table
2.Comment field also for the level who are involved in this process
Create Purchase order form with all required fields and comment fields in invisible mode,because we don't need to show in the first purchase form
Remember: every person involved in this process is treated as state like Reueststate,ManagerApproval,FinanceApproval[or reject],so you can mantain one seperate table for each state.
Just on anybodies approval or rejection,you can update table..
i don't know how many application you have to develop,if this is the only application then you can make it with your own logic plus what ever i explained or if you have more workflows then better go for workflow
if you will go through workflow concept,then you don't need to define or take care of state ,transactions...
Dec 11, 2009 05:59 AM|eshivakant|LINK
WWF will work beautifully in this scenario. Little care should be taken. Do not load a workflow too much. Keep things out of it which can be kept out.
It is amazing thing. You can code any workflow with this.