3 weeks ago
A client of mine is having problems with the promotion process of DataFlux objects. Here is the process:
The issue is somehow related to a task within monitoring transformation. Selecting another task, then reselecting original tasks solves the problem. Sounds like some sort of referential issue with tasks, but why the same issue wouldn't appear in other environments?
Opening up the job within XML editor, I can't see a reference to a task within monitoring transformation. Where does that reference get stored in a package?
Checking repository tasks, job and rules id shows that they are different between environments, so this can't be a problem since Dev2Int works fine.
Any ideas or suggestions are welcome.
It would be interesting to know, when you look at the repository database tables across each environment, if the "jobcode" associated with the task in the originating system remains the same after export then import to subsequent systems, or if it changes when imported to the business rules repository for the UAT system. I believe that's how the job node knows what business rule to reference.