@salesforce/afv-skills 1.22.0 → 1.24.0

package/skills/getting-metadata-api-context/data/metadata_api/ExtlClntAppPushSettings.json

@@ -1,93 +0,0 @@
-{
-  "sections": [
-    "title",
-    "description",
-    "file_information",
-    "directory_location",
-    "fields",
-    "sub_types",
-    "wsdl_segment"
-  ],
-  "title": "ExtlClntAppPushSettings - Metadata API",
-  "description": "Represents an external client app’s push notification settings.",
-  "file_information": ".ecaPush",
-  "directory_location": "extlClntAppPushSettings",
-  "fields_columns": [
-    "type",
-    "description"
-  ],
-  "fields": {
-    "androidPushConfig": {
-      "type": "ExtlClntAppAndroidPushConfig",
-      "description": "Represents the push notification configuration of an Android mobile app."
-    },
-    "applePushConfig": {
-      "type": "ExtlClntAppApplePushConfig",
-      "description": "Represents the push notification configuration of an iOS mobile app."
-    },
-    "externalClientApplication": {
-      "type": "string",
-      "description": "The name of the associated external client app.",
-      "required": true
-    },
-    "label": {
-      "type": "string",
-      "description": "Label for the external client app’s push notifications configuration."
-    },
-    "pushConfigLink": {
-      "type": "string",
-      "description": "Identifies the push notification credentials used by the app. Valid format is the org ID (for example, 00D000000000001 ) and an ExtlClntAppApplePushConfig or ExtlClntAppAndroidPushConfig record ID (for example, 1Dh000000000001 ) separated by a colon. For example: 00D000000000001:1Dh000000000001 If you configure pushConfigLink, you can’t also have androidPushConfig or applePushConfig in the same record."
-    },
-    "pushServiceType": {
-      "type": "PushServiceType (enumeration of type string)",
-      "description": "Identifies the mobile operating system of the mobile app. Valid values are: Apple Android",
-      "required": true
-    }
-  },
-  "sub_types": {
-    "ExtlClntAppAndroidPushConfig": {
-      "fcmProject": {
-        "type": "string",
-        "description": "The ID of the Google Firebase project associated with the mobile app.",
-        "required": true
-      },
-      "serviceAccount": {
-        "type": "string",
-        "description": "The Base64-encoded Admin SDK private key for your Google Firebase service account. You can generate this key from the Service accounts tab in the Google Firebase console. The maximum length of the string is 8000 characters.",
-        "required": true
-      }
-    },
-    "ExtlClntAppApplePushConfig": {
-      "applicationBundle": {
-        "type": "string",
-        "description": "The bundle ID of the iOS mobile app from Apple App Store Connect."
-      },
-      "certificate": {
-        "type": "string",
-        "description": "The Base64-encoded TLS certificate with Apple Push Notification service (APNs) enabled. To generate and export this certificate, see Communicate with APNs using a TLS certificate in Apple Developer documentation."
-      },
-      "environment": {
-        "type": "ApplePushEnvironmentType (enumeration of type string)",
-        "description": "The Apple Push Notification service environment. Valid values are: Production Sandbox",
-        "required": true
-      },
-      "keyIdentifier": {
-        "type": "string",
-        "description": "The key identifier for the private key entered in the signingKey field. See Get a key identifier in Apple Developer documentation."
-      },
-      "password": {
-        "type": "string",
-        "description": "The password for the TLS certificate entered in the certificate field."
-      },
-      "signingKey": {
-        "type": "string",
-        "description": "The Base64-encoded private key with Apple Push Notification service (APNs) enabled. To generate and download this key, see Create a private key to access a service in Apple Developer documentation."
-      },
-      "teamIdentifier": {
-        "type": "string",
-        "description": "The team ID listed in the membership details of the Apple Developer account associated with the iOS mobile app."
-      }
-    }
-  },
-  "wsdl_segment": "```xml\n<xsd:simpleType name=\"ApplePushEnvironmentType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"Sandbox\"/>\n    <xsd:enumeration value=\"Production\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:complexType name=\"ExtlClntAppAndroidPushConfig\">\n  <xsd:sequence>\n    <xsd:element name=\"fcmProject\" type=\"xsd:string\"/>\n    <xsd:element name=\"serviceAccount\" type=\"xsd:string\"/>\n  </xsd:sequence>\n</xsd:complexType>\n<xsd:complexType name=\"ExtlClntAppApplePushConfig\">\n  <xsd:sequence>\n    <xsd:element name=\"applicationBundle\" minOccurs=\"0\" type=\"xsd:string\"/>\n    <xsd:element name=\"certificate\" minOccurs=\"0\" type=\"xsd:string\"/>\n    <xsd:element name=\"environment\" type=\"tns:ApplePushEnvironmentType\"/>\n    <xsd:element name=\"keyIdentifier\" minOccurs=\"0\" type=\"xsd:string\"/>\n    <xsd:element name=\"password\" minOccurs=\"0\" type=\"xsd:string\"/>\n    <xsd:element name=\"signingKey\" minOccurs=\"0\" type=\"xsd:string\"/>\n    <xsd:element name=\"teamIdentifier\" minOccurs=\"0\" type=\"xsd:string\"/>\n  </xsd:sequence>\n</xsd:complexType>\n<xsd:complexType name=\"ExtlClntAppPushSettings\">\n  <xsd:complexContent>\n    <xsd:extension base=\"tns:Metadata\">\n      <xsd:sequence>\n        <xsd:element name=\"androidPushConfig\" minOccurs=\"0\" type=\"tns:ExtlClntAppAndroidPushConfig\"/>\n        <xsd:element name=\"applePushConfig\" minOccurs=\"0\" type=\"tns:ExtlClntAppApplePushConfig\"/>\n        <xsd:element name=\"externalClientApplication\" type=\"xsd:string\"/>\n        <xsd:element name=\"label\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"pushConfigLink\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"pushServiceType\" type=\"tns:PushServiceType\"/>\n      </xsd:sequence>\n    </xsd:extension>\n  </xsd:complexContent>\n</xsd:complexType>\n<xsd:complexType name=\"Metadata\">\n  <xsd:sequence>\n    <xsd:element name=\"fullName\" minOccurs=\"0\" type=\"xsd:string\"/>\n  </xsd:sequence>\n</xsd:complexType>\n<xsd:simpleType name=\"PushServiceType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"Apple\"/>\n    <xsd:enumeration value=\"Android\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n```"
-}

