

Known Issues

User Access
- Important:
Two supervisors should avoid working on
a repository at the same time. If this happens the operations of one
supervisor may overwrite the operations of the other; however, if these
supervisors have a strong knowledge of the repository structure multiple
edits shouldn't over-write or conflict with each other.
Upgrading a Repository
- When you upgrade a repository from version 4.x to 5.x, you may encounter problems with some user restrictions that have been set in Supervisor. You must reset these restrictions in the upgraded universe.
Monitoring Broadcast Agent
- Adding Broadcast Agents into the Broadcast Agent Manager:
When using the Administration tool you may add Broadcast Agent Servers to be monitored within the
Broadcast Agent Manager module. When you click on "Monitor one more Broadcast
Agent" you may provide a username with a supervisor profile. This allows you to monitor the Broadcast
Agent(s) of your group. However, if your group contains subgroups you cannot monitor the Broadcast
Agent(s) for the subgroups, even if you created them.
Workaround : Copy the supervisor into the all of the subgroups.
Import Users
- This feature allows any Supervisor to quickly
import user and group definitions from a text file, modifying or even deleting
existing ones. Because this information is so sensitive, you must be careful
to use it in the proper way, ensuring that unintentional duplications or overwrites
do not occur. To limit access to this feature, the General Supervisor can
switch the "Import Users" security command off for the whole company
(by disabling it at the root level). This way, only General Supervisors will
be able to use it by default and it can still be enabled specifically
for selected Supervisors.
- In an import file for batch creation or modification
of users and groups and their properties, you might change the name of a user
or group. If you refer to the new name of the user or group in another command
later in the same import file, it will not work, because the file is read
before any changes are made, and the name will therefore not yet have changed;
it will not be recognized and an error message will appear. However, you can
still use the old user name to manipulate the user. We recommend that
you run a separate import file to rename users and groups after other modifications
to your user/group configuration.
Print
- When printing information on
your repository configuration by means of the Print command on the File menu,
results can be inaccurate if a user has multiple instances with different
rights to the same universe. The printed result depends on the order of instances
shown in the list in the Groups and Profiles tab of the User Properties dialog
box:
- If the instance at the top of the list has access to the universe, the printed
results will indicate that the user has access to the universe
- If the instance at the top of the list does not have access to the universe,
the printed results will not indicate that the user has access to the universe
This is true of all options of the Print command, including Print in Table
Format.
Print Resources by User/Group Definition
- When printing information on
the resources in your repository by means of the Print command on the File
menu with the Resources by User/Group Definition option, extra blank lines
are printed when the Applications customization option is selected.
Print in Table Format
- When printing information on
your repository configuration in table format by means of the Print command
on the File menu with the Print in Table Format option, the operation can
be very lengthy and consume a very high proportion of memory resources if
your repository configuration is highly complex (for example, if there are
very many groups, subgroups, and multiple instances).
Document domain deletion
- When as General Supervisor you delete a document
domain using the Repository Management dialog box (called by choosing the
Repository command on the Tools menu), the deletion may be incomplete. After
deleting the document domain, open the Repository Management dialog box again
and click Scan to run a Scan and Repair of the repository to complete the
deletion cleanly.
