In Pulse, there’s a useful feature that allows admin to mark certain TI processes for execution at various stages during Pulse Migration. One such use case which we often use is to run a One Time Only TI process that will create some objects e.g. cubes, dimensions or will update certain values in cubes e.g. security setup etc. in Target database as last step of migration. This removes certain manual steps that the Admin has to otherwise do to complete migration, thereby automating the entire migration process in some cases.
However, it is unclear as to how Pulse chooses list of TI processes that can be run during migration.
E.g. if your migration Package has 10 TI processes that will be updated/created on the target database, then not all of these TI processes are available in the list of TI processes that can be executed. How does Pulse show only certain TI processes from the package & not all ?
In my opinion, the list should include all the TIs from :
- Package being executed
- Target Database
Since there might be a TI process that the admin intends to run after execution which is not part of the package but is already existing in the target database. e.g. create all subsets.