package/skills/getting-metadata-api-context/data/metadata_api/ExtlClntAppSamlConfigurablePolicies.json

@@ -1,119 +0,0 @@
-{
-  "sections": [
-    "title",
-    "description",
-    "file_information",
-    "directory_location",
-    "fields",
-    "sub_types",
-    "wsdl_segment",
-    "declarative_metadata_sample_definition"
-  ],
-  "title": "ExtlClntAppSamlConfigurablePolicies - Metadata API",
-  "description": "Represents SAML configuration policies for an external client app. Use this type to configure Salesforce as an identity provider for SAML single sign-on (SSO). In this type of SSO configuration, users log in to a third-party service provider, such as Google, using their Salesforce credentials.",
-  "file_information": ".ecaSamlPlcy",
-  "directory_location": "extlClntAppSamlConfigurablePolicies",
-  "fields_columns": [
-    "type",
-    "required",
-    "description"
-  ],
-  "fields": {
-    "acsUrl": {
-      "type": "string",
-      "required": true,
-      "description": "The assertion consumer service (ACS) URL from the third-party service provider. The ACS URL is the endpoint where the service provider receives SAML responses from Salesforce."
-    },
-    "certificate": {
-      "type": "string",
-      "description": "A security certificate that the third-party service provider uses to sign SAML requests. Include this field only if your service provider signs SAML requests and you also want to use a service provider-initiated SAML flow. If you include a certificate, Salesforce requires that all SAML requests from the service provider are signed. If you don't include a certificate, Salesforce accepts all SAML requests, whether or not they're signed."
-    },
-    "commaSeparatedPermissionSet": {
-      "type": "string",
-      "description": "A comma-separated list of permission set IDs that defines the user permissions required for an end user to use the SAML SSO flow. The permission sets that you specify here apply to the entire app, not just its SAML configuration."
-    },
-    "commaSeparatedProfile": {
-      "type": "string",
-      "description": "A comma-separated list of profile IDs that defines the profiles required for an end user to use the SAML SSO flow. Like permission sets, profiles define user permissions. The profiles that you specify here apply to the entire app, not just its SAML configuration. We recommend that you use permission sets to manage user permissions instead of profiles."
-    },
-    "customAttributes": {
-      "type": "ExtlClntAppSamlConfigurablePoliciesAttribute[]",
-      "description": "Custom attributes that you can use to send more information about the user in SAML responses. For example, send information about the user's country. The service provider can use the information to validate the user's identity."
-    },
-    "encryptionCertificate": {
-      "type": "string",
-      "description": "A certificate that's used to encrypt SAML assertions that Salesforce sends to the service provider. Use an X.509 certificate that's saved in your Certificate and Key Management settings. To get the certificate, work with a certificate provider. If you include an encryptionCertificate, make sure that your service provider is configured to decrypt SAML assertions."
-    },
-    "encryptionType": {
-      "type": "ExtlClntAppSamlEncryptType",
-      "description": "If you include an encryptionCertificate to encrypt SAML assertions, the encryptionType field specifies the encryption method. When the service provider receives SAML assertions from Salesforce, it detects this method and decrypts it. These values are valid. AES_128—Advanced Encryption Standard (AES) encryption algorithm with a 128-bit cryptographic key. AES_256—AES encryption algorithm with a 256-bit cryptographic key. For more information about AES encryption from the National Institute of Standards and Technology, see https://www.nist.gov/publications/advanced-encryption-standard-aes-0."
-    },
-    "entityUrl": {
-      "type": "string",
-      "required": true,
-      "description": "The entity ID from the third-party service provider. The entity ID is a globally unique ID that Salesforce uses to recognize the service provider."
-    },
-    "externalClientApplication": {
-      "type": "string",
-      "required": true,
-      "description": "The label for the parent ExternalClientApplication."
-    },
-    "issuer": {
-      "type": "string",
-      "description": "Specifies the URI from which Salesforce sends SAML responses. The service provider uses this value to confirm that the response came from Salesforce. If you don't include this field, Salesforce uses your My Domain by default. Include this field to specify a different value, such as an Experience Cloud site URL."
-    },
-    "label": {
-      "type": "string",
-      "description": "A name for your external client app SAML policies configuration."
-    },
-    "nameIdFormat": {
-      "type": "ExtlClntAppNameIdFormatType",
-      "description": "Specifies the format of the user's SSO identifier (dictated by the value of the subjectType field) in SAML messages. So that the service provider can recognize the user, the name ID format that Salesforce uses for SAML responses must match the format that the service provider uses. Get this value from your service provider. These values are valid. Unspecified (default)—No format. EmailAddress—The user's identifier is formatted as an email address. Persistent—The user's identifier is in an opaque format. Only Salesforce and the service provider can recognize it. The identifier doesn't change based on context. Transient—Like the Persistent identifier, the user's identifier is in an opaque format. But Transient identifiers are temporary values that can change."
-    },
-    "signingAlgorithmType": {
-      "type": "ExtlClntAppSamlSignAlgoType",
-      "description": "The signing algorithm that Salesforce uses to secure SAML messages. The signing algorithm generates a signature by hashing the private key that's stored in the certificate. Salesforce includes this signature in the SAML response—in both the response body and in the SAML assertion. When the service provider receives SAML responses, it validates the signature. Salesforce also applies this algorithm to single logout requests and responses. These values are valid. SHA1—Secure Hash Algorithm (SHA) 1 algorithm, which generates a 160-bit hash value. SHA256—SHA-256 algorithm,which generates a 256-bit hash value."
-    },
-    "singleLogoutBindingType": {
-      "type": "ExtlClntAppSamlBindingType",
-      "description": "The SAML HTTP binding type that the service provider uses when it initiates single logout. The binding type determines how the service provider transfers HTTP information to Salesforce. These values are valid. PostBinding–The service provider uses POST requests for single logout. RedirectBinding—The service provider sends single logout requests through the browser via GET requests."
-    },
-    "singleLogoutUrl": {
-      "type": "string",
-      "description": "The SAML single logout endpoint on the service provider. When Salesforce initiates single logout, it sends logout requests to this endpoint."
-    },
-    "startUrl": {
-      "type": "string",
-      "description": "A URL where users are directed after they authenticate. For example, direct users to a specific page in the service provider app. Deprecated. Use the startUrl field on the ExtlClntAppConfigurablePolicies metadata type instead."
-    },
-    "subjectCustomAttribute": {
-      "type": "string",
-      "description": "If the subjectType is CustomAttribute, specify which field you want to use to identify the user. Choose an existing field on the User object, or create a custom User field."
-    },
-    "subjectType": {
-      "type": "ExtlClntAppSamlSubjectType",
-      "description": "Specifies the user's SSO identifier. These values are valid. Username—The user's Salesforce username. FederationId—The user's federation ID, which maps to the FederationIdentifier—A field on the User object. The federation ID can be any value as long as both Salesforce and the service provider can recognize it. For example, get a value from the service provider and then specify it in Salesforce. UserId—The user's 15-character Salesforce user ID. CustomAttribute—An identifier that's taken from a custom field value. Specify the custom field in the subjectCustomAttribute field. PersistentId—An opaque identifier that only Salesforce and the service provider recognize."
-    }
-  },
-  "sub_types": {
-    "ExtlClntAppSamlConfigurablePoliciesAttribute": {
-      "formula": {
-        "type": "string",
-        "required": true,
-        "description": "A field that stores the user information that you want to send. Format the value as $<object name>.<field>.For example: $Organization.Country to indicate the Country field on the Organization object."
-      },
-      "key": {
-        "type": "string",
-        "required": true,
-        "description": "A unique name for the attribute to help you and the service provider recognize it in SAML responses."
-      }
-    }
-  },
-  "wsdl_segment": "```xml\n<xsd:simpleType name=\"ExtlClntAppNameIdFormatType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"Unspecified\"/>\n    <xsd:enumeration value=\"EmailAddress\"/>\n    <xsd:enumeration value=\"Persistent\"/>\n    <xsd:enumeration value=\"Transient\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:simpleType name=\"ExtlClntAppSamlBindingType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"RedirectBinding\"/>\n    <xsd:enumeration value=\"PostBinding\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:complexType name=\"ExtlClntAppSamlConfigurablePolicies\">\n  <xsd:complexContent>\n    <xsd:extension base=\"tns:Metadata\">\n      <xsd:sequence>\n        <xsd:element name=\"acsUrl\" type=\"xsd:string\"/>\n        <xsd:element name=\"certificate\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"commaSeparatedPermissionSet\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"commaSeparatedProfile\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"customAttributes\" minOccurs=\"0\" maxOccurs=\"unbounded\" type=\"tns:ExtlClntAppSamlConfigurablePoliciesAttribute\"/>\n        <xsd:element name=\"encryptionCertificate\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"encryptionType\" minOccurs=\"0\" type=\"tns:ExtlClntAppSamlEncryptType\"/>\n        <xsd:element name=\"entityUrl\" type=\"xsd:string\"/>\n        <xsd:element name=\"externalClientApplication\" type=\"xsd:string\"/>\n        <xsd:element name=\"issuer\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"label\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"nameIdFormat\" minOccurs=\"0\" type=\"tns:ExtlClntAppNameIdFormatType\"/>\n        <xsd:element name=\"signingAlgorithmType\" minOccurs=\"0\" type=\"tns:ExtlClntAppSamlSignAlgoType\"/>\n        <xsd:element name=\"singleLogoutBindingType\" minOccurs=\"0\" type=\"tns:ExtlClntAppSamlBindingType\"/>\n        <xsd:element name=\"singleLogoutUrl\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"subjectCustomAttribute\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"subjectType\" minOccurs=\"0\" type=\"tns:ExtlClntAppSamlSubjectType\"/>\n      </xsd:sequence>\n    </xsd:extension>\n  </xsd:complexContent>\n</xsd:complexType>\n<xsd:complexType name=\"ExtlClntAppSamlConfigurablePoliciesAttribute\">\n  <xsd:sequence>\n    <xsd:element name=\"formula\" type=\"xsd:string\"/>\n    <xsd:element name=\"key\" type=\"xsd:string\"/>\n  </xsd:sequence>\n</xsd:complexType>\n<xsd:simpleType name=\"ExtlClntAppSamlEncryptType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"AES_128\"/>\n    <xsd:enumeration value=\"AES_256\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:simpleType name=\"ExtlClntAppSamlSignAlgoType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"SHA1\"/>\n    <xsd:enumeration value=\"SHA256\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:simpleType name=\"ExtlClntAppSamlSubjectType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"Username\"/>\n    <xsd:enumeration value=\"FederationId\"/>\n    <xsd:enumeration value=\"UserId\"/>\n    <xsd:enumeration value=\"SpokeId\"/>\n    <xsd:enumeration value=\"CustomAttribute\"/>\n    <xsd:enumeration value=\"PersistentId\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:complexType name=\"Metadata\">\n  <xsd:sequence>\n    <xsd:element name=\"fullName\" minOccurs=\"0\" type=\"xsd:string\"/>\n  </xsd:sequence>\n</xsd:complexType>\n```",
-  "declarative_metadata_sample_definition": [
-    {
-      "description": "The following is an example of an ExtlClntAppSamlConfigurablePolicies component.",
-      "code": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<ExtlClntAppSamlConfigurablePolicies xmlns=\"http://soap.sforce.com/2006/04/metadata\">\n    <acsUrl>https://www.<serviceprovideracsurl>.com</acsUrl>\n    <entityUrl>https://www.<serviceproviderentityid>.com</entityUrl>\n    <externalClientApplication>mySamlEca</externalClientApplication>\n    <issuer>https://mydomainname.my.salesforce.com</issuer>\n    <label>myeca_samlpolicies</label>\n    <nameIdFormat>Unspecified</nameIdFormat>\n    <singleLogoutUrl>https://www.<serviceprovidersinglelogouturl>.com</singleLogoutUrl>\n    <singleLogoutBindingType>RedirectBinding</singleLogoutBindingType>\n    <subjectType>CustomAttribute</subjectType>\n    <subjectCustomAttribute>MyCustomField</subjectCustomAttribute>\n    <certificate>MIIDzDCCArQCCQCFaZKGsGqZ...</certificate>\n    <encryptionCertificate>MIIDzDCCArQCCQCFaZKGsGqZ...</encryptionCertificate>\n    <encryptionType>AES_128</encryptionType>\n    <signingAlgorithmType>SHA1</signingAlgorithmType>\n    <customAttributes>\n        <key>User Firstname</key>\n        <formula>$User.FirstName</formula>\n    </customAttributes>\n    <customAttributes>\n        <key>User Country</key>\n        <formula>$User.Country</formula>\n    </customAttributes>\n</ExtlClntAppSamlConfigurablePolicies>"
-    }
-  ]
-}

package/skills/getting-metadata-api-context/data/metadata_api/FeatureParameterBoolean.json

@@ -1,47 +0,0 @@
-{
-  "sections": [
-    "title",
-    "description",
-    "file_information",
-    "directory_location",
-    "fields",
-    "sub_types",
-    "declarative_metadata_sample_definition"
-  ],
-  "title": "FeatureParameterBoolean - Metadata API",
-  "description": "Represents a boolean feature parameter in the Feature Management App (FMA). Feature parameters let you drive app behavior and track activation metrics in subscriber orgs that install your package. This type extends the Metadata metadata type and inherits its fullName field.",
-  "file_information": ".featureParameterBoolean",
-  "directory_location": "featureParameters",
-  "fields_columns": [
-    "type",
-    "description"
-  ],
-  "fields": {
-    "dataFlowDirection": {
-      "type": "FeatureParameterDataFlowDirection",
-      "description": "After a package containing the components is installed, indicates whether the feature parameter’s value is editable in your License Management Org (LMO) and read-only in your customer’s org or the other way around."
-    },
-    "masterLabel": {
-      "type": "string",
-      "description": "The feature parameter name that appears in the user interface."
-    },
-    "value": {
-      "type": "boolean",
-      "description": "The default value for this feature parameter. You can reference this value in your code, just like you reference other values in a subscriber’s org."
-    }
-  },
-  "sub_types": {
-    "FeatureParameterDataFlowDirection": {
-      "FeatureParameterDataFlowDirection": {
-        "type": "string",
-        "description": "After a package containing the components is installed, indicates whether the feature parameter’s value is editable in your License Management Org (LMO) and read-only in your customer’s org or the other way around. LmoToSubscriber SubscriberToLmo"
-      }
-    }
-  },
-  "declarative_metadata_sample_definition": [
-    {
-      "description": "The following is an example of a FeatureParameterBoolean component.",
-      "code": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<FeatureParameterBoolean xmlns=\"http://soap.sforce.com/2006/04/metadata\">\n    <dataflowDirection>SubscriberToLmo</dataflowDirection>\n    <masterLabel>Budget Tracking Enabled</masterLabel>\n    <value>false</value>\n</FeatureParameterBoolean>"
-    }
-  ]
-}

