


NOTIFICATION(4)           File Formats            NOTIFICATION(4)



NAME
     notification - TeamWare notification file

SYNOPSIS
     Codemgr_wsdata/notification

DESCRIPTION
     The notification file is edited by users to register notifi-
     cation 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:

          bringover-from
          bringover-to
          putback-from
          putback-to
          undo
          workspace-delete
          workspace-move
          workspace-reparent
          workspace-reparent-to

     Whenever a user creates a workspace, a default  notification
     file  is  created  in the 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 teamware Workspace item
     from the Props menu.

     The following is a copy of the  default  notification  file.
     It describes the format of the file.

     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



SunOS 5.5         Last change: 01 December 1992                 1






NOTIFICATION(4)           File Formats            NOTIFICATION(4)



     #
     # 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
     #

     In the sample  notification  file  above,  the  first  entry
     causes  mail  to be sent to chip whenever a user brings over
     the files dir/foo.cc and dir/bar.cc into the workspace.  The
     second  entry causes mail to be sent to biff whenever a user
     brings over or puts back any files into the workspace.   The
     third  entry  causes  mail  to  be  sent  to  biff  when the
     workspace is moved.

SEE ALSO
     TeamWare User's Guide
     bringover(1),  def.dir.flp(1),  fileresolve(1),  putback(1),
     resolve(1),     twmerge(1),     ws_undo(1),    workspace(1),
     access_control(4), args(4), children(4), conflicts(4),  his-
     tory(4), locks(4), nametable(4), parent(4), putback.cmt(4)








SunOS 5.5         Last change: 01 December 1992                 2



