Posted by Dylan Wan on May 25, 2012
ODI provides the shortcut feature since the 188.8.131.52.0 release. Shortcuts look like symbolic links in Linux file system and shortcuts in windows. You keep a reference to an object that exists in another folder.
The symbolic link feature has been used widely in prepackaged apps development to handle multiple releases of the software product internally. Typically multiple top folders are created, one for each release.
Many codes can be shared from an old release to its next release. Instead of copying the codes, a symbolic link can be created in the folder created for the new release to point to the code in the folder created for the old release.
ODI shortcut feature was created for a similar purpose.
ODI allow you to create shortcuts for these objects under the ODI Project:
Shortcuts are for the codes that the developers created and modified. It try to maximize the code reuse. You create a code in a folder, and reference it in another folder, after you change the code in the original folder, the reference in the other folder also get the change. You do not need to make the same change over again for each release.
I also notice that the scenarios are not shortcutable. The scenarios (package scenario and interface scenario) are executable objects.
This dsign means that the scenarios should be regenerated after the shortcuts are created. It also means that the scenario should be regenerated after the code in the base folder is modified. It is kind of strange, but it is a design to help you to maximize the code reuse. Each interface or a package is tie to an ODI model and model could be source apps version specific. You want your code to run against a different model even the code is a shortcut.
Folders are also not shortcutable. ODI Folders are not regular folders like the way how we think in the file system directory. Each folder carries a property called “Release Tag”. The release tag can help redirecting the model to be used in generating the scenarios.