1. xMatters
  2. Community
  3. Integrations & Toolchains

Javascript version

Chris Crocco
Not Yet Reviewed

Can someone tell me what javascript version xMatters is using? Can we use ES6 features?

0

Comments

7 comments
Date Votes

Please sign in to leave a comment.

  • Travis Depuy

    Hey Chris!

       Currently using EcmaScript 5.1 in the Nashorn Javascript Engine. So no :(

    Doc'd here if needed: http://help.xmatters.com/OnDemand/xmodwelcome/integrationbuilder/create-scripts.htm

    Anything in particular you were looking to use?

    Happy Monday!

    0
  • Chris Crocco

    Hey Travis, thanks! We were looking at string template literals and destructuring in particular:

    [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals
    [2] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment

    Both would be "nice to have's" for some of the stuff we are working on.

    0
  • Travis Depuy

    Yea, both of those failed with syntax errors when I ran them. I'll add a PM request to see about upgrading. I can't guarantee anything but we'll take a look. 

    PM-5302 added. 

    0
  • Kirk Friedman

    Hey Travis,

    Would it also make sense to include the javascript version along with the xMatters version so that folks know what Javascript features are available and what aren't?  Maybe at the top of the Developer tab or some lookup.

     

    Thanks,

    Kirk

    0
  • Doug Peete

    Some more context here:

    Our implementation of Javascript using Nashorn is based on our platform running on Java 8. Java 9 will have more ES6 support, but was expected to launch with partial support and then grow over time. That statement was made before Java 9 got delayed a few times. So I am not sure what the latest ES6 support looks like in Java 9, but GA isn't until July 27th. And then we'd want it to get beat on a fair amount before we'd think of transitioning our platform to Java 9.

    We looked at Node.JS, but our xMatters Agent needs to run Integration Builder processes, and it needs to support Windows. And from what we saw, Node.JS on Windows seems to be a bit... uh... finicky.

    AWS Lambda and Google Cloud Functions also looked interesting, but again doesn't help with the behind the firewall integration problems we need to solve.

    So with all of that said, I don't see us bringing in ES6 support until CY2018 when a Java 9 upgrade for our services makes sense.

    For supported Javascript versioning: we are thinking that makes the most sense as a message somewhere in the script editor. Maybe at the bottom in the footer area, or somewhere in the right hand pane. What do you think?

    0
  • Jan Karlsbjerg

    Hi Kirk

    It's a good idea to display the JS version (either directly or in a little information pop-up (the detailed description of the supported version on the page that Travis linked to is quite long)).

    I've written up an enhancement request for displaying the JS version and also a couple of other improvements to the UI of the script editor:

    • Restore the help icon -- it's currently lost because the script editor pops open as a full page overlay on top of the regular UI
    • Only list objects (such as the "event status updates" or "device delivery updates") that are actually available in the current situation (based on the trigger chosen)

    Jan

     

    0
  • Jan Karlsbjerg

    The above enhancements are all long since in the product now.

    0

Didn't find what you were looking for?

New post