October 31, 2011
Last we left off, we turned a pseudo relation into an exclusive relation. Specifically, we created a participant2user relation, which allowed us to traverse from an activity to the user who participated in the activity with a path like: focus_obj2act_entry:fact2participant(role_code=1):participant2user:login_name Real World Usage As promised, lets give this some real world usage. Specifically, lets use this to notify someone when a case (or other workflow object) is yanked from them. A few years ago, I showed how to implement yank notifications by email. In that post, I gave some details about the challenges behind using a business rule to do this: The problem with implementing this as a business rule is that there is no data that holds onto the previous owner. Clarify's solution to this is to have the Classic Client always send an integrated Notifier message (insert into…
Notifying the Yankee
October 31, 2011
Last we left off, we turned a pseudo relation into an exclusive relation. Specifically, we created a participant2user relation, which allowed us to traverse from an activity to the user who participated in the activity with a path like: focus_obj2act_entry:fact2participant(role_code=1):participant2user:login_name Real World Usage As promised, lets give this some real world usage. Specifically, lets use this to notify someone when a case (or other workflow object) is yanked from them. A few years ago, I showed how to implement yank notifications by email. In that post, I gave some details about the challenges behind using a business rule to do this: The problem with implementing this as a business rule is that there is no data that holds onto the previous owner. Clarify's solution to this is to have the Classic Client always send an integrated Notifier message (insert into…
April 22, 2008
Quickly after creating a Twitter Integration with Dovetail I ran into rate limiting issues using Twitter's API. Twitter currently only allows 70 requests per hour. Here is their guidance... If you are developing an application that requires more frequent requests to the Twitter API, please contact us and we'll see what we can do. We maintain a white list of known-good screen names who have high-volume API needs. We also suggest researching Jabber/XMPP if your application needs to deliver a near-realtime experience (for example, a bot that replies to direct messages). I emailed Twitter support asking nicely for higher volume API usage but still haven't gotten a response. Then I realized that if we want to release this Dovetail/Twitter integration to our customers we it need to work within the rate limiting guidelines, so I listened to Twitter's guidance and…