Interaction bug between e-mail and dependencies editor?

If I have e-mail options selected in a job, then create some dependencies in the editor, the job definition appears to be incorrect.

Steps to reproduce:

1. Create a new job, 'A'. Leave everything as default except choose 'send e-mail' on 'job error'.
-> there are now 12 steps in the job as expected
Click finish
2. Create job 'B'. Leave everything as defaults
3. Go into the Job Dependencies Editor
4. Drag jobs A and B onto the page
5. Create a link from A to B (make B dependant on A)
6. Close and save the dependencies
7. Edit job A
-> there are still 12 steps. I would expect 13 (e-mail options have disappeared).
-> the 'create semaphore' flags aren't set, yet step 9 is for output semaphore files
-> the output semaphore file is empty, I would expect a filename

24x7 3.4.27 Windows 2000

This is actually a documented deficiency. The Dependencies Editor doesn't preserve existing notifications actions and triggers when you use it to modify the dependencies. It always overrides actions and file names. I hope the internal working of the Dependencies Editor will be improved in future versions.

To avoid getting into this situation please enter semaphore file names and actions manually. If you enter the same file or file mask for the "create file" action in job A and "file watch" schedule for job B, the Dependencies Editor should reflect such dependency on the job dependencies diagram. To enter multiple dependencies, specify comma-separated file names/masks; the notification action event controls type of dependency.

	SysOp wrote:
	This is actually a documented deficiency. The Dependencies Editor doesn't preserve existing notifications actions and triggers when you use it to modify the dependencies. It always overrides actions and file names. I hope the internal working of the Dependencies Editor will be improved in future versions.

Can you confirm this only affects the Windows version? The cross-platform version seems OK...

In fact the cross-platform version generally seems more advanced than the Windows one...?

Feature-wise it doesn't currently support JAL automation language with all JAL commands and extensions. On the other hand, it supports cross-platform JavaScript, which the Windows version doesn't. The rest is in a bit more advanced state in the multi-platform version than comparable features in the Windows version.