Troubleshooting NEOSYS Timesheets system: Difference between revisions

From NEOSYS User Support Wiki
Jump to navigationJump to search
(Created page with '=== Trouble shooting why a user isn’t getting timesheets reminder emails === # No email address? Reminders are sent to the person’s timesheet approver. If there is no approv…')
 
No edit summary
Line 1: Line 1:
=== Trouble shooting why a user isn’t getting timesheets reminder emails ===
=== Trouble shooting why a user isn’t getting timesheets reminder emails ===


# No email address? Reminders are sent to the person’s timesheet approver. If there is no approver or the approver doesn’t have a valid email then no reminder is sent.
* No email address? Reminders are sent to the person’s timesheet approver. If there is no approver or the approver doesn’t have a valid email then no reminder is sent.
# Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com. Note that, in the usual case, the NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.
* Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com. Note that, in the usual case, the NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.
# Check the user has logged in at least once in the last 31 days otherwise no emails are sent.
* Check the user has logged in at least once in the last 31 days otherwise no emails are sent.
# Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.
* Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.
# Timesheets are not sent if User is authorised to do “TIMESHEET AVOID REMINDERS”
* Timesheets are not sent if User is authorised to do “TIMESHEET AVOID REMINDERS”
# User is not authorised to do TIMESHEET ACCESS”
* User is not authorised to do "TIMESHEET ACCESS”
# User is the bottom user of a group. Create a “departmental” user below them.
* User is the bottom user of a group. Create a “departmental” user below them.
# Timesheet is before the start date specified in the Timesheet Configuration File
* Timesheet is before the start date specified in the Timesheet Configuration File
# User is a timesheet administrator
* User is a timesheet administrator

Revision as of 07:07, 26 July 2010

Trouble shooting why a user isn’t getting timesheets reminder emails

  • No email address? Reminders are sent to the person’s timesheet approver. If there is no approver or the approver doesn’t have a valid email then no reminder is sent.
  • Defective email address? Check the email address actually works by sending a normal email. Use timesheet configuration file to define the user to be emailed a summary list of emails sent during each reminder/approval run. In those summary emails sometimes you will get responses saying why emails cannot be sent. Other times the emails appear to be sent but server is then unable to deliver it for a 1001 reasons. If the server is unable to deliver an email the only way it can inform you is if there is a valid email address in the System Configuration File. Typically the email address is a valid email address since it will be something like clientname@neosys.com which usually not a valid email for neosys.com. Note that, in the usual case, the NEOSYS installation is configured to send emails via the NEOSYS smtp server at mailout.neosys.com:2500 which will only allow sender emails ending with @neosys.com.
  • Check the user has logged in at least once in the last 31 days otherwise no emails are sent.
  • Timesheets are not sent when the user is not expected to be in the office. In the User Details, check the user’s personal holidays, working weeks, employment start date and termination date. Check which “market” the user is in and check the public holidays and working week for that market in the Market File.
  • Timesheets are not sent if User is authorised to do “TIMESHEET AVOID REMINDERS”
  • User is not authorised to do "TIMESHEET ACCESS”
  • User is the bottom user of a group. Create a “departmental” user below them.
  • Timesheet is before the start date specified in the Timesheet Configuration File
  • User is a timesheet administrator