Exactly! On Wed, Feb 22, 2012 at 1:32 PM, LJ LongWing <[email protected]> wrote:
> ** > > That wouldn’t be a good solution then….in fact it would be a worse > situation because then you would have an un-logged modification…**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Jason Miller > *Sent:* Wednesday, February 22, 2012 2:22 PM > > *To:* [email protected] > *Subject:* Re: Disalowing 7.5 developer tool on a 7.6.04 system**** > > ** ** > > ** Just the log entry. My workflow was created and I was able to continue > modifying the object; it just was never logged.**** > > On Wed, Feb 22, 2012 at 1:06 PM, LJ LongWing <[email protected]> > wrote:**** > > ** **** > > Jason,**** > > Interesting, did it stop the modification, or just the log entry?**** > > **** > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Jason Miller > *Sent:* Wednesday, February 22, 2012 1:45 PM > *To:* [email protected] > *Subject:* Re: Disalowing 7.5 developer tool on a 7.6.04 system**** > > **** > > ** **** > > I have been wanting to do some experimentation with Dev Studio and the > Object Modification log for a while so I took this as an opportunity to see > if I could block a DS change.**** > > **** > > I have Object Modification logging turned on and then wrote a filter > against the form that would throw an error when a new record is created. > It looks like BMC accounted for this in the design because the Object > Modification record fails to create but is only a warning in DS. My hope > was the filter could specify client type and version in the Run If and > would prevent the DS change from taking place if the not a high enough API > level.**** > > **** > > Thought I would share the results.**** > > Jason**** > > **** > > [image: Inline image 1]**** > > On Wed, Feb 22, 2012 at 9:41 AM, Jonas Stumph Stevnsvig < > [email protected]> wrote:**** > > Hi listers > > I have a little question which bothers me, and I hope you can give me some > insight. > > The background: > We are about to go live with a new 7.6.04 sp2 environment. We have several > consultants, not all of which are familiar with overlays. We almost had a > catastrophe today with a person logging onto the new server with a 7.5 dev > studio. He did not get any warnings about base/overlay mode, and almost > wrecked a form by deleting fields from the wrong place. > > I am aware of the lowest api level, but our ITSM installation is still at > 7.6.00 so there are some old plugins at api level 7.5 (or thereabout). > > The Question: > How do I disallow dev studio connections < 7.6.04 without disallowing the > plugins? > > Any suggestions? > > Best regards > > Jonas > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"**** > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_**** > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
