At least Informatica has version control.
Hyperion has none and as far as I know there is no good way to use external source control. You can have versions of an object, so you can rollback changes, but there is no check-in/check-out.
I don't want a platform to have its own version control. That is your configuration management/release engineering team's responsibility. The dept should have a repository of record, almost always a formal source control application, that handles version control of all application artifacts across the board. When you have one or two rogue platforms actually
requiring their own version control system is makes them nearly impossible to keep proper software lifecycle consistency on those platforms relative to everything else. Rogue platforms are bad hen we're talking lifecycle management across a whole slew of platforms.
AFAIK, Informatica does allow you to export artifacts for proper external storage, but it also requires you to use internal source control in order to import within its own environments. We have some Hyperion here but I can't remember the exact mechanics. In order to migrate an artifact from one environment to another, if there is no internal source control, it
has to have an export/import ability. Is that how it works?
I apologize for going off a bit, this is something that makes my life harder on a regular basis. Platforms that force internal version control are a close first over platforms that do not provide reasonable command line interfaces for artifact management and common functions like service start/stop and platform bouncing. Frustratingly when a platform has one problem it usually has the other too.