Re: Ideas or direction needed for approval path

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Note to self, don't work for this company.

Sounds like an internal application -- I'd go with a Windows Form app and
clickonce deployment via companies internal web site. You'll be able to
produce the app a lot faster via Windows Form and you will have much more
user interface flexibility -- the only requirement is that everyone on the
network have Windows OS.

Definitely a state model with parent/child relationships.

"Charles" <Charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5249AB38-1BAA-475B-9506-FC02C365E239@xxxxxxxxxxxxxxxx
I have this .NET web project that I will need to create web forms that will
allow employees to request personnel actions (for example, request for
vacation time). Depending on what department the employee is in
determines
who approvals the vacation time and what paths it follows to get approved.
It could go up to three levels before the vacation time is finally
approved.

I guess my problem is that I do not really know where to start with this
or
what I should be looking at to get a solution. I am looking for ideas,
web
sites, or anything that could get me going in the right direction. I have
looked at the design pattern called Chain of Responsibility, but I think
this
is not going to work for me. I have also looked at controlling this all
in a
database giving each request an ID number related to a person to approve
ID
number. I need this stuff to be scalable.

This is the process that an employee would go through to get vacation time
approved. The employee would log in to a web site and click on a menu
that
would display a web form that would ask them about the dates they need to
take off. The employee would then click on a "submit" button.

After the employee clicks on the "submit" button the request will then go
to
their supervisor (the supervisor will be notified by e-mail about this
request). The supervisor will then log in to the same web site that the
employee did and will be able to see this request. The supervisor will be
able to approve or reject the request. If the request is approved the
request will go to the supervisor's supervisor for approval. If rejected
the
request will go back to the employee with a reason why it was rejected.

After the last supervisor has approved the request, the request will be
sent
back to the employee, telling the employee that their request has been
accepted.

Thanks for any help,
Charles



.

Relevant Pages

  • Re: Ideas or direction needed for approval path
    ... it would be a "state machine" (basically you have a ... This is the process that an employee would go through to get vacation time ... After the employee clicks on the "submit" button the request will then go ... The supervisor will then log in to the same web site that the ...
    (microsoft.public.dotnet.general)
  • Re: Ideas or direction needed for approval path
    ... is the organizational hierarchy of your organization currently stored? ... assuming that each person only has to pass their request to one person ... This is the process that an employee would go through to get vacation time ... their supervisor (the supervisor will be notified by e-mail about this ...
    (microsoft.public.dotnet.general)
  • Re: Risk of Redirecting Email.
    ... I have seen on some clients of mine, that when an employee leaves the ... they request IT to redirect their emails to a particular ... there would be nothing keeping the former employee from sending ...
    (Pen-Test)
  • Re: Missing Fields from report
    ... then created a form based upon the Request table. ... the requesting Employee table are Employee, Extension, Department. ... in my Request table nor in any reports I generate listing the requests. ...
    (microsoft.public.access.reports)
  • RE: MSACCESS - SUB FORM
    ... up to track documents and relate them to employees who I assume are ... - EXIT RE-ENTRY REQUEST ... more suggestive names for your tables wouldn't hurt, for example "Employee" ... > how can I design this four different windows to get once I press each button. ...
    (microsoft.public.access.tablesdbdesign)