Introduction
Getting Started
Main Menu
|
The webTA application uses the term ‘task’ to refer
to messages sent to system users to prompt for action. Tasks
can either be sent from the system itself, or be sent by the
system on behalf of an employee, such as when a employee
selects the
Add Timekeeper Task option.
webTA has two mechanisms for task delivery. The first, known as
internal task delivery, consists of webTA populating a table
with the employee’s tasks. The employee can periodically
check their task
list to view and clear tasks.
The second mechanism is email delivery to the webTA user.
Under this system, webTA looks up the employee’s email
address from the employee’s locator information, and
attempts to deliver an email to that address containing the
details of the task.
If webTA is unable to send the email, for example if there is no
address in the locator information or the email server is unavailable,
then webTA will repost the task using the internal task delivery
mechanism.
Note that webTA sends
mail from the database server, not from the application server.
Please verify that there is connectivity between the database server
and the SMTP server if configuring email options.
This screen allows you to select from the above two delivery mechanisms,
as well as to configure other important mail configuration settings.
- Mail server hostname This is the location of
the SMTP server webTA should deliver mail to. This can be either
a dotted quad IP address, or a DNS hostname.
- Mail server port This is the port number that
the mail server is listening to for SMTP connections. You can
usually leave this at its default value of 25.
- Address to use in email From: field This
is the address that will appear in the From: line of the email,
and must be of the form addressee@host. Please note that
return email will go to this address. In particular, if the
SMTP server determines that a particular email is
undeliverable, the SMTP server will normally send a bounce
message to this address to inform you of the problem.
- Message body header This field can be used
to define an opening header to the message sent with the task.
- Message body footer This field can be used to
define a closing footer to the message that is sent with the
task. For example, you might have a standard footer directing the
recipient to contact your trouble desk if they are having problems.
- BiDirectional NFC Email This is the email address
to which BiDirectional notifications for NFC will be sent.
- BiDirectional Kronos Email This is the email address
to which BiDirectional notifications for Kronos will be sent.
- BiDirectional Agency Email This is the email address
to which BiDirectional notifications for the Agency will be sent.
When finished, click Save to store the settings, or
Cancel to return to the previous menu without saving
changed settings. The Test button allows you to send
a test email with the current configuration; the test email will be sent
to the email address specified in the Address to use in email From:
input field. A pop-up message will indicate whether the test was
successful or not.
|
