Actions
Sign out
XpertAgent Blueprint Server
Manage blueprint access for XpertAgent Studio

Packs
Accounts
Information
Blueprint Name ID Description Version  
Account Name Access Key Pack Access Last seen  

Building Blueprint Packs

Blueprint packs are just plain zip files.

You can automatically build a pack of an existing template & super wizard combo via the "Export > Make into a blueprint pack" home screen burger menu
The builder assumes...

  • The template name and description are the pack name & description.
  • The pack version is the template version
  • The pack ID is the GUID of the template
  • The icon is either the knowledge base icon (or a default logo if not set)
  • The super-wizard file is derived via the template KB.
    Also, any files in the libraries/wizards folder which match the BASENAME of the tool .js file are also copied. e.g.
    "assess_super.js" would also include "assess_super.png" and "assess_super_large.png" etc. in the final blueprint zip

Example zip contents (n.b. the only mandatory file is an info.json in the root of the zip)... 

info.json
icon.png
template
   <contents of the template's [object] folder>
   appsettings.json
   dict.json
   etc.
tool
   <files to copy into the installation to support the blueprint (e.g. super wizzard)>
   super_wizard.js
   super_wizard.png

Example info.json... 

{
    "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx",
    "name": "FinAdvsor",
    "description": "Financial XpertAdvsor Builder",
    "version": "1.0"
}

When installing into XpertAgent Studio, the icon.png is retrieved and displayed alongside the pack name & description

When installing into the platform, a new template is created (identical to the one held in the template folder in the blueprint pack) and any files in the zip "tool" folder are copied into the libraries/wizards/custom folder