Ability to have predecessor successor order for Loader Jobs

It would be useful to be able to run a loader job to completion and then start/call the next loader job to be done. 

This would allow a chain of Loader jobs to do things like:

  LDAP load basis group. ( could add new groups/structures)

  SQL loader job to use the data that was just loaded and do the next step. (Example: auto creating Access Policy Groups for any new basis groups that were created)

If the second job starts to soon, it may not do all of what it should do in that cycle. That condition would produce an unnecessary or incomplete results for that cycle.