Publishing developer packages

Developer packages enable distribution and sharing of custom Python files used in flows, such as functions and libraries.

You can create a developer package by adding a developer package directory anywhere in the advanced view file explorer. Then, right-click the content directory and select Package. An .ibsolution file is generated at the same level as the solution directory with the name and version specified in the solution’s JSON metadata. Use Marketplace admin to publish the app to the Marketplace (All apps > Marketplace admin > Tools > Publish).

Developer package contents

Developer packages consist of the package payload stored in a src directory and a JSON file that includes package metadata. Developer packages can optionally include a README and screenshots.

├── solution
│   ├── src
│   ├── package.json
│   ├── README.md
│   ├── screenshots

Package payload

The package payload is a src directory that contains your custom Python files.

JSON file

A JSON file describes the solution metadata.

Required fields:

• name - Unique name for the developer package.

• version - Semantic version in major.minor.patch format.

• short_description - Short description that displays in the Marketplace.

• long_description - Long description of the developer package.

• authors - List of solution author or authors.

• accelerator_type - List of accelerator types: package.

• industry - List of industry tags: Financial Services, Healthcare, Insurance, Public Sector, or Shared Services.

• business_vertical - List of business verticals: Asset & Wealth Management, Business & Commercial Banking, Corporate & Investment Banking, or Retail & Consumer Banking.

• package_type - List of package tags: integration, refiner, step, or validation.

• function_type - List of function tags: formatting, integrations, machine learning, parsing, or validating.

Optional fields:

• icon_url - Path to optional icon. Always icon.png.

• beta - true adds a visual beta tag to the developer package.

• encryption_config - Dictionary that specifies the encryption protocol to use. The encryption_type must be specified with the value v1.

See the following sample package.json file for a custom library solution:

1
{
2
  "name": "ib_classifier_docsplitting",
3
  "version": "1.0.1",
4
  "short_description": "Classifier for variable-length document bundles",
5
  "long_description": "The docsplitting classifier learns to split a PDF bundle of documents, and predict the class of each document. Import FirstPageDocsplittingClassifier from docsplit_classifier in the solution.",
6
  "authors": [
7
        "Instabase"
8
    ],
9
  "accelerator_type": [
10
        "package"
11
    ],
12
  "industry": [],
13
  "business_vertical": [],
14
  "package_type": [
15
        "integration"
16
    ],
17
  "function_type": [
18
        "machine learning"
19
    ],
20
  "icon_url": "icon.png",
21
  "beta": true,
22
  "encryption_config": {
23
    "encryption_type": "v1"
24
  }
25
}

README

An optional README.md file that describes the solution package. The README might describe use cases, benefits, and instructions.

Screenshots

Optional screenshots in a screenshots/ folder illustrate how the solution works.