...
The above rollback options do not directly support the deletion of files, that were newly deployed. This option helps you remove unnecessary files from the target org or delete files that were mistakenly deployed.
...
If you wants to delete files or components from the target Salesforce Org as a part of a rollback, then you must use the Destructive Changes functionality. This functionality allows you to remove components that are no longer needed. For detailed information on how to implement destructive changes, please refer to - https://flexagon.atlassian.net/wiki/spaces/FD80/pages/10561716578/Salesforce+Tutorial#Support-of-Destructive-Packages
...
b. If you deployed a Custom Field, Validation Rule, or any subcomponent of metadata and want to revert the change by deleting the subcomponent, you can use this option by following these steps:
1. For Example, If you deployed a Custom Field or Validation Rule and wish to roll back this change, you need to delete the subcomponent (e.g., Custom Field or Validation Rule) from the Source Salesforce Org.
2. After that, In FlexDeploy - Compare the Custom Object from Salesforce Org Management tab to identify the destructive changes.
3. The comparison will reveal the destructive file (subcomponents) related to the removed Custom Field or Validation Rule.
4. Commit the destructive subcomponents and add to the package. Build and deploy the package to remove the subcomponents from the target Salesforce Org.
...
...
Rollback capabilities in FlexDeploy for Salesforce development offer flexibility, precision, and confidence in deployment management. Whether you are reverting a full deployment or rolling back specific components, FlexDeploy’s versioned artifacts, file revisions, and backups repository provide the tools necessary to ensure system stability and minimize downtime. By integrating rollback strategies into your deployment workflow, you can ensure smoother, more reliable Salesforce development and maintenance.