package/skills/getting-metadata-api-context/data/metadata_api/FeatureParameterDate.json

@@ -1,47 +0,0 @@
-{
-  "sections": [
-    "title",
-    "description",
-    "file_information",
-    "directory_location",
-    "fields",
-    "sub_types",
-    "declarative_metadata_sample_definition"
-  ],
-  "title": "FeatureParameterDate - Metadata API",
-  "description": "Represents a date feature parameter in the Feature Management App (FMA). Feature parameters let you drive app behavior and track activation metrics in subscriber orgs that install your package. This type extends the Metadata metadata type and inherits its fullName field.",
-  "file_information": ".featureParameterDate",
-  "directory_location": "featureParameters",
-  "fields_columns": [
-    "type",
-    "description"
-  ],
-  "fields": {
-    "dataFlowDirection": {
-      "type": "FeatureParameterDataFlowDirection",
-      "description": "After a package containing the components is installed, indicates whether the feature parameter’s value is editable in your License Management Org (LMO) and read-only in your customer’s org or the other way around."
-    },
-    "masterLabel": {
-      "type": "string",
-      "description": "The feature parameter name that appears in the user interface."
-    },
-    "value": {
-      "type": "date",
-      "description": "The default value for this feature parameter. You can reference this value in your code, just like you reference other values in a subscriber’s org."
-    }
-  },
-  "sub_types": {
-    "FeatureParameterDataFlowDirection": {
-      "FeatureParameterDataFlowDirection": {
-        "type": "string",
-        "description": "After a package containing the components is installed, indicates whether the feature parameter’s value is editable in your License Management Org (LMO) and read-only in your customer’s org or the other way around. LmoToSubscriber SubscriberToLmo"
-      }
-    }
-  },
-  "declarative_metadata_sample_definition": [
-    {
-      "description": "The following is an example of a FeatureParameterDate component.",
-      "code": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<FeatureParameterDate xmlns=\"http://soap.sforce.com/2006/04/metadata\">\n    <dataflowDirection>SubscriberToLmo</dataflowDirection>\n    <masterLabel>Activation Date</masterLabel>\n    <value>2017-10-23</value>\n</FeatureParameterDate>"
-    }
-  ]
-}

