Login Cart  Cart
logo

Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
View
Go to last post Go to first unread
Offline Support  
#1 Posted : Thursday, April 7, 2011 12:54:02 PM(UTC)
Support
Rank: Administration

Joined: 2/23/2008(UTC)
Posts: 7,575

Thanks: 335 times
Was thanked: 195 time(s) in 186 post(s)
Changes in 5.7.4.

[FEATURE] ClientServer Added the PowerShell Task
[FEATURE] Server VisualCron now executes Jobs (once) that should have been executed within a DST change period, i.e. 201 AM when change goes from 2 AM to 3 AM
[FEATURE] Server Added OnOff setting for database logging
[BUGFIX] Server Fixed 64 bit issue in Office Macro Task
[BUGFIX] Client Illegal characters in Execute Task command caused crash
[BUGFIX] Client Fixed compatibility issue with old Web service Tasks
[BUGFIX] Client Fixed crash in Set Variable Task when wrong type was used
Henrik
Support
http://www.visualcron.com

Please like VisualCron on facebook!
Offline ErikC  
#2 Posted : Monday, April 11, 2011 9:15:57 AM(UTC)
ErikC
Rank: Administration

Joined: 2/26/2008(UTC)
Posts: 1,191
Netherlands
Location: Amsterdam

Thanks: 53 times
Was thanked: 98 time(s) in 84 post(s)
Hi,

The bug with the conditions GUI update is still in this version. (Also in the current stable release 5.7.3)

Previous post from version 5.6.9

Regards,
Erik
Uses Visualcron since 2006.
Offline Support  
#3 Posted : Monday, April 11, 2011 10:44:57 AM(UTC)
Support
Rank: Administration

Joined: 2/23/2008(UTC)
Posts: 7,575

Thanks: 335 times
Was thanked: 195 time(s) in 186 post(s)
ErikC wrote:
Hi,

The bug with the conditions GUI update is still in this version. (Also in the current stable release 5.7.3)

Previous post from version 5.6.9

Regards,
Erik


Yes, currently we do not updating anything from the previous Task when going back and forward.
Henrik
Support
http://www.visualcron.com

Please like VisualCron on facebook!
Offline ErikC  
#4 Posted : Monday, April 11, 2011 11:03:51 AM(UTC)
ErikC
Rank: Administration

Joined: 2/26/2008(UTC)
Posts: 1,191
Netherlands
Location: Amsterdam

Thanks: 53 times
Was thanked: 98 time(s) in 84 post(s)
Hi,

So this behaviour is an GUI inconsistency because e.g. the notifications are updated.
Is this going to be changed?

Regards,
Erik
Uses Visualcron since 2006.
Offline Support  
#5 Posted : Monday, April 11, 2011 11:11:47 AM(UTC)
Support
Rank: Administration

Joined: 2/23/2008(UTC)
Posts: 7,575

Thanks: 335 times
Was thanked: 195 time(s) in 186 post(s)
ErikC wrote:
Hi,

So this behaviour is an GUI inconsistency because e.g. the notifications are updated.
Is this going to be changed?

Regards,
Erik


This is going to be changed. The main problem, which have prevented us from doing it is the Cancel button. The Cancel button refers to the current Job but should the Next/Previous buttons act as OK buttons? As there are so many settings in each Task we cannot "track" if changes where made or not. So, treating it as Ok button would be the best option. But, it could be slightly confusing with the Cancel button anyway.

What do you think?
Henrik
Support
http://www.visualcron.com

Please like VisualCron on facebook!
Offline ErikC  
#6 Posted : Monday, April 11, 2011 12:30:17 PM(UTC)
ErikC
Rank: Administration

Joined: 2/26/2008(UTC)
Posts: 1,191
Netherlands
Location: Amsterdam

Thanks: 53 times
Was thanked: 98 time(s) in 84 post(s)
Support wrote:
What do you think?

Using the buttons as OK buttons seems fine to me. But it has to be clear to the end user that using the two navigation buttons will apply changes.
You might want to change the names on then two buttons:
- Apply & Previous
- Apply & Next

The Cancel button implies that the actions can be cancelled. You could rename this button to 'Close', and the OK button could be renamed to 'Apply changes'.

Regards,
Erik

Edited by user Monday, April 11, 2011 12:30:50 PM(UTC)  | Reason: typo

Uses Visualcron since 2006.
Offline ErikC  
#7 Posted : Friday, April 15, 2011 10:09:13 AM(UTC)
ErikC
Rank: Administration

