Workflow Tracking Blazor WebApp asap
Budget: ₹1,500 – ₹12,500 INR
The main goal is to create a reliable and efficient web application tailored for workflow tracking. This tool will play a crucial role in helping businesses and teams manage their operations more effectively, making it easier to organize tasks, monitor progress, and achieve better outcomes.
I am looking forward to collaborating with a dedicated .NET Core developer who shares my passion for making workflow management simpler and more accessible. Together, we can develop a powerful tool that meets the diverse needs of modern businesses and teams.
Work Flow Tracking System
Brief History
• Work comes in with attachments as PDF
• Attachments are downloaded and assigned package numbers corresponding to the subject
• Documents are reviewed and comments are added in the JOB
• Code status ABC are assigned. Time spent is also assigned
• Notification sent out to admin and manager for each review completed
• Invoice is then generated.
USER ROLES –
Client – client is a out of the company user who will create and upload packages into the system which will be reviewed by the employees. He can create new packages and see his own previously uploaded packages.
Admin – Admin is the user of the application who will access to the whole application, each and every feature.
Manager - Admin is the user of the application who will access to the most of the application, there are some features which are not available to manager other than Admin – ( will let you know later). Once the reviewer has reviewed the documents and submitted the package as complete. Manager will approve the package as complete, email will be sent out to the Client notifying that the package has been completed.
Reviewer – Reviwer will only have access to the master page to see all the packages in the system which are under progress or open. All the completed packages will be accessible through a list. He will download the documents linked to the package and Review the package through action button on masterpage. He will review the document by filling out a form which will be made by us. I will explain more functionality of the review form later. Reviewer only has access to MASTER PAGE, REVIEW FORM, ALL COMPLETED PACKAGES. HIS PROFILE.
Expectations
Login Page
• Client and Employee authentication, user selects role and goes to respective page after logging in.
• Client is forwarded to Previous Packages Page
• Employee is forwarded to MasterPage
Client input page – Accessible to client and Admin only.
• Type of request selected
• Multiple file upload page with up to 2GB capability
• Client will give the package number
• Use the file name, DO NOT RENAME RATHER REMOVE THE EXTENSION
• Set priority WITH a possibility of priority override i.e 12345
• Set the deadline or due date
• Capture the date submitted & validate upon submission
• Follow up package number
Previous Packages Page – Accessible to authorised client only
• Show all the previous packages to client logged in.
• He can access only his own uploaded packaged and change the priority and due date.
• On right corner add button to Create package which will go to Client Input Page
Master Page
Shows the client’s name
I am looking forward to collaborating with a dedicated .NET Core developer who shares my passion for making workflow management simpler and more accessible. Together, we can develop a powerful tool that meets the diverse needs of modern businesses and teams.
Work Flow Tracking System
Brief History
• Work comes in with attachments as PDF
• Attachments are downloaded and assigned package numbers corresponding to the subject
• Documents are reviewed and comments are added in the JOB
• Code status ABC are assigned. Time spent is also assigned
• Notification sent out to admin and manager for each review completed
• Invoice is then generated.
USER ROLES –
Client – client is a out of the company user who will create and upload packages into the system which will be reviewed by the employees. He can create new packages and see his own previously uploaded packages.
Admin – Admin is the user of the application who will access to the whole application, each and every feature.
Manager - Admin is the user of the application who will access to the most of the application, there are some features which are not available to manager other than Admin – ( will let you know later). Once the reviewer has reviewed the documents and submitted the package as complete. Manager will approve the package as complete, email will be sent out to the Client notifying that the package has been completed.
Reviewer – Reviwer will only have access to the master page to see all the packages in the system which are under progress or open. All the completed packages will be accessible through a list. He will download the documents linked to the package and Review the package through action button on masterpage. He will review the document by filling out a form which will be made by us. I will explain more functionality of the review form later. Reviewer only has access to MASTER PAGE, REVIEW FORM, ALL COMPLETED PACKAGES. HIS PROFILE.
Expectations
Login Page
• Client and Employee authentication, user selects role and goes to respective page after logging in.
• Client is forwarded to Previous Packages Page
• Employee is forwarded to MasterPage
Client input page – Accessible to client and Admin only.
• Type of request selected
• Multiple file upload page with up to 2GB capability
• Client will give the package number
• Use the file name, DO NOT RENAME RATHER REMOVE THE EXTENSION
• Set priority WITH a possibility of priority override i.e 12345
• Set the deadline or due date
• Capture the date submitted & validate upon submission
• Follow up package number
Previous Packages Page – Accessible to authorised client only
• Show all the previous packages to client logged in.
• He can access only his own uploaded packaged and change the priority and due date.
• On right corner add button to Create package which will go to Client Input Page
Master Page
Shows the client’s name