Employee

Derive the Impot classification from Married/Single/Divorced and Children

Review the Service that checks whether all fields are populated (before generating a form)

• Check this service:   CheckEmployeeDataByDocumentTemplateService.checkDataComplete(employee.id, document_template.id)
  • It is used in “index_create_forms.html.twig”
• It appears that this gives a ‘Incomplete’ even when both the Employee and Employer has all the fields populated
• Make the service popup (tooltip) with the missing field(s) to be filled in.   Hide the generate button until ‘Complete’ criteria is met

Response from Website Inquiry Contact Form process (in Payroll Project)

• As in ATS, the process of submitting an inquiring will create a new User.  Ensure that the role of that new user include ROLE_EMPLOYER
• New Employers can choose the services they want to avail themselves of
  • Monthly payroll
  • Employment contract negotiations
  • Health insurance set-up
  • Employee permits (including managing capturing and checking the data from the employees)
  • Employee admin (housing, transport, training)
  • Ski hire for the season
    • Use the Product entity to control the text for each service (including pricing)
    • Check box for each Product that each Employer wants to take up
• When a User logs in, if they are ROLE_EMPLOYER but do not have an associated Employer details set up, it will show a page designed to walk them through setting up an Employer. 
  • Employer page should include a question as to what services they would like to use. (See above)
• If an Employer has been set up, it will direct them to their own dashboard page with their Employer(s) (likely 1 but can cater for others) with the links to their various pages with some sort of summary info.
• If a a ROLE_EMPLOYEE or ROLE_USER, then design a dashboard page for an Employee
  • Access to their personal details
  • Store of permits
  • Payslips
  • General information and help
• When uploading an Employee, be sure to track Default Language

Payroll – Other tasks 

• Create a Pricing entity
  • Product (relational field)
  • # Employee and price (thoughts – single entry of multiple entries per product)?
• Create a Communications Template entity
  • Name
  • Text in EN, FR, DE etc
• When uploading a new Employee be sure to include their country so the User Default language can be set.
  • Edit the Employee upload function (New or Edit or Import) to check the employee language setting