Depending on the service with which the integration is being performed, it is common to have cases in which sending a parameter, even if "empty", is different from not sending the parameter.
For example: Assuming we want to update the name of a user in the record of a service, this service might understand that, if the "user_name" parameter with the "John Doe" value and the "user_age" parameter with the "empty" value (such as an empty or "null" text) are sent, it will update the name of the user as desired (John Doe), but it may also update the age of the user to "empty" (or return an invalid age error, for example).
So, the correct procedure in this case would be to send only the "user_name" parameter in the request, so that the service only updates the user name, disregarding the updates of any other field, as they are not in the request parameters.
Therefore, in this version, an improvement has been performed to allow checking and unchecking the parameters that must be sent in the request as necessary.
View also the improvements made to this component in previous versions: