Greetings, Short answer - yes, I shall add you to "the list" but bear the below in mind.
Typically what we do is - and we are doing this more now than we did in the past. If we release a patch that is needed by a particular community, we will just notify that community and if it is globally useful, we will notify globally (as best we can here obviously given the contact and customer information we have) Reason being, many times, something we do to the product does not impact the overall user base as a whole and there is no need for them to upgrade. We work with over 150 business partners (they use our technology to implement their products) who are encountering things that can be quite esoteric and have nothing at all to do with the average end user scripter, but we did need add to the product to support the need - typically in a very rapid manor. We also do the same thing with our end users too btw, it just doesn't happen as often as it does with the partners. So we make the conscience decision not to constantly update everyone about these sorts of changes. More a perception thing - folks may perceive something that is constantly being updated as "half baked". Of course, we don't want to give that false impression. What we do is not at all like what a packaged application vendor can do - anticipate that Version A should do X,Y and Z and anticipate adding Q and D in Version B. The reality is, for what we do, the world is a very big, very complex, ever changing place - so we organize ourselves to react quickly to individuals. Regards, Thom Thom C. Blackwell Product Manager Boston Software Systems (866) 653-5105 ex 807 www.bossoft.com <http://www.bossoft.com/> Sign up for my weekly webinar! <http://www.bostonworkstation.com/customer_center/special_events.aspx> LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. From: [email protected] [mailto:[email protected]] Sent: Wednesday, February 03, 2010 9:03 AM To: Talk Subject: [talkbws] Auto Email for New Versions/Updates Is there a list I can get on for new versions/updates to the BWS Product? Brian Stevenson | Systems Administrator University Health System <http://www.universityhealthsystem.com/> | Business Information Services 8131 Pinebrook Drive | San Antonio, TX 78230 Office | (210) 644 - 0212 Pager | (210) 203 - 9851 Cell | (210) 602 - 5792 --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk .aspx ________________________________ CONFIDENTIALITY NOTICE: This communication is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are notified that any use, dissemination, forwarding, distribution, or copying of the communication is strictly prohibited. Please notify the sender immediately by e-mail if you have received this by mistake and delete this e-mail from your system. (University Health System) --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk .aspx --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonworkstation.com/customer_center/virtual_user_group_talk.aspx
