Working Period is opened everyday at 6:00 am and is closed every night between 2 and 3 am.
At 5:00 AM a trigger executes a rule to save 2 reports to files.
At 5:05 AM a trigger executes a rule to send these 2 reports by email.
Results:
First Problem: each reaport is sent twice.
Second Problem: Working Period report is sent with Endind Time4:59 AM (1 minutes before trigger) instead of the real Ending Time of Working Period (in the showcase : 2:20 AM)
Third Problem: This morning it CREATES the files with the 2 days old Working period.
One problem is that Helper.GetUniqueString() (or any other {DATE:X} functions that you could use in V5) will generate the date/timestamp on the fly, so your saved Report Name will be different than your Report File Attachment, because the Helper is generating timestamps seconds (or minutes) apart from each other in the Actions.
You should generate the Report Filename ONCE and store it in a Program Setting, then use the Program Setting for the Report Save action and the Email Attachment action.
Also, hard-coding the attachment Filename in the Save Report Action and the Email Action is a bad idea. Make it a [:parameter] and feed in the Program Setting Filename from the Rules.
Generates only the date (no hh:mm:ss) like WP_MMDD_YYYY.xps which I am fine with due to the fact that I create the file and send it the same day. And that works well … also I will not change it, as at least this part works. The problems are:
Report is sent twice
today “Save report to File” saved today an old working period.
(ignore the yellows, these are the ones I generated manually)
Got it for #2 problem !!!
(I guess)
It might be due to the fact that:
in order to excute the trigger SamPOS.exe has to be running (always the case on the server for administrative purpouses)
As I don’t come on Sundays, SambaPOS was running since the Saturday without closing it on and off or login/logoff !
It must be that because SamPOS behaves like a fool when no log off/log on has happened for more than 1 day as far as reports/tickets/messages/etc … are concerned
So basically I cannot take a day off.
(waitress closes working period from a terminal, server is always on with SambaPOS running)
That is very likely true. The Trigger mechanism should probably moved into the Message Server service since it is likely to always be running.
As for sending email twice, you wouldn’t happen to have the TO and CC addresses the same would you?
That’s fine if you don’t want to take my advice on “best practices” for SambaPOS. You should almost never hard-code action parameters in the Action itself, especially when those parameters contain things that you know will be dynamic. I have seen this exact problem before because people hard-code the action parameters instead of making them a [:parameter] and wonder why it doesn’t work.
