Changes in this version so far:

[FEATURE] All: New logo and graphical profile
[FEATURE] Client: Added Job count to main window
[FEATURE] Client/API: Added more advanced and selective import of settings
[FEATURE] Client/Server: Popup Task->Now you can send to executing user
[FEATURE] Client/Server: Email Trigger->Optionally create folder tree for emails (and attachments)
[FEATURE] Client/Server: Email Trigger->Added case sensitive option
[FEATURE] Client/Server: File filter->Added result limit
[FEATURE] Client/Server: File filter->Added result sorting
[FEATURE] Client/Server: File filter->Added support for Variables in file size filter
[FEATURE] Client/Server: PowerShell Task->Added x86 execution mode
[FEATURE] Client/Server: Excel - Get cell->Added password support
[FEATURE] Client/Server: Excel - Get cell->Added support for parsing dates
[FEATURE] Client/Server: Excel - Set cell->Added support for old Excel formats
[FEATURE] Client/Server: Excel - Create->Added support for old Excel formats
[FEATURE] Client/Server: Rename methods in various Tasks->Added option to choose between VisualCron and REN implementation in Server settings
[FEATURE] Client/Server: Added support for AD group logon with options to assign specific VisualCron permissions group
[FEATURE] Client/Server: Web service Task->Added client Certificate support
[BUGFIX] Server: Delete files Task->Fixed a false positive error that was not raised properly when a file could not be deleted
[BUGFIX] Server: Email Trigger->Fixed an issue with not firing when using Timeout option on Trigger.
[BUGFIX] Server: SharePoint->Update list item->Fixed Variable resolving issue
[BUGFIX] Server: FTP Task->Fixed a problem overriding Transfer type
[BUGFIX] Server: Settings import->Fixed issue with importing Exit code collections
[BUGFIX] Server: SSISDB Task->Added more debugging and error handling
[BUGFIX] Server: HTTP Task->Fixed parameter type handling for PUT method
[BUGFIX] Server: Minor adjustments in Rename functionality
[BUGFIX] Client: PGP Encrypt->Removed the need for setting password when using conventional encryption
[BUGFIX] Server: Handled a crash related to Flow and Notifications
[BUGFIX] Server: PowerShell Task->Improved exit code and error handling
[BUGFIX] Server: Excel Create/Set cell Tasks->Fixed a problem with row splitting
[BUGFIX] Client: Excel Create->Fixed a problem with validating form
[BUGFIX] Client/Server: Variables->Now handle more complex input (for example JSON which could break the Variable parser)
[BUGFIX] Server: Fixed a potential crash that could occur when handling Variables at execution
[BUGFIX] Server: PowerShell Task->Fixed issue with x86 execution and execution from file issue
[BUGFIX] Server: Fixed general crash issue related to Flow
[BUGFIX] Client: FTP Task->Fixed display issue of Connection used
[BUGFIX] Server: Archive Decompress Task->Fixed a problem with destination folder and error handling
[BUGFIX] Server: FTP Task->Download->Fixed a problem converting old settings which could lead to a reset in Remote file filter settings
[BUGFIX] Server: Assembly execute Task->Fixed a problem reflecting x86 assemblies
[BUGFIX] Server: SQL Task->Handled an error in SQL Job execution related to null messages in result at completion

---

New build, changes:

[BUGFIX] Server: Email Trigger->Fixed an issue with not firing when using Timeout option on Trigger.
[BUGFIX] Server: SharePoint->Update list item->Fixed Variable resolving issue

---

Hi Henrik,
My first impression about the new look is not so good. The color scheme is just not right. When I installed it over 7.2.1 I now have a blackish look. Why this color scheme and not just stick to the windows default, almost everybody application is using. Now it looks childish if you were playing with the color properties. You have to change it (please).

Thanks for the bug fixes though ;-)

Regards,
Erik

---

Hi Henrik,
My first impression about the new look is not so good. The color scheme is just not right. When I installed it over 7.2.1 I now have a blackish look. Why this color scheme and not just stick to the windows default, almost everybody application is using. Now it looks childish if you were playing with the color properties. You have to change it (please).

Thanks for the bug fixes though ;-)

Regards,
Erik

The reason for the color scheme is to match web site colors and logo colors. Also, we are thinking of moving away from Office 2007 look and go to Office 2013 and try to use less gradients.

But, not set in stone yet - still testing.

---

New build, changes:

[FEATURE] Client: Added Job count to main window
[BUGFIX] Server: FTP Task->Fixed a problem overriding Transfer type

---

The reason for the color scheme is to match web site colors and logo colors. Also, we are thinking of moving away from Office 2007 look and go to Office 2013 and try to use less gradients.
But, not set in stone yet - still testing.

I see some colors match the Office 2013 ribbon, but it's just not the same. And the reason for using a windows standard is that it feels natural for the end user.
For a designer it's also easier to stick to the default colors, so you won't have to change all the forms.

Color differences with Office 2013:

• Hover colors in the ribbon rections
  
• Default ribbon section color differs
  
• Titlebar colore is dark grey
  
• the bar behind the ribbon labels is black
  
• Hover color of an item in a section is slightly different
  
• Selected ribbon label is yellow
  

If you want the same look as Office 2013, there is a lot of changing to do.

Regards
Erik

---

The reason for the color scheme is to match web site colors and logo colors. Also, we are thinking of moving away from Office 2007 look and go to Office 2013 and try to use less gradients.
But, not set in stone yet - still testing.

I see some colors match the Office 2013 ribbon, but it's just not the same. And the reason for using a windows standard is that it feels natural for the end user.
For a designer it's also easier to stick to the default colors, so you won't have to change all the forms.

Color differences with Office 2013:

• Hover colors in the ribbon rections
  
• Default ribbon section color differs
  
• Titlebar colore is dark grey
  
• the bar behind the ribbon labels is black
  
• Hover color of an item in a section is slightly different
  
• Selected ribbon label is yellow
  

If you want the same look as Office 2013, there is a lot of changing to do.

Regards
Erik

I am talking about Office 2013 controls - not colors. Still, colors can be different because themes in different programs. But I agree that some colors should be default, like the application bar at least.

---

Not 'entirely' unrelated... But Henrik, you should change the Avatar/image next to your 'Support' name to match the new logo on the forum ;-)

Brian

I know you're actively working on the ribbon/colors/etc... but i've found a glitch that i'll try and explain.

When I first installed 7.5.0 (build date 9-24-2014) i think it was build number 27297, the theme was kinda messed up. Big button in upper left corner had no logo (not sure if on purpose or not), but it wasn't bad looking. Then I downloaded the latest beta this morning (10-2-2014) and installed it. The build version is now 21568, which seems wrong (lower version number) with a build date of 2014-10-01.

The problem is, now the theme is 'flat' and looks sorta bad. haha. But that's not the overall issue. The theme was reset to flat, which is not what I had selected prior. But the problem is, if I go run the Guide and select Black or Blue instead of flat, the next time I close/reopen the client it's 'Flat' again.

