Maybe this should be in feature requests?

In the process of experimenting with the task repository I created a powershell task in the repository and job/task that referenced it. The only option is to reference the repository task by direct ID. I then deleted the powershell task from the repository and readded it. Now the job fails as the new task has a new ID but the task in the job still references the old task repository ID.

What if I brought down a new version from the online repository or dropped/added my own task, would it get a new ID and break existing tasks?

What about copying repository tasks between servers? Would the same issue of the risk of overwriting repository tasks exist that exists right now with standard jobs/tasks? I'd love to see a server-independent task repository. Which brings to mind the question, how is that handled with tasks from the online repository? Are they assigned server-dependent task ID's when downloaded? If so, we need this for jobs and tasks copied between servers ASAP!

Downloading will keep the same Id (and overwrite it if you redownload). There is no risk of clash between id's in general. It is the same as with Jobs.

Probably we can add support to reference Task repository object by name. Will move this topic to Feature requests.

---

Since its related I'd like to add an additional thing. In the task repository, tasks are listed by name and description. And in the variables window, one selects the task from the tree control by name. However, once selected the VC variable name (for instance in the "value" box of a set job variable task) is only the cryptic task_id: {TASKREPOSITORY(cac72ba7-a697-4663-96e4-cbe001187305|)}. In the future there's no way I'll know what task that is by the ID alone. This is just an example or argument for being able to reference the task by name.

Please try with this now: https://www.visualcron.c....aspx?g=posts&t=9532 

You should be able to use the Name property instead of Id.

---

Manually typed the name of the task's function instead of the ID (no double-quotes): worked. I could not select it though, the default is still "direct" which of course plugs in the ID.

Manually typed the name of the task's function instead of the ID (no double-quotes): worked. I could not select it though, the default is still "direct" which of course plugs in the ID.

Right, it is more like a hidden feature right now.

---