Joined: 2/26/2008(UTC)
Posts: 1,191
Netherlands
Location: Amsterdam

Thanks: 53 times
Was thanked: 98 time(s) in 84 post(s)
Just an addition to my previous post:

What will happen when I now only use the task navigation buttons and then clicking on the OK button?

I think if there are condition changes within the tasks the active task will change the condition set when I click on the OK button.

If this is the case, I think you should remove/disable the buttons till there is a full update when using the navigation buttons. You than change the task without knowing you are changing stuff.

Mad
[edit]
I just checked myself and this is indeed the case!
This is a major issue I think and should be fixed asap.
Now I have to instruct all my people not to use the navigation buttons.
[/edit]


Regards,
Erik

Edited by user Friday, April 15, 2011 10:14:19 AM(UTC)  | Reason: Not specified

Uses Visualcron since 2006.
Offline Support  
#8 Posted : Friday, April 15, 2011 3:27:37 PM(UTC)
Support
Rank: Administration

Joined: 2/23/2008(UTC)
Posts: 7,575

Thanks: 335 times
Was thanked: 195 time(s) in 186 post(s)
ErikC wrote:
Just an addition to my previous post:

What will happen when I now only use the task navigation buttons and then clicking on the OK button?

I think if there are condition changes within the tasks the active task will change the condition set when I click on the OK button.

If this is the case, I think you should remove/disable the buttons till there is a full update when using the navigation buttons. You than change the task without knowing you are changing stuff.

Mad
[edit]
I just checked myself and this is indeed the case!
This is a major issue I think and should be fixed asap.
Now I have to instruct all my people not to use the navigation buttons.
[/edit]


Regards,
Erik


We will look at this. Thanks for the report.
Henrik
Support
http://www.visualcron.com

Please like VisualCron on facebook!
Offline astorrs  
#9 Posted : Tuesday, April 19, 2011 9:15:11 AM(UTC)
astorrs
Rank: Newbie

Joined: 4/19/2011(UTC)
Posts: 2
Location: Vancouver, Canada

I'm getting the following error (stderr) when trying to execute "PowerShell script text" tasks in 5.7.4:

Quote:
Exception in Task: Cannot invoke this function because the current host does not implement it.

Executing against a "PowerShell file" works fine, as do other tasks. The PowerShell script text error occurs for even the most basic cmdlets (e.g., Write-Host "Hello World")

Windows 7 64-bit (no SP1) with VisualCron 5.7.4 running locally in Client/Server mode.

Any ideas? And is there any documentation on what's allowed in the PowerShell script text field? (e.g., VisualCron variables?)
Offline Support  
#10 Posted : Tuesday, April 19, 2011 12:42:02 PM(UTC)
Support
Rank: Administration

Joined: 2/23/2008(UTC)
Posts: 7,575

Thanks: 335 times
Was thanked: 195 time(s) in 186 post(s)
astorrs wrote:
I'm getting the following error (stderr) when trying to execute "PowerShell script text" tasks in 5.7.4:

Quote:
Exception in Task: Cannot invoke this function because the current host does not implement it.

Executing against a "PowerShell file" works fine, as do other tasks. The PowerShell script text error occurs for even the most basic cmdlets (e.g., Write-Host "Hello World")

Windows 7 64-bit (no SP1) with VisualCron 5.7.4 running locally in Client/Server mode.

Any ideas? And is there any documentation on what's allowed in the PowerShell script text field? (e.g., VisualCron variables?)


To output normally you need to use this code:

Quote:
Write-Output "Hello World"
Henrik
Support
http://www.visualcron.com

Please like VisualCron on facebook!
Offline astorrs  
#11 Posted : Tuesday, April 19, 2011 6:25:08 PM(UTC)
astorrs
Rank: Newbie

Joined: 4/19/2011(UTC)
Posts: 2
Location: Vancouver, Canada

Support wrote:
To output normally you need to use this code:

Quote:
Write-Output "Hello World"

Thanks Henrik, I was testing out the new version at 11pm at night and obviously wasn't thinking straight, given that the answer is as clear as day in the error message. ;)

The new feature works like a charm, I'm really excited about how much cleaner this will make my jobs (without having to shell out and execute the scripts outside of VisualCron's built-in logging capabilities).

Andrew
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

footer
Follow VisualCron on Facebook Follow VisualCron on Twitter   Join the VisualCron group on LinkedIn neteject.com anyconnect.net millimetrics.com xendapp.com