."
." Copyright (c) 1991 by Sun Microsystems, Inc.
."
."  @(#)notification.4       1.4     92/04/24 SMI
."
.TH NOTIFICATION 4 "01 December 1992"
.SH NAME
notification \- TeamWare notification file
.SH SYNOPSIS
.B Codemgr_wsdata/notification
.LP
.SH DESCRIPTION
The \fBnotification\fP file is edited by users to register notification requests. TeamWare was formerly known as CodeManager. 
The notification facility permits TeamWare commands to detect TeamWare events that
involve a workspace and to send electronic mail in response to the event.  The
following are the events that can be registered:
.IP
bringover-from
.sp 0
bringover-to
.sp 0
putback-from
.sp 0
putback-to
.sp 0
undo
.sp 0
workspace-delete
.sp 0
workspace-move
.sp 0
workspace-reparent
.sp 0
workspace-reparent-to
.LP
Whenever a user creates a workspace, a default notification file is created in
the
.B Codemgr_wsdata
metadata directory.  The default file consists of a large comment that
describes the format of the file (the "#" character at the beginning of a line
delimits a comment).  Users can edit this file directly, or modify it  using
the 
.B teamware 
Workspace item from the Props menu.
.LP
The following is a copy of the default notification file.  It describes the
format of the file.
.sp
.nf
VERSION 1
#
# A workspace's notification file.
#
# Note: Because this file is edited manually, you may
#       want to maintain it using SCCS.
#
# The format for each entry is:
#
#       email_address event ...
#       BEGIN
#       file1
#       dir
#       .
#       .
#       .
#       END
#
# where <email_address> is the address to which the mail will be sent;
# <event> is one of the following:
#       bringover-from
#       bringover-to
#       putback-from
#       putback-to
#       undo
#       workspace-delete
#       workspace-move
#       workspace-reparent
#       workspace-reparent-to
#
# The bringover, putback, and undo events can include a list of files and
# directories to be associated with the event.  When a directory is listed,
# all files hierarchically beneath it are registered.  The list must be
# delimited by BEGIN and END statements.  To get registration for all files
# in the workspace, use a list of ".", an empty list, or no list.
#
# The following is a sample notification file:
#
#       chip@mach1 bringover-to
#       BEGIN
#       dir/foo.cc
#       dir/bar.cc
#       END
#       biff@mach2 bringover-to putback-to
#       BEGIN
#       .
#       END
#       biff@mach2 workspace-move
#
.fi
.LP
In the sample notification file above, the first entry causes mail to be sent
to 
.B chip 
whenever a user brings over
the files
.B dir/foo.cc and 
.B dir/bar.cc 
into the workspace.  The second entry causes mail to be sent to 
.B biff
whenever a user brings over or puts back 
.I any 
files into the workspace.  The third entry causes mail to be sent to
.B biff 
when the workspace is moved.
.LP
.in -5
.SH "SEE ALSO"
.I TeamWare User's Guide
.sp 0
.BR bringover (1),
.BR def.dir.flp (1),
.BR fileresolve (1),
.BR putback (1),
.BR resolve (1),
.BR twmerge (1),
.BR ws_undo (1),
.BR workspace (1),
.BR access_control (4),
.BR args (4),
.BR children (4),
.BR conflicts (4),
.BR history (4),
.BR locks (4),
.BR nametable (4),
.BR parent (4),
.BR putback.cmt (4)