Trying to pull up a job log, and Visual Cron crashes.
I sent you the exception through email.

New version:

[FEATURE] Client/Server: Added multiple Trigger dependency support

Trying to pull up a job log, and Visual Cron crashes.
I sent you the exception through email.

Could be that you use different versions of Client and Server?

+ certificate internal naming

I'm using this version (6.1.0) and the wildcard is still not working correctly.
I just created a task to delete all files in a folder that start with query1.
I put in "query1*.*" and using the test function, it found:
query1_1.txt
query1_2.txt
query1_3.txt

then I put in "query1.txt" and using the test function, it found:
query1.txt

I then executed the first and deleted the first 3 only.

[FEATURE] Client/Server: Added multiple Trigger dependency

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at VisualCron.JobClass.DeleteTriggerFromDepedency(String strDependencyId, String strTriggerId, Boolean bolDeleteInOtherDedendencies)
   at ODNKNCFDHHPJPCMOFFIIHIOEPAPDAKPENFKF.PNOEMAMAKLNOLFHBEPACNMFJNBCALIHBNPMJ.BHCFDJCFHNANLPALEGOKAJIOMCHMPDMECADK()
   at ODNKNCFDHHPJPCMOFFIIHIOEPAPDAKPENFKF.PNOEMAMAKLNOLFHBEPACNMFJNBCALIHBNPMJ.FHOIFEGGFADLOMFFELOPFGLAGMFJNOLPJINC(Object , ToolClickEventArgs )
   at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
   at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
   at Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick()
   at Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.DoClickProcessing(MouseEventArgs e)
   at Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.OnMouseUp(MouseEventArgs e)
   at Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
   at Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
   at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
   at Infragistics.Win.UltraControlBase.OnMouseUp(MouseEventArgs e)
   at Infragistics.Win.UltraWinToolbars.UltraToolbarsDockArea.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

1. Create a job
   
2. Create a default file trigger and name it 1
   
3. Clone this trigger 3 times and name them 2 - 3 and 4
   
4. select the 1st and make a dependency with the 2nd
   
5. select the 3rd and make a dependency with the 4th
   
6. select the 4th and make a dependency with the 1st and deselect the 3rd
   
7. The ERROR should be there now

1. It is possible to have only one trigger in a dependency by changing the dependencies among eachother
   
2. It looks like I'm not able to remove a dependendy. I always have to select 2 or more triggers

Hi,

I have an question regarding the trigger dependency:

If I have multiple sets of dependencies for one job and one set triggers my job all the trigger counts for this set are reset to zero. The other trigger counts, beloning to other sets, aren't.

Is this normal behaviour? Shouldn't all trigger counters set to zero when a job is triggered?

Regards,
Erik

It is possible to have only one trigger in a dependency by changing the dependencies among each other

We could not reproduce (maybe we fixed it with other fixes):

It is possible to have only one trigger in a dependency by changing the dependencies among each other

1. Create a job
   
2. Create a default file trigger and name it 1
   
3. Clone this trigger 3 times and name them 2 - 3 and 4
   
4. Select the 1st and make a dependency with the 2nd
   
5. Select the 3rd and make a dependency with the 4th
   
6. select the 1st and make dependencies with 1, 2 and 3 (4th lost his dependency now)
   
7. select the 4th and make dependencies with 2, 3 and 4
   
8. the 1st trigger is now the only one left in the dependency

We could not reproduce (maybe we fixed it with other fixes):

It is possible to have only one trigger in a dependency by changing the dependencies among each other

To have only one dependency on a trigger do the following:

1. Create a job
   
2. Create a default file trigger and name it 1
   
3. Clone this trigger 3 times and name them 2 - 3 and 4
   
4. Select the 1st and make a dependency with the 2nd
   
5. Select the 3rd and make a dependency with the 4th
   
6. select the 1st and make dependencies with 1, 2 and 3 (4th lost his dependency now)
   
7. select the 4th and make dependencies with 2, 3 and 4
   
8. the 1st trigger is now the only one left in the dependency

I did not try this with the new beta version. I'll do this in a minute.