RPE and Office 365 VBA Macros disabled replacement strategy
DOORS 9 RPE users relying on post processing macros (ExpandWordOLEs for example) are facing 2 looming issues:
1. Security lockdown of Office 365 environments prohibiting the execution of macros (often even in "Trusted" locations)
2. EOL for VBA and macros in general (2027 is the latest I've heard)
It's getting to the point where even field codes in a document are being blocked.
Has anyone experimented with or implemented a forward strategy for replicating the functionality of what macros accomplish visibly, and behind the scenes? (Word export in DOORS 9.x, for instance relies on VBA to accomplish its job)
My projects have literally thousands of embedded OLE graphics and tables that need to be processed during compliance document generation.
M. Sutherland, where are you? Mark Murphy, anything to add to your post from https://jazz.net/forum/questions/267714/anyone-had-experience-of-using-office-365-with-doors-9
2 answers
Hi Cliff,
I am the author of the ExpandWordOLEs macro.
I think there's a misunderstanding on your part. Macros are a HUGE productivity time saver and MS can't deprecate them any time soon. They are looking to migrate the technology to other languages but we're years away.
I did some research and I think the misunderstanding comes down to VBScript vs. VBA:
-
VBScript Deprecation, Not VBA:.Microsoft has announced the deprecation of VBScript (Visual Basic Script), which is a separate scripting language from VBA, although they share a common lineage. This deprecation of VBScript will occur in phases, eventually leading to its removal from Windows.
-
VBA Remains Supported:.VBA is still a core component of desktop Office applications like Excel, Word, and Access. Microsoft recognizes the vast amount of existing VBA code supporting critical business processes and has stated that VBA will continue to be supported as long as Office applications are supported.
Regarding security -- there are ways to configure Word to allow macros to run seamlessly. You have to jump through hoops but this is a configuration setting in Word / Company Policy setting. Check the Trust Center Macro Settings outlined here:
Kevin Murphy
IBM Champion
Hey Kevin. Yep on all the above. Word as a locally installed app seems to have a better rate of success than Utilizing Office 365 (web based). My main purpose for the thread was to see what others are doing to mitigate the ever tightening blocking of macros, and legacy file types. Maybe that's too broad of a subject.