In part one, we covered the new Audit Log and Document Value Locking functionality, as well as quick mention of the improved Reporting Structures module. In part two, we look at the new object centric functionality.
Object Ownership Changes
CostMANAGER 2.7 gave us an opportunity to take a close look at how we handle ownership and sharing for objects such as input screens, reports and filters. Previous versions used a concept of ‘shared’ and ‘personal’ objects. This allowed users to have their own, private versions of reports, or create filters that only they could see. This lead to problems, however, where database administrators couldn’t be sure of exactly who owned which objects. Additionally, if a user who created key reports and input screens was deleted, the objects they created would also be removed. We have rectified these problems by improving the object ownership system.
In CostMANAGER 2.7 and beyond, all objects are now owned by the database itself. Individual user access is by way of explicit sharing. With this approach, users can still create their own ‘personal’ objects that only they have access to, but these can now be shared or transferred to other users later if desired. Most importantly this change allows administrators keep better control over the database objects. To assist with these changes, we created three new modules.
The first screen is the Object List. This screen is an overview of all of the objects in the database. It also has the ability to set high level permissions against each. From here, you can see how many users have access to each object. If an object has zero users, this indicates that the object is possibly redundant and might be suitable for deletion.
The Object Permission screen allows administrators to glance at the objects to see who has access to them. This can be a valuable tool when a user can’t figure out why they can’t access a particular report, for example. As with all standard KCM grid screens, the information can be sorted and grouped to find specific information quickly.
Finally, we have the Object Dependencies screen. Feedback from our users told us that finding out which objects were dependent on each other was difficult. This module was created to address the problem. We feel that it will significantly improve this process, and allow end users find out why they’re unable to delete particular objects.
In previous versions of CostMANAGER, if you try to delete an object that it being used by another object (for example a report function on a tabular report) the user would need to track down every place that the object is used and ‘unlink’ it. This was too complex and needed streamlining. Therefore the Object Dependencies screen was built.
The module shows every occurrence of each object in the database. You can also see whether or not a particular object is redundant and can be deleted. We feel that this feature will dramatically improve object management in KCM.
Kildrummy® CostMANAGER 2.7 brings huge advances in functionality over previous versions of CostMANAGER. If you wish to upgrade your Enterprise or Express installation contact Kildrummy Technical Support and we’d love to help assist you through the process.