Delete a distribution rule within a version
delete
/fscmRestApi/resources/11.13.18.05/personAssignmentLaborSchedules/{LaborScheduleId}/child/versions/{versionsUniqID}/child/distributionRules/{distributionRulesUniqID}
Request
Path Parameters
-
LaborScheduleId(required): integer(int64)
The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
-
distributionRulesUniqID(required): string
This is the hash key of the attributes which make up the composite key--- DistributionRuleId and LineNumber ---for the Person Assignment Labor Schedule Version Rules resource and used to uniquely identify an instance of Person Assignment Labor Schedule Version Rules. The client should not generate the hash key value. Instead, the client should query on the Person Assignment Labor Schedule Version Rules collection resource with a filter on the primary key values in order to navigate to a specific instance of Person Assignment Labor Schedule Version Rules.
For example: distributionRules?q=DistributionRuleId=<value1>;LineNumber=<value2> -
versionsUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Person Assignment Labor Schedule Versions resource and used to uniquely identify an instance of Person Assignment Labor Schedule Versions. The client should not generate the hash key value. Instead, the client should query on the Person Assignment Labor Schedule Versions collection resource in order to navigate to a specific instance of Person Assignment Labor Schedule Versions to get the hash key.
Header Parameters
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
There's no request body for this operation.
Back to TopResponse
Default Response
No Content. This task does not return elements in the response body.