Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    4
  • Subscribers subscribers
    3
  • Views views
    419
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

For version control purposes, can I export/import SBM 10.1.1.3 appscripts and javascripts?

pbustin

I would like to be able to export and (less important) import appscripts and javascripts in SBM 10.1.1.3 so that I can use Version Manager to store the revisions. (Incidentally, I think VM requires that the script names not have spaces).
  • 0

    Check with Serena support for a ScriptExporter utility. Alternatively, you might be able to dig them out of the MSD (blueprint) file which, as you probably know, is just a zip.My own practice is to use a version control utility when developing AppScripts and JavaScripts. I create these as individual files outside of Composer using an editor like Notepad , do the version control at that stage, then import the code into Composer.
  • 0
    Hi @Paul , Does this Script exporter tool still exists ? (also does it have some import function ?)
  • 0
    Seems like the support have no Infos about this tool..:D
  • 0
    To match what Composer can do with verification, including knowing when $ INCLUDE matches the name of the calling or called script, I would have to copy and paste, verify, modify, and copy and paste again, but I guess that's OK.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.