package/skills/getting-metadata-api-context/data/metadata_api/FeatureParameterInteger.json

@@ -1,47 +0,0 @@
-{
-  "sections": [
-    "title",
-    "description",
-    "file_information",
-    "directory_location",
-    "fields",
-    "sub_types",
-    "declarative_metadata_sample_definition"
-  ],
-  "title": "FeatureParameterInteger - Metadata API",
-  "description": "Represents an integer feature parameter in the Feature Management App (FMA). Feature parameters let you drive app behavior and track activation metrics in subscriber orgs that install your package. This type extends the Metadata metadata type and inherits its fullName field.",
-  "file_information": ".featureParameterInteger",
-  "directory_location": "featureParameters",
-  "fields_columns": [
-    "type",
-    "description"
-  ],
-  "fields": {
-    "dataFlowDirection": {
-      "type": "FeatureParameterDataFlowDirection",
-      "description": "After a package containing the components is installed, indicates whether the feature parameter’s value is editable in your License Management Org (LMO) and read-only in your customer’s org or the other way around."
-    },
-    "masterLabel": {
-      "type": "string",
-      "description": "The feature parameter name that appears in the user interface."
-    },
-    "value": {
-      "type": "int",
-      "description": "The default value for this feature parameter. You can reference this value in your code, just like you reference other values in a subscriber’s org."
-    }
-  },
-  "sub_types": {
-    "FeatureParameterDataFlowDirection": {
-      "FeatureParameterDataFlowDirection": {
-        "type": "string",
-        "description": "After a package containing the components is installed, indicates whether the feature parameter’s value is editable in your License Management Org (LMO) and read-only in your customer’s org or the other way around. LmoToSubscriber SubscriberToLmo"
-      }
-    }
-  },
-  "declarative_metadata_sample_definition": [
-    {
-      "description": "The following is an example of a FeatureParameterInteger component.",
-      "code": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<FeatureParameterInteger xmlns=\"http://soap.sforce.com/2006/04/metadata\">\n    <dataflowDirection>SubscriberToLmo</dataflowDirection>\n    <masterLabel>Current Project Count</masterLabel>\n    <value>42</value>\n</FeatureParameterInteger>"
-    }
-  ]
-}