One other issue... if I DO run the guide and select Black, or Blue... either one other than Flat, it does look good. That is, until I expand the window to full screen and then back to windowed mode again. Now the Minimize/Maximize/Close (Red 😵 are covered up by a black bar (regardless of choosing blue or black'. Only way to close the client is to right-click the taskbar icon and select close, or press ALT-F4. i'm using 2012 R2 server if that matters. If I drag the window to the top of the screen and let it auto-maximize (windows feature), the minimize/maximize/X buttons are visible again as well as the text in the title bar.

EDIT:
It does appear that it makes a difference in whether you click the maximize or restore (middle) button vs dragging the window by selecting the title bar and dragging down with your mouse to 'pull' it out of maximized mode. If I do it that way, that's when i get the black bar. If I just use the maximize/restore button it looks fine. Hopefully that makes sense.

Brian

Hi Brian,

You just let me check something, the 'Guide'. The three options look much better than the one I was presented after the installation. Now my colors are back to normal (blue theme).

Regards,
Erik

---

Hi Brian,

You just let me check something, the 'Guide'. The three options look much better than the one I was presented after the installation. Now my colors are back to normal (blue theme).

Regards,
Erik

We will polish the first but probably remove the themes completely as they will not match our color profile and it easier to maintain one and keep one profile.Thanks.

---

The reason for the color scheme is to match web site colors and logo colors. Also, we are thinking of moving away from Office 2007 look and go to Office 2013 and try to use less gradients.
But, not set in stone yet - still testing.

I see some colors match the Office 2013 ribbon, but it's just not the same. And the reason for using a windows standard is that it feels natural for the end user.
For a designer it's also easier to stick to the default colors, so you won't have to change all the forms.

Color differences with Office 2013:

• Hover colors in the ribbon rections
  
• Default ribbon section color differs
  
• Titlebar colore is dark grey
  
• the bar behind the ribbon labels is black
  
• Hover color of an item in a section is slightly different
  
• Selected ribbon label is yellow
  

If you want the same look as Office 2013, there is a lot of changing to do.

Regards
Erik

I do not see that Office 2013 follows theme of Windows. Tried changing theme but Office 2013 does not change. If we look at Excel it generally uses a green theme no matter what. OneNote uses a purple theme. Word blue. So, it seems that each Office 2013 application have their own theme.

---

New build, changes:

[BUGFIX] Server: Settings import->Fixed issue with importing Exit code collections
[BUGFIX] Server: SSISDB Task->Added more debugging and error handling

---

Just so i'm clear, is this how it's 'supposed' to look, currently? The 'Flat' look? Nothing I do get's it off this 'theme', even after running through the guide to switch it to a nice looking view (blue or black). Either one is 10x better than the flat look i'm seeing now.

Brian

Just so i'm clear, is this how it's 'supposed' to look, currently? The 'Flat' look? Nothing I do get's it off this 'theme', even after running through the guide to switch it to a nice looking view (blue or black). Either one is 10x better than the flat look i'm seeing now.

Brian

We are still experimenting with colors. Blue and black are using gradients which are not the typical 2014 style - they are based on the gradient Office 2007 controls which are not used in many new applications. The idea is to have one flat look that uses Office 2013 controls. The "choose theme" will eventually disappear from the guide. Maybe come back later but with removed Office 2007 style and different color versions of the Office 2013 control.

As an existing VisualCron user you will find two things that are new. Office 2007 controls are replaced by Office 2013 controls. Colors have changed to fit new logotype and website. Both changes might be new and feel different first. We are likely not going back to Office 2007 controls as they are 'out of fashion' but we may change the colors we are experimenting with.

---

New build, changes:

[FEATURE] Client/API: Added more advanced and selective import of settings
[BUGFIX] Server: Minor adjustments in Rename functionality

---

New build, changes:

[BUGFIX] Client: PGP Encrypt->Removed the need for setting password when using conventional encryption

---

New build, changes:

[FEATURE] Client/Server: Popup Task->Now you can send to executing user
[FEATURE] Client/Server: Email Trigger->Optionally create folder tree for emails (and attachments)
[FEATURE] Client/Server: Email Trigger->Added case sensitive option
[FEATURE] Client/Server: File filter->Added result limit
[FEATURE] Client/Server: File filter->Added result sorting
[FEATURE] Client/Server: File filter->Added support for Variables in file size filter
[BUGFIX] Server: Handled a crash related to Flow and Notifications

---

New build, changes:

[FEATURE] Client/Server: Popup Task->Now you can send to executing user

Awesome thanks, big help for usability options.

Thanks

Lee

New build, changes:

[BUGFIX] Server: PowerShell Task->Improved exit code and error handling

---

New build, changes:

[FEATURE] Client/Server: PowerShell Task->Added x86 execution mode

---

New build, changes:

[FEATURE] Client/Server: Excel - Get cell->Added password support
[FEATURE] Client/Server: Excel - Get cell->Added support for parsing dates
[FEATURE] Client/Server: Excel - Set cell->Added support for old Excel formats
[FEATURE] Client/Server: Excel - Create->Added support for old Excel formats
[BUGFIX] Server: PowerShell Task->Improved exit code and error handling
[BUGFIX] Server: Excel Create/Set cell Tasks->Fixed a problem with row splitting
[BUGFIX] Client: Excel Create->Fixed a problem with validating form
[BUGFIX] Client/Server: Variables->Now handle more complex input (for example JSON which could break the Variable parser)

---

Found a bug in the PowerShell Task while doing some testing related to this post:

http://www.visualcron.co...sts&t=4584#post19604 

Basically, if you check the box for x86 execution, you're ok. If you uncheck it, it's broke permanently. No way to fix without deleting the task and re-creating it.

see screenshot:


Brian

Found a bug in the PowerShell Task while doing some testing related to this post:

http://www.visualcron.co...sts&t=4584#post19604 

Basically, if you check the box for x86 execution, you're ok. If you uncheck it, it's broke permanently. No way to fix without deleting the task and re-creating it.

see screenshot:


Brian

Thanks, this has been fixed in latest build.

---

New build, changes:

[FEATURE] Client/Server: Rename methods in various Tasks->Added option to choose between VisualCron and REN implementation in Server settings
[FEATURE] Client/Server: Added support for AD group logon with options to assign specific VisualCron permissions group
[BUGFIX] Server: Fixed a potential crash that could occur when handling Variables at execution
[BUGFIX] Server: PowerShell Task->Fixed issue with x86 execution and execution from file issue

---