MODSYSCF - CUSTOMS OFFICE CONFIGURATION Ó UNCTAD - SITE (V1.15) 9.6 What the MODSYSCF Menu Options do Configure Office The purpose of ‘configuring an office’ is to set system options (i.e. parameters) that determine what ASYCUDA++ functions are used for that particular office. Office configurations are set on an ASYCUDA++ client computer by selecting the desired functions for that office and transferring this configuration to the server. Once the office configuration is set on the server all users who connect to that server will automatically be given this configuration. To better understand this configuration function, and to see the range of options available,   it   is   useful   to   first   read   the   next   part   of   this   Section,   System Parameters. One Office, one Server Versions of ASYCUDA++ before version 1.15 allowed only one office configuration per client/server network.   This   meant   that   each   office   had   their   own   server   installed   and   all   of   that   office’s ASYCUDA++  computers  were  connected  to  that  server.  Communications  between  offices  in  a national ASYCUDA++ network was by the passing of messages from one office server to another office server though the ASY++ gateway. See  the  technical  documentation  on   MODGTW   for  a  full  explanation  of  the function of the ASYCUDA communications gateway, the ASY++ Gate. Multiple Offices, one Server ASYCUDA++,  from  release  1.15a,  allows  for  multiple  offices  or  several  system  configurations  on the same server. This means that offices, with different office codes and functional configurations or needs, can run from the one central server. As many offices can be defined as are required. The configuration for each office is created and stored on the server. To Configure an Office To set an office configuration, select the menu option  ‘Configure Office’ and  ‘Login’ to the server. A window is displayed with the current office code and a field where you can enter the office code to which you want to change. The client sends a message to the server when you change the office code and press  ‘OK’. This message checks if a configuration has already been created for this office. If a configuration for this office already exists on the server, the server transfers and automatically configures the Client PC for this office. Although   the   server   saves   a   file   named   for   each   office   configuration,   once transferred to the client the name of the file on the client remains sys.cnf. If a configuration for the office is not on the server, a new office configuration, the Client PC keeps the configuration of the previous office, but the office code is the new one. (This feature allows you to define, by default, the same configuration for all the offices).