package/skills/getting-metadata-api-context/data/metadata_api/FieldMappingConfig.json

@@ -1,43 +0,0 @@
-{
-  "sections": [
-    "title",
-    "description",
-    "fields"
-  ],
-  "title": "FieldMappingConfig - Metadata API",
-  "description": "Represents the configuration for fields mapped between a source object and one or more destination objects and fields. This object is available in API version 63.0 and later.",
-  "fields_columns": [
-    "type",
-    "description"
-  ],
-  "fields": {
-    "Description": {
-      "type": "textarea",
-      "description": "The description of the field mapping configuration."
-    },
-    "DeveloperName": {
-      "type": "string",
-      "description": "The unqiue name for FieldMappingConfig."
-    },
-    "Language": {
-      "type": "picklist",
-      "description": "The language of the FieldMappingConfig. Possible values are: da—Danish de—German en_US—English es—Spanish es_MX—Spanish (Mexico) fi—Finnish fr—French it—Italian ja—Japanese ko—Korean nl_NL—Dutch no—Norwegian pt_BR—Portuguese (Brazil) ru—Russian sv—Swedish th—Thai zh_CN—Chinese (Simplified) zh_TW—Chinese (Traditional)"
-    },
-    "MasterLabel": {
-      "type": "string",
-      "description": "Label for the FieldMappingConfig."
-    },
-    "NamespacePrefix": {
-      "type": "string",
-      "description": "The namespace prefix associated with this object. Each Developer Edition organization that creates a managed package has a unique namespace prefix. Limit: 15 characters. You can refer to a component in a managed package by using the namespacePrefix__componentName notation. The namespace prefix can have one of the following values: In Developer Edition organizations, the namespace prefix is set to the namespace prefix of the organization for all objects that support it. There is an exception if an object is in an installed managed package. In that case, the object has the namespace prefix of the installed managed package. This field’s value is the namespace prefix of the Developer Edition organization of the package developer. In organizations that are not Developer Edition organizations, NamespacePrefix is only set for objects that are part of an installed managed package. There is no namespace prefix for all other objects."
-    },
-    "ProcessType": {
-      "type": "picklist",
-      "description": "Specifies the type of process that the field mapping configuration supports. Possible values are: ChangeRequest GiftEntry Incident Problem The default value is GiftEntry."
-    },
-    "SourceObjectId": {
-      "type": "picklist",
-      "description": "The ID of the source object for all of the fields mapped in the configuration. Possible values are: GiftEntry"
-    }
-  }
-}

