The MSPro Boomi Collection
About
Boomi Console
Boomi Console
  • Boomi Console
    • What is ...
  • Installation & Setup
    • Download & Install
    • Setup a Workspace
    • Connect your Workspace
    • Test your Workspace
  • Commands
    • COMP - Components
      • GET
      • DOC
    • PACK - Packaged Components
      • PACK GET
      • PACK DOC
    • DEPLOY - Deployments
      • GET - Deployments and Packages
      • EXEC - Deploy components
        • Deployment from Repos
        • Promotion to Env
      • DELETE - Undeploy Components
    • WORKSPACE CONNECT
    • ACCOUNT INFO
    • Arguments
      • Common Arguments
        • The Set Argument in Detail
        • Query Filter
          • Start date or time span
        • Arguments in a file
        • Allow Multi
        • Component Resolution
      • COMP Arguments
        • COMP GET Arguments
        • COMP DOC Arguments
      • PACK Arguments
      • DEPLOY Arguments
        • DEPLOY GET Arguments
        • DEPLOY EXEC Arguments
        • DEPLOY DELETE Arguments
  • Use-Cases
    • Analyze deployed components
    • Components in a Folder
    • Deploy Components
    • Reveal a Process
    • Reveal an API Component
    • Deployed Components Overview
    • Deployment Task Document
    • Create a cSet.jsonc file
  • Library
    • Component Set
      • The Components Set JsonC file
        • Create a package file
      • Set File resolution
    • The Report Engine
      • Render DataSets
        • DataSet Base
        • Component Metadata DataSet
          • Component Metadata Header
          • Component Metadata
          • CompDataSet With Counts
        • Deployed Packages DataSet
        • Package Content DataSet
        • Map Markdown Dataset
      • Components
        • Deployable Components
        • Orphaned Components
    • The Workspace
      • Manage your workspace
      • Components Set Workspace
      • Workspace folders
      • The project database
    • Configuration files
      • Application Settings
      • Workspace configuration file
      • boomiConsole.user.json
    • How to...
      • Use Excel to view CSV files
      • Local metadata and caching
      • Getting help
      • Environments
      • How to get a Component's Id
    • Referenced Pages
      • Lists
      • Documentation Snapshots
  • Download and Release History
  • Help Text
    • Documentation Links
    • Target Path Resolution
    • GitHub Emojis
    • Packaged Component and Versions
    • Components and Versions
    • Component Hierarchy
    • Referenced Components
Powered by GitBook
On this page
  1. Library

Component Set

Group several components into a logical set

Last updated 7 months ago

A (short: Set) is a Json file-based collection of components.

I - Markus Schmidt - invented this term and the idea behind, when I wanted to work with a collection (set) of components which I was editing during a sprint. A Component Set allowed me to deploy and to document my sprint output with a single reference to my working set.

You can look at Component Sets like project files. Instead of specifying multiple component Ids, you can put them into a Components Set. Component Sets are JsonC files (Json with Comments), which contain a set of components -> working set.

-> The Components Set JsonC file

Sets for APIs

You can also use Component Sets to group components that belong together, like APIs (API.JsonC) . You can then deploy or document all these components by using /s API argument

{
  "header": {
    "name": "NetSuite API Services" ,
    "packageVersions": [
      { "date": "2024-06-25", "author": "msc", "changes": [ "Created" ] }
    ]
  },
  "components": [
    { "deploy": true,  "hint" : "API.NetSuite",         "id" : "b4cbeef0-.."};

    { "deploy": false,  "hint" : "POST /purchaseOrder", "id" : "f5c4a6fa-..."},
    { "deploy": false,  "hint" : "GET  /purchaseOrder", "id" : "219c73ef-..."},
    { "deploy": false,  "hint" : "GET  /supplier",      "id" : "f61476d1-..."} 
  ]
}
Component Set