I can't find in any doc which calendar activiti timer uses. Is it a business calendar (takes into account only weekdays) or a regular calendar?
I need to terminate process in 14 days by the regular calendar (2 weeks). So if I use this duration in timer event P14D will it trigger event in 14 days or in 14 weekdays????
I went through activivi calendars' source files and found out that it works with the regular calendar even though all that calendars named as "business" calendars.
Related
I am currently using the google calendar API to insert events into a calendar. This is the RRULE that I am using for now that allows me to insert an event at the same time on specific days of the week every week.
RRULE:FREQ=WEEKLY;INTERVAL=1;COUNT=30;BYDAY=TU,WE,FR;
Currently, events are being inserted at the same time on TU, WE & FR. However, I would like to insert the event at different times each day.
For example, the event should be between 3-4PM on Tuesdays and Wednesdays every week but between 5-7PM on Fridays. I want to avoid creating 3 separate weekly recurring events by calling the calendar API with different timings for each of these instances.
You can only use the recurrence rules on recurrent events. As it is described on the docs "Events are called recurring if they repeat according to a defined schedule". In this scenario you are effectively requesting different events albeit very similar ones because you need different schedules for each one.
Basically, im trying to make sense out of user_engagement events, i've read that they are triggered once the user is with the app on first plane for at least 10 seconds, but once they are with the app open and triggered the first user_engagement event, when is the next one gonna be triggered? After 10 minutes of use? after another 10 seconds? I couldnt find that number.
"Duplicate Event" button doesn't work for me. I need to replicate event data for multiple events (dates).
Can create an event template in order to create multiple events with the exact same settings/data? If so, what's the process?
Context: this is for recurring events involving sporting equipment rental.
Use the link below to see. Forward to May. Note the event times on the 15th. I essentially want the exact same events replicated from 15 May-15 October and I'd love to avoid manually inputting each event. For example, I'd like to create a template for the 11a-1p rental and create an event for each of the days within the aforementioned time period without editing every detail of the event roughly 180 times. Same for each other event. That's 8 different events (all identical) for roughly 180 days of the season. That's a lot of manual data input. Feel me?
Events Calendar
I would like to get all events of a recurring event.
Therefore I set the option singleEvents to true.
Now, when I list all events, the response returns endless items (by using nextPageToken). Sure, I can set a MaxTime to have a maximum time limit.
However, I need the syncToken to get only updated events. Otherwise my server has a lot of synchronization tasks. :(
The server gets Push Notifications when something changed. When I create a recurring event, the server recieved the push notification and tries to get the updated events via the last syncToken (using list events).
How can I set a maximum time limit, so I can get the nextSyncToken without having endless nextPages.
My current call:
GET https://www.googleapis.com/calendar/v3/calendars/[CALENDAR]/events?singleEvents=true&syncToken=[SYNC-TOKEN]
When you use a sync token, GCal gives you all the updated events and the only way to limit the amount of events in each response is to use a pager. Set maxResults to limit the amount of results you get per page (max 2500) and then use pageToken until you get another nextSyncToken which means you are at the last page and there are no more events to sync. Each request will either have a nextSyncToken or nextPageToken but no both.
GCal creates 730 events for repeating events without some kind of limit, so 2 years worth of daily events or just under 61 years for a "first Friday of each month" type event. You can check this with the built in API and copying the results to somewhere you can search and count the instances of one of the keys. With defaults, 250 results per page with the 3rd page returning 230.
This isn't just how many are passed with events list and singleEvents true. You'll see in your GCal calendar that the events stop after this time and if you check back tomorrow there won't be another daily event that's been created.
Of course, there could be many long events since the last sync but since you're using push notifications this shouldn't affect you.
Lately I have been dealing with a similar scenario and came up with this solution:
-set singleEvents to false
-for recurring events retrieve instances individually with timeMin and timeMax
Now you can still use syncTokens and the instances() part of the API let's you break up the recurring events into single events with a query. You just have to make sure you do a full sync if you are nearing timeMax again.
Source: https://developers.google.com/google-apps/calendar/v3/reference/events/instances
I am creating an app in asp.net for Google calendar integration. When we insert a particular event to the calendar then at the same point i want to copy the same calendar event in to another calendar and i want to do the same process in a single request. So may any one please guide me for this problem. I am using google calendar version 3 for this. Thanks in advance
Is it necessary that they be two separate Calendar events? If not, you should be adding the second calendar as an attendee of the event rather than creating a copy of the event. See the events reference and look for the attendees list attribute. This can be achieved in a single API call.
If it is indeed necessary that the events are entirely separate and independent of each other, it will require two events.insert() operations, one on each calendar. However, as long as the user you are authenticating as has access to both calendars, it should be possible to batch the two operations into a single HTTP call.