Flexicious is licensed on a per developer basis. For Single Domain licenses, we require the domain information (or the app name in case of AIR apps) when we create your build.

Flexicious Setup Workflow:

  • You purchase Flexicious via our website.
  • We send you a link to request your build
  • Once this link is submitted, we generate your build, and you receive an email with the SWC and instructions on deploying the Console. Please read this carefully.
  • You install the console, and request a license
  • We send you the license file, which you then deploy to the console

Some Frequently asked questions:

1) What is the Flexicious Console?
a. Flexicious Console is a small AIR app that will manage your license information, show recent blog posts, notify you of current build version and latest build available.

2) I have purchased multiple developer licenses. Do each of my developers need to request a build?
a.  No, the same SWC should be used for all developers. However, each of your flex developers will need to install the Flexicious Console, and request and deploy their respective licenses. Instructions for this are in the build email.

3) When I receive an updated build (new version released, etc), do I need to reinstall the license/Flexicious Console?
a. No, the console should not be uninstalled. The console and license file deployment is a onetime process. Usually, all that needs to be done when a new build is published is to replace the old swc with the new one.

3) What should I do when my licensed domain changes?
a. Just request a new build with the appropriate domain information and mention the domain change in the notes. We will send you an updated swc with the new domain.

4) Do I need to deploy any license to the webserver/server where my air/flex app is hosted?
a. No. The licensing mechanism kicks in ONLY when the swc detects that it is running inside a Flash Debug player, with localhost or file based URLS. No licensing code executes (except the domain check for single domain customers) on non-debug players or when the browser path is not local. 

5) How is the domain licensing implemented?
a. Domain licensing : This is only applicable to Single Domain Customers. The domain is licensed when you request a build. One of the fields on the “Request A Build” page is the domain you wish to license. We usually allow upto 3 domains, assuming they are DEVELOPMENT/PROD/QA instances of the same application. This is independent of the developer licensing.

6) How does the developer licensing work?
a.  Developer Licensing : This is implemented via the usage of the console. Each developer who runs Flexicious in debug mode on localhost/file URLS  needs to have the Console installed. When you install the Flexicious Console, you should see a button to send us a license request. This captures information from your system that is used to generate the license hash. Once your request is processed, you are sent a file  with the name flexicious.license. Instructions on deployment are included in the email.

For issues deploying the license file:

When you run Flexicious on localhost, using Flash Debug Player, you must have the Flexicoius Console installed, with the license file deployed. The server tab text area should display "License validated. Starting License Server...License Server Started ... ". If you do not see this text, this means you do not have a license installed. There should be a button that says "Request License". Click this button and fill out the form. Once we receive this request and verify your informaiton. we will send you a license file to deploy. If you run into issues when you deploy the license file, please follow the steps below before contacting support.:

  1. First, ensure that your license was issued within the past 72 hours.
  2. Ensure that you are using the same user to deploy the license that you did to request it
  3. If you have verified all of the above, and deploying the file does not change the status of the license textbox, just quit the Console, Place the license file next to the console exe (Usually C:\Program Files\FlexiciousConsole or C:\Program files (x86)\FlexiciousConsole), and then restart the console. Note to MAC users : The license file must be placed next to the swf like shown in the screenshot here
  4. Restart the machine.

If none of the above work, this could indicate a corrupt license file, please reach out to our support in this scenario.

Issues building from the source

For those of you who are having issues compiling the library from Source (Source Customers only - Site/Enterprise), there are 2 known FYIs:

1) Known Issue compiling compilation issue with com.flexicious.nestedtreedatagrid.automation.FlexDataGridAutomationImpl

Resolution - The Automation Files have been moved out to a different Library. Please delete this file to resolve the compilation issue.

2) Unable to open Included file "../../../../../../FlexGrid/includes/StatePersistenceInclude.as"

Resolution - This error will appear if the Classic and Ultimate source files are extracted to the same level. By default, Ultimate is one level below Classic, so if you have extracted them to the same directory, just remove an extra "../". Also, you may need to change FlexGrid to ClassicLib in the path. Typically, the path should look like this : include "../../../../../ClassicLib/includes/StatePersistenceInclude.as";

Update: For 3.0 and later, we have moved all the includes to a common location.

//please download all the includes from http://flexicious.com/allincludes.zip, extract to some folder on your drive, and replace c:/code/flxssrc with the appropriate path

//please search the workspace for C:/Code/flxssrc/, there are a number of locations where the files are imported. 

3) For those of you compiling the Flex 3 version of the source, ensure you change the isFlex3 to true and isFlex4 to false in the compilation parameters. (You can do so via Right click on project, properties, Flex Compiler, and this needs to be done for both Classic and Ultimate). Finally, for Flex 3, under the root of the projects, there should be a file called defaults3.css. (for both Classic and Ultimate). The contents of this file should be copied and pasted into the defaults.css located next to each file.

4) For compiling the Dashboard source files, please make sure you add the Ultimate project or Classic project as a reference. There are a number of files in Dashbload library that are also path dependent on where you extract the referenced Classic/Ultimate files, so you may need to repeat step 2) for these same.Also, please use SDK 4.5 or higher to compile dashboard.

We have also run into some incompatibility issues that were introduced because Adobe changed the way they want the design.xml formatted for Flex Builder 4.5. Please bear with us while we update our build mechanism and verify compatibility to account for all the different builder vs sdk version variations being forced upon us. In the interim, what this means is the following.

If you see the following error: "Could not resolve <flxs:FlexDataGrid> to a component implementation", just replace the following in the component declaration: xmlns:flxs="http://www.flexicious.com/2011" with xmlns:flxs="com.flexicious.nestedtreedatagrid.*" :

Also, if you notice that autocomplete (intellisense) is not working:

you can always manually import the namespaces as such:

xmlns:flxs="com.flexicious.nestedtreedatagrid.*" (For Ultimate)

xmlns:grids="com.flexicious.grids.*"  (For Classic)

xmlns:controls="com.flexicious.controls.*" (For the extended basic controls like TextInput, MSCB)

An example import will look like (for Flex 4):

<mx:VBox xmlns:fx="http://ns.adobe.com/mxml/2009"
         xmlns:mx="library://ns.adobe.com/flex/mx" width="100%" height="100%"
         xmlns:controls="com.flexicious.controls.*"          xmlns:flxs="com.flexicious.nestedtreedatagrid.*">