PENGIN PI! A CRM with the back bone of a feature light ERP system. Utilitarian in design, easy to extend, customize, and deploy. Made by a community, supported by Tobu Pengin.
These view templates need to be rendered for the hiring and admin role only. The applicants link should be in our tools menu in the main navbar.
Applicants:
The main view should list all applicants similarly to how we render threads in our forums. If there are no applicants, the main view should say, "there are currently no applicants". The table should list name, position applied to, and application date.
Applicant:
The applicant view should render all of our content in the ORM, including rendering a PDF thumbnail image of the pdf/doc files for the resume and cover letter. Don't worry about rendering the PDF thumbnail of the actual file. Just use a generic placeholder file stored in app/static/images
Clicking on the file image should use the file path API to allow the hiring manager to download the file from our storage platform using the path keys in our database. The rest of the form should simply render text labels of the data from the application orm.
SCOPE CREEP: Upon thinking about this, I do want to add one more feature to the applicant view. We need to be able to delete them for now. You can borrow the delete code from the products section when we delete a product. If an applicant is not a fit or declines to respond, I'd like to have a mechanism to remove them from the system for now. Later on, we will permanently keep everyone, but right now, we need some basic housekeeping to keep costs down.
NOTE: This application view will have more features added later. For now, we just need to create the view and render the information.
These view templates need to be rendered for the hiring and admin role only. The applicants link should be in our tools menu in the main navbar. Applicants: The main view should list all applicants similarly to how we render threads in our forums. If there are no applicants, the main view should say, "there are currently no applicants". The table should list name, position applied to, and application date.
Applicant: The applicant view should render all of our content in the ORM, including rendering a PDF thumbnail image of the pdf/doc files for the resume and cover letter. Don't worry about rendering the PDF thumbnail of the actual file. Just use a generic placeholder file stored in app/static/images
Clicking on the file image should use the file path API to allow the hiring manager to download the file from our storage platform using the path keys in our database. The rest of the form should simply render text labels of the data from the application orm.
SCOPE CREEP: Upon thinking about this, I do want to add one more feature to the applicant view. We need to be able to delete them for now. You can borrow the delete code from the products section when we delete a product. If an applicant is not a fit or declines to respond, I'd like to have a mechanism to remove them from the system for now. Later on, we will permanently keep everyone, but right now, we need some basic housekeeping to keep costs down.
NOTE: This application view will have more features added later. For now, we just need to create the view and render the information.