Skip to main content
Aria Knowledge Central

delete_reg_uss_config_params_m Sample Call and Response

This example removes two parameter name-value pairs from a named set of global application configuration parameters previously created with the set_reg_uss_config_params_m method. It is based on the plsql_m_r73.yml definition file.

This example includes every required field. The method accepts no optional fields beyond the envelope fields, so no fields have been left out.

Sample call

{
  "rest_call": "delete_reg_uss_config_params_m",
  "output_format": "json",
  "client_no": 100,
  "auth_key": "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6",
  "set_name": "checkout_flow_config",
  "param_names": [
    { "param_name": "max_retry_count" },
    { "param_name": "default_currency" }
  ]
}

The rest_call and output_format fields are envelope fields added by the REST layer rather than fields documented on the method itself. The set_name field identifies which named configuration set to remove parameters from. The param_names field is a nested, repeatable structure, so this example represents it as a JSON array of objects, each carrying one param_name value; this call removes two parameter names from the set in a single request, and a real call could include more or fewer entries.

Sample response

{
  "error_code": 0,
  "error_msg": "OK"
}

An error_code of zero and an error_msg of "OK" indicate that Aria removed both parameter names from the configuration set successfully. This example omits the method's error_details output field, which is a nonpublic field with no client-facing purpose.

TOP
  • Was this article helpful?