1.6.1.4. Editing blocks and keys
1.6.1.4.4. Additional functions in $CADEANS_DEFAULTUSER
Prev  Next
1.6.1.4.4. Additional functions in $CADEANS_DEFAULTUSER

In the directory $CADENAS_DEFAULTUSER directory has a few special features compared to the other directories with regard to the context menu commands displayed.

When selecting the category $CADENAS_DEFAULTUSER category, the same configuration files are displayed as under $CADENAS_USER. The purpose of the double listing is that, regardless of the default settings under $CADENAS_DEFAULTUSER personal settings can be set under $CADENAS_USER can be set.

[Note]Note

As long as files under $CADENAS_USER are identical to those under $CADENAS_DEFAULTUSERthey do not physically exist and are only displayed in PARTadmin (overlay ).

Files changed by the user are physically saved under $CADENAS_USER but only those keys that contain deviations from the status under $CADENAS_DEFAULTUSER are included.

See below under Context menu commands at file level.

Administratively, you can set whether the personal settings should be overwritten with the default settings (see Always overwrite command). This is not the case by default.

Executing a context menu command in $CADENAS _DEFAULTUSER leads to an action in $CADENAS _USER. The action only takes effect once it has been saved and the target application has been reopened.

In the following the context menu commands are described on key, block and file level:

  1. Context menu commands on key level:

    Select a key line and call the context menu.

    • Do not overwrite [Never overwrite] (default): Green background color

      The key value in $CADENAS_USER is not overwritten.

    • Always overwrite: Yellow background color

      The key value in $CADENAS_USER is overwritten at each restart of the application.

    • Delete: Red background color

      The key in $CADENAS_USER becomes deactivated .

    [Note]Note

    The activated option is identified by a checkmark.

  2. Context menu commands on block level:

    Select a block and call the context menu.

    • Merge

      Same blocks from $CADENAS_DEFAULTUSER and $CADENAS_USER are merged.

    • Do not merge

      Identical blocks from $CADENAS_DEFAULTUSER and $CADENAS_USER are not merged.

    • Overwrite

      Same blocks from $CADENAS_DEFAULTUSER and $CADENAS_USER are completely overwritten.

    [Note]Note

    The activated option is identified by a checkmark.

  3. Context menu commands on file level: The activated option shows a checkmark.

    Context menu commands on file level

    Context menu commands on file level

    • Use overlay (default):

      [Note]Note

      As long as files under $CADENAS_USER are identical to those under $CADENAS_DEFAULTUSERthey do not physically exist and are only displayed in PARTadmin (overlay ).

      Files changed by the user are physically saved under $CADENAS_USER but only those keys that contain deviations from the status under $CADENAS_DEFAULTUSER are included.

      The following example uses the configuration file classificationwizard.cfg to illustrate the relationships:

      1. Initial situation in PARTadmin:

        The configuration file classificationwizard.cfgis displayed under $CADENAS_USER.

        Initial situation at file level:

        The file is not displayed in the user directory because it does not differ from the same file under $DEFAULT_USER.

        [Note]Note

        In versions <= V11 SP4 all files under "User" and "Default-User" were displayed in parallel.

        classificationwizard.cfg not available at file level

        classificationwizard.cfg not available at file level

      2. The value of the System key is now changed in PARTadmin.

        -> The change is signalized by bold font.

      3. Click on Save .

        -> Bold font disappears.

      4. Now open the User directory on file level.

        -> Only now the changed config is displayed.

      5. Open the config file.

        [Note]Note

        Only changes are displayed.

        Only the changed key is contained in the configuration file

        Only the changed key is contained in the configuration file

    • Always copy [Copy always] :

      The default file replaces the "own" file in the user directory.

      In other words, the user cannot add or change anything.

    • Copy ne [Copy newer] wer :

      For changes by the administrators, the file is copied. It may then be changed by the user.

    [Note]Note

    The activated option is identified by a checkmark.

Prev Up Next
1.6.1.4.3. Editing blocks, keys and key values Home 1.6.1.4.5. Additional function with activated $CADENAS_SITESETUP