File Transfer Paths lost in an ALIAS job - retains original job's paths

Discussion created by shravani_vedantham_6826 on Jan 10, 2018
Latest reply on Jan 29, 2018 by shravani_vedantham_6826


I am looking for a solution for an issue we are currently facing in Production after migrating from AM V8.10 to A.E 12.0.2

Here is the background : We support a wide range of File Transfers from one server to many servers. In order to save up memory in DB and also to avoid multiple jobs where Source is always the same. We have come up with a solution to create one Base Job and use that job as an ALIAS in all other JOBP's where needed. The job is added to the JOBP/Flow and only the task properties is changed as per the destination.(like, the login, file paths etc.,)

Now the issue is , after creating a new flow with the ALIAS job in it, save it and close. When the job actually is scheduled to run, the FTP tab loses its information and retains the Base job's values and fails.

Again, this doesn't happen all the time, but happens often. The times when it happened/this was noticed is

  1. When it is transported from another client/Environment
  2. Copy a JOBP with ALIAS jobs in it
  3. this even happens when there are two ALIAS jobs in a JOBP and only 1 is modified , the other loses

This really is creating an issue and re-work as we have to enter the paths/logins on the FTP tab. Would like to know if this happened with any other applications and really appreciate any suggestions/inputs.

Please do let me know if you need additional information. I created a ticket with Automic Support and you can find more information inINC00217452