Year, month, and day variables.
When sending a file with a scheduled task in the event manager we only have the {{T}} and {{TSTR}} variables available to add a time stamp to the file name. I need to send files with a YYYY_MM_DD time stamp for compatibility with an external service. Also having variables for the year {{YYYY}} or {{Y}, month {{MM}} or {{M}} and day {{DD}} or {{D}} would make this possible.
-
Hi Michel, thanks for your request. I do see that {{TSTR}} is the only human readable datestamp variable that Cerberus currently offers, and this was only introduced last year. I can get your request over to engineering, but the more detail the better for when our team reviews the request. So I can get this over to engineering could you please provide as much context/background information as possible? It would help if you can answer the following questions. Thanks -- Ian
- What is the problem that this feature would fix?
- Why is it a problem?
- Is there a workaround you currently have for this problem?
- Do you have a suggestion on how you would like to see the problem fixed??
- How big is the problem? Who is affected by this problem? (End Users, Admins, etc.)
0 -
- What is the problem that this feature would fix?
It would allow me to automate sending files with names that have custom date formats.
- Why is it a problem?
Because the current {{TSTR}} format is not compatible with an external service provider.
- Is there a workaround you currently have for this problem?
Not currently, but I could probably do it with PowerShell and OpenSSH instead if I end up having to.
- Do you have a suggestion on how you would like to see the problem fixed??
Just add separate variables for the year, month, and day.
- How big is the problem? Who is affected by this problem? (End Users, Admins, etc.)
Data for a financial service is not being updated automatically. Admins currently have to upload it manually.
0 -
Excellent, thanks, much appreciated. I will get this into an Engineering request today.
0
Please sign in to leave a comment.
Comments
3 comments