--- title: Bundles slug: bundles icon: {"faIcon":"fa-solid fa-sack-dollar"} docTags: createdAt: 2025-11-11T23:22:48.601Z --- The Bundles capability provides a way for someone to fill in and submit more than one catalog item forms, as part of a collection, in one go. Example processes/use cases: 1. New starter/User onboarding: As part of an onboarding of a new starter, they may need a laptop, a mobile phone and access to various applications relevant to their role in the organization. You can configure individual catalog item forms for "Order a laptop", "Order a mobile phone" and "Request an application access" so you can submit them separately, but you can also have all of them included as part of a New starter bundle. 2. Hardware request: You may have individual catalog item forms to order a laptop, to order a tablet and to order a mobile phone. You may also have a catalog item form to order relevant accessories. However, as part of a hardware request process, you can configure a bundle for someone to fill the catalog item form to order the hardware, as well as a form to order relevant accessories. 3. Offboarding: As part of an offboarding of an employee or a contractor, the individual's line manager may need to submit a form for HR but also other forms IT purposes like retrieving and reimaging their laptops and mobile phone. :::hint{type="info"} You should consider having a single catalog item generating multiple subtasks if you are configuring for a single process, but you require multiple steps that are relatively straight forward to complete. An example is, if it is for a hardware request and you want to track the steps individually as separate record or ticket but they all follow the same status lifecycle and capture same set of information. You may have a subtask for Procurement team to buy the hardware, a subtask for IT to image the hardware, once received, and a subtask for Field services to provide the hardware to the requestor. If there are already individual catalog items with their own catalog forms and workflows that you want users to be able to order together as part of a process, then configuring a bundle for them may make sense. ::: # Overview What you need to be aware of with Bundles: 1. A bundle is also a catalog item, but has one or more catalog items (other than itself) "bundled" with it. Therefore, apart from configuring its bundled items, the rest of the bundle configuration is the same as a catalog item's configuration 2. Once a catalog item has at least one bundled item, it will automatically be marked as a "catalog bundle" 3. When a bundle is submitted: 1. The bundle itself will raise a parent record to all of the bundled items 2. Each of the bundled items will raise a record each, no different to when they are individually raised, outside of a bundle 4. Within both a catalog item's and its questions' configuration, it can be configured to check whether the catalog item is being filled in / submitted as part of a bundle or not # Initial configuration ## Creating a new bundle A bundle is created and configured the same way as a [Catalog Items](docId\:BFgJ8yNH1Hsi8ZaEyYoPc) ## Bundling catalog items To bundle one or more catalog items: :::::WorkflowBlock ::::WorkflowBlockItem Create the catalog item you want to be the bundle. Fill in the fields as needed just like you would when creating a regular catalog item. Go to the "Bundled items" tab and in the "Bundled item" field, select the catalog item(s) to bundle: :::hint{type="info"} You will need to pre-create the catalog items that you want to bundle ::: ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/oaAbkd1AhWOXFc0zXN4Dd_image.png) :::: :::WorkflowBlockItem Once you have finished adding to the Bundled item field, click Save on the catalog item. The bundled items would be displayed in the related list under the "Bundled item" field, and the catalog item having the bunded items had been automatically marked as a bundle. ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/-if0YxM2FgDZmX_ezpwGc_image.png) ::: :::WorkflowBlockItem For each Bundled item record on the related list of Bundled items, you can configure the below when you view the Bundled item entry on the related list: | **Field name** | **Description** | **Example value** | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | | Required | If this bundled item can / cannot be excluded from a bundle | Yes | | Order | How this bundled item is displayed relative to other bundled items. The lower order bundled items are displayed first relative to bundled items with higher order | 10 | | Precondition | Condition on when this bundled item is displayed. In the example, the "Order a laptop" catalog item will be available in the bundle if the bundle's question "HardwareRequired" is answered Yes | When a question asking if hardware is required, is answered Yes | | Precondition script | Using script, condition on when this bundled item is displayed | | ::Image[]{src="https://app.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/_bDyegO2K8xJE2RX9ojiY_image.png" size="60" width="3020" height="2714" position="center" showCaption="false"} ::: :::WorkflowBlockItem After the Order of each Bundled item is updated, the related list of the bundled items will update. An example is below showing their updated Orders: ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/eiAK2Xv6daJ4A98vWLdAA_image.png) ::: :::WorkflowBlockItem Once a catalog item has at least one bundled item, it will be automatically flagged as a bundle and you can find it under the Administration > Catalog > Catalog bundles navigation menu: ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/3d8-szCqmgYdt8ku_15Q9_image.png) ::: :::WorkflowBlockItem ::: ::::: # Usage :::::WorkflowBlock :::WorkflowBlockItem A bundle is presented with three tabs in order: 1. First tab called "Requirements", displays the bundles' questions 2. Second tab called "Details", displays all the individual bundled catalog item forms whose Precondition and Precondition script conditions are met. 3. Third tab called "Summary", displays the summary page prior to the bundle and bundled items submitted ::: :::WorkflowBlockItem Fill in the first tab. Responses to the first tab may decide which catalog form(s) is/are presented on the second tab. This is using the Precondition configuration on the Bundled item referred to above. ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/fPcxQQS_cx_JE2Uw76tp0_image.png) ::: :::WorkflowBlockItem Fill in the second tab where you will see each of the bundled items displayed as sub-tabs. Example below shows three bundled catalog items as part of the bundle. ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/xEOO6O7W6PZtsscNMhbNu_image.png) ::: :::WorkflowBlockItem Still in the second tab, go through each bundled catalog item and fill in all the mandatory questions as a minimum. ::: :::WorkflowBlockItem Once all the bundled catalog items' mandatory questions are filled in, when you click on "Next" at the bottom of the form, you will be taken to the final tab "Summary". Example below: ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/XQUg5UPK2WxTWQ9XMIqsR_image.png) ::: :::WorkflowBlockItem At any time if you need to go back to previous tabs (e.g. either Details or Requirements), you can left click on the tab's header. ::: ::::WorkflowBlockItem When you are ready to submit your bundle, click "Submit" button in the final tab. This will create: 1. A parent record for the submitted Bundle, and 2. A child record for each of the submited bundled item. Note that each of the bundled items will run their respective pre-configured workflows the same way if they are submitted individually outside of a bundle. :::hint{type="info"} In the example above, 5 ITSMRequest records will be submitted. 1 will be the parent with 4 as the children requests. ::: :::: ::::: # Copying question set values If you have common question sets between your bundles and your bundled items, the answers to those all of those common question sets' questions on the bundle, will copy over to the ones on the bundled items. ## Example - Requestor information You have a Question set collecting both Requestor and Requested for information, assigned to a bundle: ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/QietarkcLEsWSfLAPyAW9_image.png) If you associate the same question set to a bundled item and then answer the question set's questions on the catalog bundle: ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/Qj2NEhCoKaYjqU3I6C3Rm_image.png) The bundled item with the same question set will auto populate, with the answers copied over from the bundle's question set: ![](https://api.archbee.com/api/optimize/RDSPJwtKQ5B5sE-oMCN16/ImgDIbAU_Nz5UG8XrlCWH_image.png) # Advanced configuration For the following Catalog question's capabilities, they have access to know whether they are used by catalog items or questions sets part of catalog items, that are ordered as part of a bundle OR ordered as part of a single catalog item submission. :::hint{type="info"} If a question is part of a bundled request, it will have access the id of the bundle definition, via a variable called **bundleCatalogId** ::: ## Question's precondition script Example below is a precondition script that will display a catalog question, if the question is currently being loaded as part of a single catalog item request, not part of a bundled request ```javascript answer = !bundleCatalogId; ``` Example below is a precondition script that will display a catalog question, if the question is currently being loaded as part of a bundle. That bundle's definition record having an id of d8ac347fe86f811f09998ba183885ea88 ```javascript answer = bundleCatalogId == "d8ac347fe86f811f09998ba183885ea88"; ``` ## Question's default value script Example below is a catalog question's default value script that returns true if the question is currently being loaded as part of a bundle ```javascript let flag = false; if (bundleCatalogId) { flag = true; } answer = flag; ```