Destiny One is the first Registration Software I've administered and supported. I found it relatively easy to learn and use. It was named OneCE when I started working with it and the help files weren't easy to understand. The help files have improved exponentially, and there is very little we can't find out for ourselves without having to turn to the Destiny One support team for assistance.
When we began to implement Multi-Program Office for other departments in the University the functionality seemed to be being created on the fly while we were preparing to implement. This meant that we had no experience with the new functionality, nor enough opportunity to test it in our test instance prior to implementation to production.
One big flaw with Multi-Program use is that we aren't able to lock down functionality to Program Office for users which means administration personnel need to perform the manual entry for department heads by request to ensure they don't accidentally make changes to other Program Offices settings. For example: Workflow assignments, Enrolment Restrictions, Tuition profiles, etc.
Setting up Workflow assignments and making changes is a long and arduous process as with each change, you're taken to the top of the screen and must scroll back down to where you were to add or remove an additional person. I estimate approximately 30 minutes of work for each Costing Unit. We have approximately 200 Costing Units and more to come as more faculties come on board.
We also do not have the ability to print out or view the entire Configuration Map of our existing Configuration settings.
Where reporting is concerned, we feel the developers don't really have a handle on what the requirements are to run programs or conferences. Perhaps to gather requirements, they should interview the faculties who are running these types of programs to ascertain needs.