package/skills/getting-metadata-api-context/data/metadata_api/FieldRestrictionRule.json

@@ -1,80 +0,0 @@
-{
-  "sections": [
-    "title",
-    "description",
-    "file_information",
-    "directory_location",
-    "fields",
-    "wsdl_segment",
-    "declarative_metadata_sample_definition"
-  ],
-  "title": "FieldRestrictionRule - Metadata API",
-  "description": "Represents a field visibility rule that controls whether a field is visible to a user, based on the field’s inclusion in a field set. If Enhanced Personal Information Management setting was enabled before Spring ’22, field visibility is based on the field’s compliance categorization. This type extends the Metadata metadata type and inherits its fullName field.",
-  "file_information": ".rule",
-  "directory_location": "fieldRestrictionRules",
-  "fields_columns": [
-    "type",
-    "description"
-  ],
-  "fields": {
-    "active": {
-      "type": "boolean",
-      "description": "Indicates whether the rule is active (true) or not (false). The default value is false."
-    },
-    "classification": {
-      "type": "string[]",
-      "description": "The data classification compliance categorization or field set that is targeted by the rule. The rule applies to fields that are marked with this categorization or included in this field set. If you enabled Enhanced Personal Information Management before Spring ‘22 (API version 54.0), you can use Salesforce's default compliance categorization values or values that you add yourself. If you enabled Enhanced Personal Information Management after Spring ‘22 (API version 54.0), use the PersonalInfo_EPIM field set or a field set that you add yourself.",
-      "required": true
-    },
-    "classificationType": {
-      "type": "ClassificationType (enumeration of type string)",
-      "description": "The type of classification method used in your org. If you enabled Enhanced Personal Information Management before Spring ‘22 (API version 54.0), use ComplianceCategory. If you enabled Enhanced Personal Information Management after Spring ‘22, use FieldSet. ComplianceCategory— FieldSet— The default value is ComplianceCategory. Available in API version 54.0 and later."
-    },
-    "description": {
-      "type": "string",
-      "description": "The description of the rule.",
-      "required": true
-    },
-    "enforcementType": {
-      "type": "EnforcementType (enumeration of type string)",
-      "description": "The type of rule. Possible values are: FieldRestrict—Field visibility rule. Only this value is valid. Restrict—Do not use. Scoping—Do not use.",
-      "required": true
-    },
-    "masterLabel": {
-      "type": "string",
-      "description": "The name of the rule.",
-      "required": true
-    },
-    "recordFilter": {
-      "type": "string",
-      "description": "The criteria that determine which fields are visible to the specified users. For example, the field can check if the logged-in user matches the Employee’s ID.",
-      "required": true
-    },
-    "targetEntity": {
-      "type": "string",
-      "description": "The object for which you're creating the rule. Only the Employee and User objects are supported.",
-      "required": true
-    },
-    "userCriteria": {
-      "type": "string",
-      "description": "The users that this rule applies to, such as all active users or users with a specified role or profile.",
-      "required": true
-    },
-    "version": {
-      "type": "int",
-      "description": "The rule's version number.",
-      "required": true
-    }
-  },
-  "wsdl_segment": "```xml\n<xsd:simpleType name=\"ClassificationType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"ComplianceCategory\"/>\n    <xsd:enumeration value=\"FieldSet\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:simpleType name=\"EnforcementType\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"Scoping\"/>\n    <xsd:enumeration value=\"Restrict\"/>\n    <xsd:enumeration value=\"FieldRestrict\"/>\n    <xsd:enumeration value=\"D360_Restrict\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:complexType name=\"FieldRestrictionRule\">\n  <xsd:complexContent>\n    <xsd:extension base=\"tns:Metadata\">\n      <xsd:sequence>\n        <xsd:element name=\"active\" type=\"xsd:boolean\"/>\n        <xsd:element name=\"classification\" minOccurs=\"0\" maxOccurs=\"unbounded\" type=\"xsd:string\"/>\n        <xsd:element name=\"classificationType\" minOccurs=\"0\" type=\"tns:ClassificationType\"/>\n        <xsd:element name=\"description\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"enforcementType\" type=\"tns:EnforcementType\"/>\n        <xsd:element name=\"masterLabel\" type=\"xsd:string\"/>\n        <xsd:element name=\"recordFilter\" type=\"xsd:string\"/>\n        <xsd:element name=\"targetEntity\" type=\"xsd:string\"/>\n        <xsd:element name=\"userCriteria\" type=\"xsd:string\"/>\n        <xsd:element name=\"version\" type=\"xsd:int\"/>\n      </xsd:sequence>\n    </xsd:extension>\n  </xsd:complexContent>\n</xsd:complexType>\n<xsd:complexType name=\"Metadata\">\n  <xsd:sequence>\n    <xsd:element name=\"fullName\" minOccurs=\"0\" type=\"xsd:string\"/>\n  </xsd:sequence>\n</xsd:complexType>\n```",
-  "declarative_metadata_sample_definition": [
-    {
-      "description": "The following is an example of a FieldRestrictionRule component, which uses the ComplianceCategory classification type. The classification value is one of Salesforce's default compliance categorization values, but you can create a custom compliance categorization value to use instead.",
-      "code": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<FieldRestrictionRule xmlns=\"http://soap.sforce.com/2006/04/metadata\">\n    <active>true</active>\n    <classification>PII</classification>\n    <classificationType>ComplianceCategory</classificationType>\n    <description>Is Owner of Employee</description>\n    <enforcementType>FieldRestrict</enforcementType>\n    <masterLabel>Is Owner Field Restriction Rule</masterLabel>\n    <recordFilter>OwnerId = $User.Id</recordFilter>\n    <targetEntity>Employee</targetEntity>\n    <userCriteria>$User.IsActive = true</userCriteria>\n    <version>1</version>\n</FieldRestrictionRule>"
-    },
-    {
-      "description": "The following is an example of a FieldRestrictionRule component, which uses the FieldSet classification type. The classification value is Salesforce's default field set for personal information, but you can create a field set to use instead.",
-      "code": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<FieldRestrictionRule xmlns=\"http://soap.sforce.com/2006/04/metadata\">\n    <active>true</active>\n    <classification>PersonalInfo_EPIM</classification>\n    <classificationType>FieldSet</classificationType>\n    <description>Is Owner of Employee</description>\n    <enforcementType>FieldRestrict</enforcementType>\n    <masterLabel>Is Owner Field Restriction Rule</masterLabel>\n    <recordFilter>OwnerId = $User.Id</recordFilter>\n    <targetEntity>Employee</targetEntity>\n    <userCriteria>$User.IsActive = true</userCriteria>\n    <version>1</version>\n</FieldRestrictionRule>"
-    }
-  ]
-}