Hi,

I do not like the GUI for the trigger dependency.
It's not clear you have to select a trigger and setup the dependencies for this trigger. The popup window is not telling you that you are setting up the dependencies for the selected trigger.

I made a new GUI screen that does the trick and hope you will use this as the new dependency window.

Regards,
Erik

Thanks for the image. But why is the selected Trigger important? The window is design to create any dependency and not just selected Trigger.

---

Edit: A Trigger do not have any property 'dependency'. It is the Job that have a list of dependencies where each dependency may link to Triggers (within the Job) that exist in that Dependency.

---

Hi,

The dependency window is now also using the selected trigger as an input for the selection in the list. But is is not clear for the end user.
Yesterday I saw that it was possible to make more dependencies to select a different trigger before clicking on the Dependency button. Before that I did not know this becouse it wasn't clear.

With my screen it is clear to the end user that you are doing something for the selected trigger, so he knows he can select other triggers to make more dependecies.

[EDIT] Not that my screen is the one, but it's more clear you have to select other triggers to make more dependencies [/EDIT]

Regards,
Erik

---

Hi,

The dependency window is now also using the selected trigger as an input for the selection in the list. But is is not clear for the end user.
Yesterday I saw that it was possible to make more dependencies to select a different trigger before clicking on the Dependency button. Before that I did not know this becouse it wasn't clear.

With my screen it is clear to the end user that you are doing something for the selected trigger, so he knows he can select other triggers to make more dependecies.

[EDIT] Not that my screen is the one, but it's more clear you have to select other triggers to make more dependencies [/EDIT]

Regards,
Erik

Actually, it is not a Trigger that needs to be selected but a dependency. So, the validation might be wrong. This may be a little bit unclear. The actual selected Trigger is not important at all as you select Triggers in the checkbox which could be completely different from the 'selected' Trigger - as the 'selected' refers to a dependency and not a Trigger.

So, I think we need to forget about the relation to Trigger when pressing the Dependency button but rather think 1. is a Dependency on the selected Trigger? If yes, edit the dependency. If no, create a new one.

---

So, I think we need to forget about the relation to Trigger when pressing the Dependency button but rather think 1. is a Dependency on the selected Trigger? If yes, edit the dependency. If no, create a new one.

Ok, I understand this now.

So what about a Dependency label in the menu bar and having two buttons here: Add/Edit en Delete instead of the current Dependency button.

Regards,
Erik

---

Yes, that might be something to change - not sure if we will do that in current version. Right now we have constructed documentation for the current look. We appreciate the feedback here.

---

Hi,

What if I have a dependency in place and I disable one trigger in this dependency.
Now, the job will never run due to an incomplete dependency, but shouldn't an inactive trigger be excluded from the dependency?

Regards
Erik

---

Hi,

What if I have a dependency in place and I disable one trigger in this dependency.
Now, the job will never run due to an incomplete dependency, but shouldn't an inactive trigger be excluded from the dependency?

Regards
Erik

Thanks for the remark. We have made a change to support this for next build.

---