Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Feature REQUESTS
(04-29-2025, 07:21 PM)admin Wrote: You should know that the current version does not pass the backup result to the post command. If the backup result is passed to the post command, this may cause errors for post commands that do not support this parameter.


Hello,
  You can add a checkbox to pass the result. (Default unchecked)
 
Thank you
Reply
(Yesterday, 08:26 PM)chmichael Wrote:
(04-29-2025, 07:21 PM)admin Wrote: You should know that the current version does not pass the backup result to the post command. If the backup result is passed to the post command, this may cause errors for post commands that do not support this parameter.


Hello,
  You can add a checkbox to pass the result. (Default unchecked)
 
Thank you

Get what you mean and I'll give feedback to my development team.
Reply
(Today, 12:01 AM)admin Wrote:
(Yesterday, 08:26 PM)chmichael Wrote: Hello,
  You can add a checkbox to pass the result. (Default unchecked)
 
Thank you

Get what you mean and I'll give feedback to my development team.

I would prefer something like dynamic variables that can be used whenever needed.

Examples:
%time% = current time
%date% = current date
%exitcode% = ok|error
%errorcode% = error code, if error occured
%errormsg% = error message, if error occured
%runtime% = runtime in seconds
%size% = backup size in kbyte
... and a lot of other maybe useful variables.

Then you can implement a small link that opens a popup to show all the available variables to choose from.

When needed, you can then use any/none of the given variables in the parameters.
So if your application needs an error code, just give it a go with myapplication.exe code=%exitcode% or something similar.

Another advanced idea could be the implementation of webhooks or the possibility to specify a direct URL that gets executed. This could also support variables then.
Reply
(Today, 12:40 AM)al3x Wrote:
(Today, 12:01 AM)admin Wrote: Get what you mean and I'll give feedback to my development team.

I would prefer something like dynamic variables that can be used whenever needed.

Examples:
%time% = current time
%date% = current date
%exitcode% = ok|error
%errorcode% = error code, if error occured
%errormsg% = error message, if error occured
%runtime% = runtime in seconds
%size% = backup size in kbyte
... and a lot of other maybe useful variables.

Then you can implement a small link that opens a popup to show all the available variables to choose from.

When needed, you can then use any/none of the given variables in the parameters.
So if your application needs an error code, just give it a go with myapplication.exe code=%exitcode% or something similar.

Another advanced idea could be the implementation of webhooks or the possibility to specify a direct URL that gets executed. This could also support variables then.

Thank you for your suggestion, this feature will be implemented in a future release.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)