in2-agent-server 0.20260821.185429

package/reference/campfire-configuration-items-guide.md

@@ -0,0 +1,710 @@
+# Campfire Configuration Items Guide
+
+<!--
+PROVENANCE. Transcribed from VFP's "Campfire Configuration Items - Common Types Guide"
+(V12, 08 August 2025) and re-synced 2026-08-19 against the revision VFP's team sent that day.
+That revision changed exactly two things — it ADDED a `Named Credential` section and a `Role`
+section — and left every other section's field rules byte-identical. Both were already in
+CI_RULES (src/campfire/configItem.ts), added 2026-08-18 from the live restricted picklist after
+Renner's QA dropped three delivered Roles and a Named Credential from a writeback; the client
+doc has now caught up with what the org already accepted.
+
+The screenshots are not reproduced here, so where one carried a load-bearing fact the prose
+states it (see the Role note).
+-->
+
+## Campfire Configuration Items - Common Types Guide
+
+### Overview
+
+This document will outline the most common type of Configuration Items or metadata components that we use to solve the client requirements at VFP and that can be tracked in the Campfire application.
+
+The Configuration Items is a list of metadata components that the consultant has built for each system requirement on a given project.  One or more configuration items can be added to a requirement. This list is used as a checklist and manifests during deployment when the components created in the Salesforce test or sandbox environment are collectively deployed to other Salesforce environments. The configuration items list can be exported in a specific file format to be imported into a deployment tool like ClickDeploy to execute the deployment from one environment to another. At VFP, the deployment tool of choice is ClickDeploy.
+
+Below are the types of configuration items and how to enter these metadata components in the Campfire Configuration Items record.
+
+### Actions & Global Actions
+
+For Actions you will have to complete the following fields depending if it’s a Global Action or an Action inside an Object:
+
+- **Type:** QuickAction
+- **Configuration Item API Name:** The name of the Action
+- **Object API Name:** The object API name that holds the action (Only used if the Action is from an object, if it’s a global action then this field must be blank)
+
+You can get the name of the Action from a custom object by going to Setup - Object Manager - Opening your object and clicking on the Buttons, Links, and Actions tab:
+
+If it’s a Global Action you can get the name by going to Setup - Global Actions and finding your Global Action:
+
+Here is what a Configuration Item for Actions in objects looks like in Campfire:
+
+This is what it looks like for Global Actions:
+
+### Apex Classes
+
+To add Apex Classes you will have to complete the following fields:
+
+- **Type:** ApexClass
+- **Configuration Item API Name:** The Name of the Apex Class
+
+You can get the Apex Class Name by going to Setup - Apex Classes and reviewing the Name column of your ApexClass:
+
+### Apex Triggers
+
+To add Apex Triggers you will have to complete the following fields:
+
+- **Type:** ApexTrigger
+- **Configuration Item API Name:** The Name of the Apex Trigger
+
+You can get the Apex Trigger Name by going to Setup - Apex Classes and reviewing the Name column of your ApexTrigger:
+
+### Approval Processes
+
+For Approval Processes you will have to complete the following fields:
+
+- **Type:** Approval Process
+- **Configuration Item API Name:** the Unique Name of the Approval Process
+- **Object API Name:** the Object API Name that holds the approval process
+
+You can get the Unique Name of the Approval Process by going to Setup - Approval Processes and opening your approval process:
+
+Here is what a Configuration Item for Approval Process looks like in Campfire:
+
+### Apps / Lightning Page Assignments
+
+For Apps and/or Lightning Page Assignments you will have to complete the following fields:
+
+- **Type:** App
+- **Configuration Item API Name:** The Developer Name of your app
+
+You can find the Developer name of your app by going to Setup - App Manager and finding your app:
+
+Lightning Page Assignments aren't directly deployable. To move them to a new org, you must include the associated app in your deployment. For example, to deploy the first line of Lightning Page assignments in the screenshot, you need to add the QTC - Project Management app as an App Configuration Item.
+
+Here is how a Configuration Item for Apps should look like in Campfire:
+
+### Buttons
+
+For Custom Buttons you will have to complete the following fields:
+
+- **Type:** WebLink
+- **Configuration Item API Name:** the name of the custom button
+- **Object API Name:** The Object API Name of the object that holds the button
+
+You can get the button name by going to Setup - Object Manager - Opening your object and clicking on the Buttons, Links and Actions tab:
+
+Here is how a good Configuration Item for Custom Buttons looks like in Campfire:
+
+### Compact Layouts
+
+For Compact Layouts you will need to complete the following fields:
+
+- **Type:** CompactLayout
+- **Configuration Item API Name:** The API name of the Compact Layout
+- **Object API Name:** The API name of the object that holds the Compact Layout.
+
+You can find the API Name of the Compact Layout by navigating to Setup - Object Manager - Clicking on your object and clicking the Compact Layout tab:
+
+Here is what a Configuration Item for Compact Layouts looks like in Campfire:
+
+### Conditional Field Formatting on Lightning Pages
+
+For Conditional Field Formatting on Lightning Pages you will need to complete the following fields:
+
+- **Type:** UiFormatSpecificationSet
+- **Configuration Item API Name:** The API name of the Conditional Formatting
+
+You can get the API name of the Conditional Formatting by navigating to the Object Page - Conditional Field Formatting and copying the API Name column:
+
+### Custom Fields
+
+For adding custom fields you must complete the following fields:
+
+- **Type:** CustomField
+- **Configuration Item API Name:** The API name of the custom field
+- **Object API Name:** The API name of the Object that holds the Custom Field
+
+You can get the API Name of the field by navigating to Setup - Object Manager - Search for your object - Fields & Relationships and finding the Custom Field:
+
+You can find the Object API Name by clicking on the Details tab:
+
+Here is what a good Custom Field Configuration Item looks like in Campfire:
+
+API Names for Custom Fields and Object API Names MUST ALWAYS end with __c if it’s custom (this rule also applies for Certinia OOB fields), this formatting doesn’t apply if the field or the object are OOB (Out-of-the-box) from Salesforce.
+
+### Custom Fields (Custom Metadata Types)
+
+To add custom fields from Custom Metadata Types you must complete the following fields:
+
+- **Type:** CustomField
+- **Configuration Item API Name:** The API name of the custom field
+- **Object API Name:** The API name of the Custom Metadata Type that holds the Custom Field.
+
+You can get the API name of your custom fields by navigating to your Custom Metadata Type and reviewing the Custom Fields section:
+
+### Custom Fields (Custom Settings)
+
+To add custom fields you must complete the following fields:
+
+- **Type:** CustomField
+- **Configuration Item API Name:** The API name of the custom field
+- **Object API Name:** The API name of the Custom Settings that holds the Custom Field.
+
+You can get the Custom Field API Name by going to the Custom Settings and reviewing the fields:
+
+### Custom Labels
+
+To add Custom Labels you need to complete the following fields:
+
+- **Type:** CustomLabel
+- **Configuration Item API Name:** The API name of the Custom Label
+
+You can get the name of the Custom Label by going to Setup - Custom Labels and reviewing the Name column:
+
+### Custom Metadata
+
+Custom Metadata are records that belong to a Custom Metadata Type
+
+In order to add Custom Metadata as Configuration Items in Campfire you will need to complete the following fields:
+
+- **Type:** CustomMetadata
+- **Configuration Item API Name:** The API name of the Custom Metadata
+- **Object API Name:** The API Name of the Custom Metadata Type that holds the Custom Metadata
+
+You can get the API Name of the Custom Metadata by going to Setup - Custom Metadata Types - clicking on the Manage Records button from your Custom Metadata Type and reviewing the Name column:
+
+### Custom Metadata Fields
+
+In order to add custom fields from a Custom Metadata Type as Configuration Items in Campfire you will need to complete the following fields:
+
+- **Type:** CustomFIeld
+- **Configuration Item API Name:** The API name of the Custom Metadata Field
+- **Object API Name:** The API name of the Custom Metadata Type that holds the custom field
+
+You can get the API name of the Custom Metadata Field by navigating to Setup - Custom Metadata Type - Opening the Custom Metadata Type and reviewing the API Name column under Custom Fields:
+
+### Custom Metadata Types
+
+In order to add Custom Metadata Types as Configuration Items in Campfire you will need to complete the following fields:
+
+- **Type:** CustomObject
+- **Configuration Item API Name:** The API Name of the Custom Metadata Type
+
+You can get the API Name of the Custom Metadata Type by going to Setup - Custom Metadata Types and reviewing the API name column:
+
+### Custom Metadata Validation Rules
+
+In order to add Validation Rules from a Custom Metadata Type as Configuration Items in Campfire you will need to complete the following fields:
+
+- **Type:** ValidationRule
+- **Configuration Item API Name:** The API name of the Validation Rule
+- **Object API Name:** The API name of the Custom Metadata Type that holds the Validation Rule
+
+You can get the API name of the Validation Rule by navigating to Setup - Custom Metadata Type - Opening the Custom Metadata Type and reviewing the Rule Name column under the Validation Rules section:
+
+### Custom Notifications
+
+In order to add Custom Notifications Configuration Items in Campfire you will need to complete the following fields:
+
+- **Type:** CustomNotificationType
+- **Configuration Item API Name:** The API Name of the Custom Notification
+
+You can get the API Name of the Custom Notifications by navigating to Setup - Custom Notifications and reviewing the API Name column:
+
+### Custom Objects
+
+In order to add Custom Objects as Configuration Items in Campfire you will need to complete the following fields:
+
+- **Type:** CustomObject
+- **Configuration Item API Name:** The API name of the Object
+
+You can get the Object API Name by going to Setup - Object Manager - Open your object and clicking on the Details tab:
+
+Here is what a good Configuration Item for Custom Object looks like in Campfire:
+
+### Custom Permissions
+
+To add Custom Permissions you need to complete the following fields:
+
+- **Type:** CustomPermission
+- **Configuration Item API Name:** The API name of the Custom Permission
+
+You can get the API name of the Custom Permissions by going to Setup - Custom Permission and seeing the Name column of your Custom Permission:
+
+### Custom Settings
+
+In order to add Custom Settings as Configuration Items in Campfire you will need to complete the following fields:
+
+- **Type:** CustomObject
+- **Configuration Item API Name:** The API name of the Custom Setting
+
+You can get the Custom Settings API Name by going to Setup - Custom Settings and opening your Custom Settings:
+
+### Dashboard Folder
+
+For Dashboard Folder you will have to complete the following fields:
+
+- **Type:** DashboardFolder
+- **Configuration Item API Name:** The Developer Name of the folder
+
+You can get the Developer Name of the folder by navigating to the folder, clicking the arrow icon and clicking on Rename:
+
+### Dashboards
+
+For Dashboards you will have to complete the following fields:
+
+- **Type:** Dashboard
+- **Configuration Item API Name:** The Developer Name of your dashboard
+- **Report / Dashboard Folder API Name:** The unique name of the folder that contains the Dashboard
+
+You can’t get the Dashboard’s Developer Name by conventional means so you have to run this query, you can get both the Developer Name and the name of the folder with this query:
+
+SELECT DeveloperName, Folder.DeveloperName FROM Dashboard WHERE Title = ‘The name of your dashboard’
+
+Remember to also include as a Configuration Item the folder that contains the Dashboard.
+
+### Declarative Lookup Summaries (DRLS)
+
+For DRLS triggers you will need to complete the following fields:
+
+- **Type:** CustomMetadata
+- **Configuration Item API Name:** The API name of your DRLS
+- **Object API Name:** dlrs__LookupRollupSummary2
+
+You can get the API name of the DRLS directly in the DRLS app in Salesforce:
+
+Here is how a DRLS configuration item should look like in Campfire:
+
+### Duplicate Rules / Matching Rules
+
+For Duplicate Rules or Matching Rules you will need to complete the following fields:
+
+- **Type:** DuplicateRule or MatchingRule
+- **Configuration Item API Name:** The API name of your Duplicate Rule or Matching Rule
+- **Object API Name:** The API of the object that holds the duplicate rule or matching rule
+
+You can get the API name of your matching rule by going to Setup - Matching Rules and opening your Matching Rule:
+
+Getting the Duplicate Rules API Name is a little bit more complicated in Salesforce UI but you can run this simple query to get it:
+
+SELECT DeveloperName FROM DuplicateRule WHERE MasterLabel = 'YOUR DUPLICATE RULE NAME'
+
+Here is how a Campfire Configuration Item for Duplicate Rules or Matching Rules looks like in Campfire:
+
+### Email Templates
+
+For Email Templates you will have to complete the following fields:
+
+- **Type:** Email Templates
+- **Configuration Item API Name:** The unique name of your Email Template
+- **Report / Dashboard Folder API Name:** The unique name of the folder that contains the Email Template. If your template folder is the standard OOTB public folder then just put unfiled$public in this field
+
+You can get the Unique Name from the Email Template by going to Setup - Classic Email Templates - Opening your Email Template and checking the Unique Name field:
+
+You can also get the Email Template Unique Name and the Email Template Folder Unique Name by running this query:
+
+SELECT Folder.DeveloperName, DeveloperName FROM EmailTemplate WHERE DeveloperName = ‘EMAIL TEMPLATE UNIQUE NAME’
+
+### Email Templates Folder
+
+For Email Templates you will have to complete the following fields:
+
+- **Type:** EmailTemplateFolder
+- **Configuration Item API Name:** The developer name of your Email Template Folder
+
+You can get the developer name of your Email Template Folder by running this query:
+
+SELECT Folder.DeveloperName, DeveloperName FROM EmailTemplate WHERE DeveloperName = ‘EMAIL TEMPLATE UNIQUE NAME’
+
+The Folder.DeveloperName column is the Developer Name of the Email Template Folder
+
+### Field Sets
+
+For Field Sets you will have to complete the following fields:
+
+- **Type:** FieldSet
+- **Configuration Item API Name:** The API Name of the Field Set
+- **Object API Name:** The API Name of the object that holds the Field Set
+
+You can get the API Name of the Field Set by going to Setup - Object Manager - Open your object and clicking on the Field Set tab:
+
+Here is what a good Configuration Item for Field Sets looks like in Campfire:
+
+### Flows
+
+For Flows you will have to complete the following fields:
+
+- **Type:** Flow
+- **Configuration Item API Name:** The API name of your flow
+
+You can get the API name of your flow by going to Setup - Flows - Opening your Flow and clicking the Save As Button:
+
+Here is what a Configuration Item for Flows should look like in Campfire:
+
+### Global Value Sets (Picklist Global VAlues)
+
+For Global Value Setsyou will have to complete the following fields:
+
+- **Type:** GlobalValueSet
+- **Configuration Item API Name:** The API name of the picklist global value set
+
+You can get the API name of the Global Value Set by going to Setup - Picklist Value Sets Opening your Value Set and copying the Name field:
+
+### Lightning Pages
+
+For Lightning Pages you will have to complete the following fields:
+
+- **Type:** LightningPage
+- **Configuration Item API Name:** The API name of your page.
+
+You can get the API name of the page by going to the Page Builder of your page and you should be able to find the API name on the right side of the screen:
+
+Here is what a Configuration Item for Lightning Pages should look like in Campfire:
+
+### List View Button Layout
+
+List View Button Layouts are not deployable individually, you will have to deploy the Custom or Standard object that contains the List View Button Layout.
+
+In order to add Custom Objects as Configuration Items in Campfire you will need to complete the following fields:
+
+- **Type:** CustomObject
+- **Configuration Item API Name:** The API name of the Object
+
+You can get the Object API Name by going to Setup - Object Manager - Open your object and clicking on the Details tab:
+
+Here is how the Configuration Item should look like:
+
+### List Views
+
+Here are the fields that you need to complete for List Views:
+- **Type:** ListView
+- **Configuration Item API Name:** The API Name of the list view
+- **Object API Name:** The Object API Name of the object that holds the List View
+
+You can get the List View API Name by navigating to the list view, clicking on the Gear icon, and then on the Rename button:
+
+**
+
+Here is what a Configuration Item for List Views should look like in Campfire:
+
+### Muting Permission Sets
+
+For Muting Permission Sets, you will have to complete the following fields:
+
+- **Type:** MutingPermissionSet
+- **Configuration Item API Name:** The API name of the Muting Permission Set
+
+You can find the API Name of the Muting Permission Set by navigating to the Permission Set Group that contains the Muting Perm Set - Muting Permission Sets in Group and copying the Muting Permission Set Name column:
+
+### Named Credential
+
+For Named Credential you will need to complete the following fields:
+
+- **Type:** NamedCredential
+- **Configuration Item API Name:** The Name of the Named Credential
+
+### Page Layouts
+
+For Page Layouts you will need to complete the following fields:
+
+- **Type:** Layout
+- **Configuration Item API Name:** The name of the page layout
+- **Object API Name:** The API name of the object that holds the page layout.
+
+You will have to use the Page Layout regular label that you can find under Setup - Object Manager - Opening your Object and clicking on the Page Layouts tab:
+
+Here is what a Configuration Item for Page Layouts looks like:
+
+> **Note:** If you were to deploy OOTB Certinia Page Layout or other package Page Layouts, make sure to append the package prefix at the beginning of the Configuration Item API Name:
+
+### Paths
+
+For Paths you will have to complete the following fields:
+
+- **Type:** PathAssistant
+- **Configuration Item API Name:** The API Name of the path
+
+You can get the API Name of the path by navigating to Setup - Path - Click Edit on the Path - Review the API Name field:
+
+### Permission Set Groups
+
+For Permission Set Groups you will have to complete the following fields:
+
+- **Type:** PermissionSetGroup
+- **Configuration Item API Name:** The API name of you Permission Set Group
+
+You can find the API name of your Permission Set Group by going to Setup - Permission Set Groups and finding your Permission Set Group:
+
+Here is how a Configuration Item for Permission Set Groups should look like in Campfire:
+
+> **Note:** If you were to deploy OOTB Certinia Permission Set Groups or other package PSGs, make sure to append the package prefix at the beginning of the Configuration Item API Name:
+
+### Permission Sets
+
+For Permission Sets you will have to complete the following fields:
+
+- **Type:** PermissionSet
+- **Configuration Item API Name:** The API Name of the Permission Set
+
+You can find the API name of the Permission Set by going to Setup - Permission Sets - Opening your Permission Set and clicking on the Edit Properties button:
+
+Here is what a Configuration Item for Permission Sets should look like in Campfire:
+
+### Profiles
+
+For Profiles you will have to complete the following fields:
+
+- **Type:** Profile
+- **Configuration Item API Name:** The name of your profile
+
+You can find the name of your profile by going to the Setup - Profiles and finding your profile:
+
+Here is how a Configuration Item for Profiles should look like in Campfire:
+
+### Public Groups
+
+For Public Groups  you will have to complete the following fields:
+
+- **Type:** Group
+- **Configuration Item API Name:** The API name of your group
+
+You can find the API Name of your Public Group by going to Setup - Public Groups and opening the Public Group:
+
+Here is how a Configuration Item for Public Groups should look like in Campfire:
+
+### Record Types
+
+For Record Types you will have to complete the following fields:
+
+- **Type:** RecordType
+- **Configuration Item API Name:** The Record Type Name
+- **Object API Name:** The API name of the Object that holds the Record Type.
+
+You can get the Record Type Name by going to Setup - Object Manager - Open your Object and click on the Record Types tab:
+
+Here is what a Configuration Item for Record Types should look like in Campfire:
+
+### Role
+
+For Roles you will have to complete the following fields:
+
+- **Type:** Role
+- **Configuration Item API Name:** The Role Name
+
+> **Note:** the guide illustrates this with the Setup - Roles - Role Edit page, with the **Role Name** field ringed — the developer/API name (e.g. `CEO`), which sits directly under **Label** and is a separate field from it. Use Role Name, not the label, and not "Role Name as displayed on reports".
+
+### Report Types
+
+For Report Types you will have to complete the following fields:
+
+- **Type:** ReportType
+- **Configuration Item API Name:** The name of your report type
+
+You can get the report type’s name by going to Setup - Report Type and finding your Report Type:
+
+Here is how a Configuration Item for Report Types looks like in Campfire
+
+### Reports
+
+For Reports you will have to complete the following fields:
+
+- **Type:** Report
+- **Configuration Item API Name:** The Unique Name of your report
+- **Report / Dashboard Folder API Name:** The unique name of the folder that contains the report. If your report is from the public folder, use unfiled$public as the folder API Name
+
+You can find the unique name of the report folder by navigating to the reports tab, finding your report folder and clicking on the Rename button:
+
+You can get the Report Name by navigating to the report - Edit and clicking on the Properties button:
+
+You can also get the Name by running this query:
+
+SELECT DeveloperName FROM Report WHERE Name  = 'The Name of your Report'
+
+Here is how a Configuration Item for Reports should look like:
+
+### Sharing Rules
+
+For Sharing Rules you will have to complete the following fields:
+
+- **Type:** SharingCriteriaRule or SharingOwnerRule (depending on whether it is a criteria-based or owner-based sharing rule)
+- **Object API Name:** The API name of the Object that holds the Sharing Rule
+- **Configuration Item API Name:** The API Name of the Sharing Rule
+
+You can get the Sharing Rule API Name by going to Setup - Sharing Settings - scrolling down to your specific object's Sharing Rules section and clicking Edit on the Rule:
+
+### Sharing Sets
+
+For Experience Site’s Sharing Sets you need the following fields:
+
+- **Type:** SharingSet
+- **Configuration Item API Name:** The API Name of the Sharing Set
+
+To get the API Name of the Sharing Set, navigate to Setup - Digital Experiences - Settings - Open the Sharing Set - Grab the Sharing Set Name field:
+
+### Standard Fields
+
+For adding standard fields you must complete the following fields:
+
+- **Type:** StandardField
+- **Configuration Item API Name:** The API name of the standard field
+- **Object API Name:** The API name of the Object that holds the standard Field
+
+You can get the API Name of the field by navigating to Setup - Object Manager - Search for your object - Fields & Relationships and finding the Standard Field
+
+### Tabs
+
+For Tabs you will need to complete the following fields:
+
+- **Type:** Tab
+- **Configuration Item API Name:** the Name of the Tab (The spaces must be replaced with underscores)
+
+If the Tab is from a Custom Object, then the Configuration Item Name must end with __c
+Example: Campfire_Requirements__c
+
+You can get the name of the Tab by going to Setup - Tabs and opening your tab:
+
+Here is what a Configuration Item for Tabs looks like in Campfire:
+
+### Validation Rules
+
+Validation Rules work almost the same as page layouts. You will need the name of the Validation Rule and the Object API Name of the object that holds the validation rule.
+
+You will have to complete the following fields on the Configuration Item:
+
+- **Type:** ValidationRule
+- **Configuration Item API Name:** Name of the Validation Rule
+- **Object API Name:** The API Name of the Object that holds the validation rule
+
+You can get the Validation Rule name by going to Setup - Object Manager - Finding your object and clicking on the Validation Rules tab:
+
+Here is what a Configuration Item for Validation Rules looks like in Campfire:
+
+### Visualforce Pages
+
+To add Visualforce Pages  you will have to complete the following fields:
+
+- **Type:** ApexPage
+- **Configuration Item API Name:** The Name of the Visualforce Page
+
+You can get the Visualforce Page name by navigating to Setup - Visualforce Pages and reviewing the name column of your Visualforce Page:
+
+### Workflow Email Alert
+
+For Workflow Email Alerts, you will have to complete the following fields:
+
+- **Type:** WorkflowEmailAlert
+- **Configuration API Name:** the API name of the Workflow Email Alert
+- **Object API Name:** the API name of the object that holds the Workflow Email Alert
+
+### Workflow Field Updates
+
+For Workflow Field Updates, you will have to complete the following fields:
+
+- **Type:** WorkflowFieldUpdate
+- **Configuration API Name:** the API name of the workflow field update
+- **Object API Name:** the API name of the object that holds the workflow field update
+
+Here is how a good Configuration Item for Workflow Field Updates looks like in Campfire:
+
+### Workflow Outbound Messages
+
+For Workflow Outbound Messages you will have to complete the following fields:
+
+- **Type:** WorkflowOutboundMessage
+- **Object API Name:** The API name of the object linked to the Outbound Message
+- **Configuration Item API Name:** The unique name of your Workflow Outbound Message
+
+You can get the Workflow Outbound Message name by going to Setup - Outbound Messages - Opening your outbound message and reviewing the Unique Name field:
+
+## Certinia Components
+
+Components from Certinia like Navigation Menus, Cards Panels, Highlights, etc are not deployable since these components are data.
+
+In order to keep track of these tasks, create a Campfire Deployment Task for the Requirement and mark it as Pre-Deployment.
+
+Like mentioned before, these components are actually data so records exist within the system. It’s possible to export them from the Source Org and then Import them into the Target Org by following these steps:
+
+Export the data using the Salesforce Inspector in the Source Org.
+
+Export query: SELECT fferpcore__ItemType__c, fferpcore__Label__c,
+fferpcore__LargeData__c, Name FROM fferpcore__exp_configurationItem__c
+
+Once you have the data export, you can copy it to an Excel format:
+
+After copying the data, go to the target org and use the data import from the Inspector:
+
+Paste the data in the text box and click Run Insert:
+
+Once the data has been imported, confirm on the front-end that everything is working correctly.
+
+## How to use Campfire Config Items with CLickDeploy
+
+### Exporting your Configuration Items
+
+There are several ways to export your Configuration Items, you can use reports, queries or other tools
+
+In this case, we will use SOQL using the Salesforce Inspector Chrome extension since it’s the faster way.
+
+Once you are on the Salesforce Inspector data export screen, you can write the following query to quickly gather your configuration items:
+
+SELECT ClickDeploy_Text__c from Campfire_Configuration_Item__c where Requirement__r.Name = 'You Requirement Number'
+
+If you want to grab the Configuration Items from various Requirements then you can use the IN statement:
+
+SELECT ClickDeploy_Text__c from Campfire_Configuration_Item__c WHERE Requirement__r.Name IN ('Your Requirement Number', 'Your Requirement Number', 'Your Requirement Number')
+
+If you want to get all the Configuration Items that are linked to Requirements from a particular Project, you can run this query:
+
+SELECT ClickDeploy_Text__c FROM Campfire_Configuration_Item__c WHERE Requirement__r.Project__r.Name = 'the name of the project'
+
+If you want to get all the Configuration Items from a particular Build Cycle, you can run this query:
+
+SELECT ClickDeploy_Text__c FROM Campfire_Configuration_Item__c WHERE Requirement__r.Campfire_Build_Cycle__r.Name = 'The name of the Build Cycle' AND Requirement__r.Project__r.Name = 'The Name of the Project'
+
+Once you have the data, let’s click the Copy (Excel Format) button and let’s paste this into a sheet:
+
+> **Tip:** You can quickly create a new spreadsheet in Google Sheets by using the shortcut CMD + T in Mac or Control + T in Windows, typing sheet.new and pressing enter:
+
+Once we have the sheet opened, let’s paste our data into the sheet:
+
+Once the data is pasted into the sheet, it’s time to copy our configuration Items:
+
+### Importing to ClickDeploy
+
+Once we have the configuration items copied, we can log in to ClickDeploy and import the data.
+
+Create a new deployment and set up your source org and your target org:
+
+Once you are inside the deployment, click More and then Import Components Selections:
+
+Paste your Configuration Items inside the text box and click Import:
+
+A success window will appear and your components will be added to the Deployment:
+
+After adding your components, be sure to validate the deployment and address any issues that arise.
+
+However, keep in mind that a "Validated Deployment" doesn’t necessarily mean everything is included. ClickDeploy may validate a deployment successfully while still having invalid components.
+
+Invalid components are indicated by this symbol in the Diff column:
+
+These validation errors may indicate that the component does not exist in the target org or that ClickDeploy couldn’t locate it due to incorrect ClickDeploy Text in the Configuration Item.
+In such cases, reach out to the configuration owner of the Requirement associated with the problematic Configuration Item. Ask them to identify the exact component that needs to be added.
+
+## Examples of Dependencies and considerations for Deployments
+
+There are certain dependencies that need to be taken into consideration when deploying.
+
+Some of these dependencies are:
+
+Permission Sets / Profiles & Custom Fields: If you have a permission set or profile that contains access to a field that doesn’t exist in the target org then your deployment will fail. Make sure to add that custom field to your deployment.
+Reports / Dashboards: Reports and dashboards must have a folder, make sure to also deploy their respective folders.
+Lightning Pages with List Views, Flows or Certinia Custom Components: If you have a lightning page that contains an embedded screen flow, then that screen flow must also be added to the deployment, it’s also the same situation with List Views added to Lightning Pages. Certinia Custom Components like Cards Panels, Highlights Panels, etc are NOT DEPLOYABLE and will have to be re-created in the Target Org with the exact Name that they have in the Source Org
+Flows & Custom Fields: if you have a flow that uses custom fields that don’t exist in the target org, the deployment will fail. Make sure to add those missing custom fields to the deployment.
+Flows & Custom Objects: If you are going to deploy a Flow that contains a custom object like Record Triggered Flow then make sure that the Custom Object is added to the deployment or confirm that it already exists in the target org.
+Field Sets & Custom Fields: If you are going to be deploying a field set, make sure that the fields that are part of said Field Set are added to the deployment or they already exist in the target org.
+Approval Processes & Workflow Field Updates or Workflow Email Alerts: If you are deploying an Approval Process that has one or multiple Workflow Field Updates or Workflow Email Alerts in it then those Workflow Field Updates and/or Workflow Email Alerts must also be in the deployment or must exist in the Target Org already.
+
+Some of these considerations are:
+
+Flows: Flows get deployed as inactive most of the time. If it’s a new version of an existing flow from the target org then the latest version of that flow must be activated. You can keep track of these action items as Deployment Tasks on the corresponding Requirement.
+API Name Changes: Changes to API names of existing components in the Target Org are NOT DEPLOYABLE. ClickDeploy will take them as new components instead of existing ones. Example: If you have an Object called RADTest Requirement in the target org and you change the API name of that object in the Source Org and deploy it, ClickDeploy will create a new object instead of updating the existing one from your Target Org.
+V12 08 August 2025