That said, there are a number of options for getting your questions addressed:
- StackOverflow: For asking questions of the VersionOne Development Community.
- GitHub Issues: For submitting issues that others may try to address.
npm install v1jssdk
Getting Started With
sample.js on Node.js
To build the libraries, you'll need Node.js.
npm install # install dependencies npm run build # build distributable SDK
You can now run the sample against our public test instance by typing:
You can modify the info at the top of the script to point to your own VersionOne instance.
Experimental: Use from a web browser
We're also are experimenting with getting this to work from the web browser. Here's a public example that is running:
That script executes against a public instance of VersionOne that is hosted in Amazon.
The credentials for that instance are
That uses the
v1browsersdk.js file that you can find in this repository. In order
for the example to run in JSFiddle, it points to the one deployed to the gh-pages branch.
The other information on the gh-pages branch is currently out of date as of November 2nd, 2013.
v1browsersdk.js file is built by running this command:
Configure your own on-premise VersionOne instance to allow CORS requests
If you have your own on-premise installation, open the VersionOne
Web.config file and add the three entires
<add name="VersionOne" ... /> entry:
<httpProtocol> <customHeaders> <clear /> <add name="VersionOne" value="Enterprise/18.104.22.168; XP" /> <add name="Access-Control-Allow-Origin" value="*" /> <add name="Access-Control-Allow-Methods" value="GET,PUT,POST,DELETE,OPTIONS" /> <add name="Access-Control-Allow-Headers" value="Content-Type, Authorization" /> </customHeaders> </httpProtocol>
- ACKNOWLEDGEMENTS.md - Acknowledgments of included software and associated licenses
- LICENSE.md - License for source code and redistribution
- CONTRIBUTING.md - Guidelines and information on contributing to this project
Not into the chat thing? Get help from the community of VersionOne developers: