Distribution – Overview

Distribution procedure

Distribution procedure 1. Get your API key To license and deploy Sigma Apps, you (or your organization) need to be registered as a Sigma App developer and obtain a public and private API key. To sign up, please send an email to: apideveloper@sigmaestimates.com [contact-form-7 id=”31284″ title=”Distribution procedure part 1″]   2. Get an App ID...

Package API

Manifest format The manifest is an XML file with a root element named sigma.package.manifest.The root node can contain the following child elements: Name Value Description id string, optional A unique ID; Either a script ID or a GUID. name string, optional Name of the package.For display in the user interface. version string, optional Installer package...

App Concepts

App Concepts Sigma Apps are used to extend the functionality in Sigma, and to integrate Sigma with either Webservices or Windows Desktop applications. Sigma end users will install the App, and experience something new in Sigma. Very much like apps on the smartphones. A Sigma App is a package of one or more of these...

Sigma Bundle Files

Sigma bundle files If the App includes any AppScript files, these must be compiled into a “Sigma bundle” file. This file is encrypted with your private API key and used for license control. When Sigma loads a licensed Sigma bundle file, it will contact the Sigma license server and validate the license. The user will...

Packages

Packages The Sigma App is a package (a single file) containing: A manifest file Installation files The manifest file describes the App ID, version and contents. Basically the file is a ZIP file, containing at least a file called install.xml, which is a manifest file describing everything else in the package. The extension of the...