-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mutliple Observation in API Endpoint "/api/policy-hub/policy-content #57
Labels
bug
Something isn't working
Comments
@mkanal thanks for the input.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reference:
Observation 1:
Requesting API Endpoint "/api/policy-hub/policy-content" Membership Key with invalid Value.
Endpoint: /api/policy-hub/policy-content
Request body
Current Behavior
Response contains valid rightOperand="active",
Expected Behavior
Instead of correcting the constraint, an error was expected with details addressing the incorrect value.
Remark:
Is this a misunderstanding of the functionality of the endpoint the behavior correctly?
Observation 2:
Requesting API Endpoint "/api/policy-hub/policy-content " "Key": "FrameworkAgreement.traceability" and invalid value
Endpoint: /api/policy-hub/policy-content
Request body
Current Behavior
Expected Behavior
Instead of providing an attribute list with possible Values, an error was expected with details addressing an incorrect value.
Remark:
Is this a misunderstanding of the functionality of the endpoint, the behavior correctly?
Observation 3:
Requesting API Endpoint "/api/policy-hub/policy-content " "Key": "BusinessPartnerNumber" and invalid Value
As expected, an 400 with error description is returned
Observation 4:
Requesting API Endpoint "/api/policy-hub/policy-content " "Key": "purpose" and no value
Endpoint: /api/policy-hub/policy-content
Request body
Current Behavior
Expected Behavior
Instead of {dynamicValue} values valid values are expected. In case calling {{baseUrl}}/api/policy-hub/policy-types?useCase=Traceability the purpose is well-defined
Observation 5:
What is the purpose of "technicalEnforced": false /true? What impact has this regarding a business, app?
Observation 6:
Endpoint: /api/policy-hub/policy-content
Request body
Current Behavior
Expected Behavior`
Error message with http status code 400 that value is not allowed. Only "ID Trace 3.1" is allowed.
Observation 7:
Why namespace is only used for logicalOperand Or and And ?
The text was updated successfully, but these errors were encountered: