This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Forum
- :
- Re: Learn more on the 21st
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 26, 2003
07:11 PM
Learn more on the 21st
My company plans to upload a "Learn More" message on the 21st of each month (not an update, just a message). How can I automatically display messages the first time the application is started on or after the 21st? If the user has already been given the opportunity to Learn More, we don't want to bother them again until the 21st of the next month.
If Update Service can't help me, I'm prepared to use brute force (i.e. the local system clock and a file indicating the last time messages were displayed). SetScheduleInterval() appears to be of little use since it works off of relative rather than absolute dates. For marketing purposes, we really want this to happen on the 21st rather than just every 30 days.
Rick LaMont
If Update Service can't help me, I'm prepared to use brute force (i.e. the local system clock and a file indicating the last time messages were displayed). SetScheduleInterval() appears to be of little use since it works off of relative rather than absolute dates. For marketing purposes, we really want this to happen on the 21st rather than just every 30 days.
Rick LaMont
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 29, 2003
07:31 AM
The Update Service displayscheduledupdates() was designed to spead the load of updates over a given timeperiod. You are trying to do the opposite. You want everyone to check on the 21st. The good news is that you can probably easily work around this. See if this combination of calls works for you...
---------
When your app starts, check the system clock.
if it is the 21st, call displaymessages()
if it is not the 21st,
call appupdate() to check for critical/ optional software updates
----------
There are a few other variations on this you could use depending on how often you want to check for actual software updates.
---------
When your app starts, check the system clock.
if it is the 21st, call displaymessages()
if it is not the 21st,
call appupdate() to check for critical/ optional software updates
----------
There are a few other variations on this you could use depending on how often you want to check for actual software updates.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 30, 2003
02:53 PM
Regarding the poor design of my application, may I direct your attention to the word "marketing" :rolleyes:
As far as the brute force algorithm, it's more involved than just checking the system clock to see if it's the 21st. Suppose the 21st is a Saturday and the user doesn't login until Monday. Then we want to display messages on the 23rd. If the user runs the program 10 times on the 21st we only want to pester them once.
In any event it's working now. I'll spare you the implementation details.
Thanks,
Rick LaMont
As far as the brute force algorithm, it's more involved than just checking the system clock to see if it's the 21st. Suppose the 21st is a Saturday and the user doesn't login until Monday. Then we want to display messages on the 23rd. If the user runs the program 10 times on the 21st we only want to pester them once.
In any event it's working now. I'll spare you the implementation details.
Thanks,
Rick LaMont