Remove Workspace parameter from tools that don't output to a workspace
ArcGIS Pro 3.2.2
There are tools that have a Workspace parameter, but the tools don't actually output data to a workspace, so the parameter isn't used.
Could the Workspace parameter be removed from all geoprocessing tools where it isn't used? Otherwise, it's confusing to users when there is a parameter that doesn't do anything. And users wonder if the tool produces a static output/file, instead of a temporary feature layer in the map.
BUG-000164707 - In ArcGIS Pro 3.2, there are some geoprocessing tools (such as Make Feature Layer or Make Table View) that have a parameter with a note saying 'This parameter is not used'. This parameter matches what is listed in the documentation of this tool, however, this parameter was used in older versions of ArcGIS Pro and the change to this tool is not documented or explained in the Data Management Toolbox History 'Tool Reference' document.
Status: Known Limit (Learn More)
Additional Information: The workspace parameter of MakeFeatureLayer and MakeTableView was used to automatically adjust field names in the field info parameter to use lengths suitable for the specified workspace/format.
The field info parameter of these tools in ArcGIS Pro does not support field renaming, as explained here: ENH-000142266
The parameter has never been used, and field renaming has never been possible, since Pro 1.0. Documenting the change in the parameter description between Pro 3.1 and 3.2 is not accurate. It was tested and observed during the 3.2 release cycle that the workspace parameter served no purpose, thus the documentation change. Documentation corrections are not listed in the toolbox history topic.
Bug and Enhancement Request Status says:
Known Limit
After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. The issue's Additional Information section may contain further explanation.
I don't know why that issue would be considered "outside of Esri's control". It seems like it is within Esri's control to improve those tools.