What type of records can be converted into a packageable format using the Copado Extension tool?(Select all that apply)

The Copado Extension tool is designed to bundle and distribute reusable Copado-specific configurations. Its primary purpose is to package automation assets that can be shared and installed in other Copado orgs. The main record types that can be converted into a packageable format using this tool are Functions (custom scripts) and Job Templates (sequences of automated steps). These components form the core building blocks of reusable processes within the Copado platform.

A. User Story records: User Stories are transactional records that track metadata changes for a specific requirement; they are not reusable configuration components to be packaged as an extension.

B. Apex Class: An Apex Class is a standard Salesforce metadata component. It is deployed to an org via a User Story, not packaged as a reusable Copado configuration with the Extension tool.

1. Copado Documentation, "Introduction to the Copado Extension Builder": This document explicitly states the purpose of the Extension Builder. It says, "With the Copado Extension Builder, you can create extensions to bundle and share your custom Functions and Job Templates." This directly confirms that Functions and Job Templates are the intended record types for packaging.

2. Copado Documentation, "Create and Bundle an Extension": This guide details the steps for creating an extension. The process involves selecting a Git repository and then adding components. The available components for selection are specified as Functions and Job Templates, reinforcing that these are the supported types.