Skip to content

AyberkErdem/MyCore

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 

Repository files navigation

MyCore

Summary

Two layered(UI-API) End-to-end request process manager website created with .NET CORE ,using SQL for the database.


LOGIN


Used combined Windows&Basic authentication for system login.
Two types of users using website :
-clients that request data,reports or specialized screens
-Admins that answer those request

MAIN


For admins after login system welcomes you with main page that includes your performance graph that shows your completed requests rate for every request type compared to total requests received, the requests that you are currently responsible of , the requests that waiting for someone to take responsibility and your notifications(message,changes in your requests,request appointment etc.) For users you see the current status of your requests,the history of your completed requests and notifications.

REQUEST LISTING


A page with filters that you can use to search&find a specific request or list every request that fits your description
also implemented quickfilters using javascript so basically you post a complex filter than filter that list using quickfilters if needed.

REQUEST CREATING


A page for clients to create requests.Other than textboxes page also has drag&drop area for file uploading , dynamic dropdown-lists to select request type and category or any report that currently active if needed.

REQUEST MANAGEMENT


A page for both clients-admins to use manage the process,Includes partial view live chat created with SSE(Server Send Events) logic so the workload of the server is minimized for a live chat.
The things admins can do on the page:
Edit,take responsilibility ,cancel or complete request.
Chat with clients.
Save notes.
The things clients can do on the page:
Edit or cancel request.
Chat with person responsible with the request.

Perks

The entire system doesn't need any other comm enviroment or file share to solve the requests.
Almost completely dynamic for the potential changes in the format can be customized by the changes in database no need to alter codes
Minimized raw sql usage, no run-around codes,no exploration with url changes(form management)
High Performance :Partial views,async functions ,no js time intervals(except voking SSE for chat) and summarized listings

Disadvantages

Direct load of the shared Files:
Request Management Page loads with file uploaded to the system related to the request so the user can download it.For cases download is not neccessary or already done can be marked as no need to load file data unless requested.(Currently working on it)
HTML-CSS(responsibility and design):
Tested only for the currently active users screens at the firm no problems at there but i am not happy with the looks at the wide-screen and bad returns for pick of color

ADMIN MAIN PAGE

DESIGN

CREATING REQUEST

REQUEST MANAGEMENT PAGE(CLIENT)

Live chat created with SSE(server send events) adapted to .NET CORE and with partial view

REQUEST MANAGEMENT PAGE(ADMIN)

REQUEST LISTING

Quick filters on the top filtering list using javascript without post/get actions

DETAILED POST ACTION FILTER

About

readme only

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors