A few months back during a discussion in the office @JohnPrawyn was talking about some difficulty in doing a birthday alerts app using orangescape, (orangescapian’s birthday alerts is his responsibility). Then I just forgot about it.
2 days back, i fell asleep while reading, and i had a dream about the implementation of the birthday app, I woke up and quickly noted down what ever i had remembered. It was simple, but there were some small problems…. So here is the process flow, which i had dreamed.
There are no ways to schedule things as of now (maybe some feature is on the pipeline!), so i decided to use the SLA feature. Checks are done to find the Birthday every month / week / day (based on the nearness of the alert day).
The above process flow, is flawless on the paper, now have set some data to check it.
So, are you still wondering what was the small problem that i had talked about. Yeah, there is a problem there. A feature of SLA is that the time duration to check will start off once the request reaches the particular activity. which means, for ex. In the Process Flow above, if the request reaches the activity Initialize, at say evening 4:30 and the SLA hours are set as 24 hours, then the activity will next happen tomorrow at 4:30 in the evening. Which means, to get the reminder at the beginning of the day, i should sit at the beginning of the day and set the reminder. Will need to find a work around on that. (i have one, but let me first finish the testing of this first, it everything works fine, then i will implement it out.)
O! and there are only 6 fields (+ system fields) in the model,
Well anyway, i had dreamed of solutions before, but nothing of this sort has happened. It would usually be like conversing with someone and coming up with something, but not the complete answer to a question.