Please enable JavaScript.

Coggle requires JavaScript to display documents.

Parameter Validations, Parameters, Parameters - functional flows with…

- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Logged user must have relevant publisher/admin permission
        
        Go to resource path
        
        Add parameters with -> parameter in-path, style-simple, explode-false, required-true, Allow Empty-N/A
        
        Create application
        
        2 more items...
        
        Logged user must have admin permission
        
        Logged user must have admin permission
      - Logged user must have admin permission
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-path, style-simple, explode-false, required-true, Allow Empty-N/A
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Query, style-Form, explode-false, required-false, Allow Empty-true
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Query, style-Form, explode-false, required-false, Allow Empty-false
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Header, style-Simple, explode-false, required-true, Allow Empty-N/A
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Header, style-Simple, explode-false, required-true, Allow Empty-N/A
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Query, style-Form, explode-true, param type-Array
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Query, style-Form, explode-false, param type-Array
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Query, style-Space Delimited, explode-false, param type-Array
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Query, style-Pipe Delimited, explode-false, param type-Array
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Header, style-Simple, explode-false, param type-Array
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Header, style-Simple, explode-true, param type-Array
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Query, style-Form, explode-true, param type-Object
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Query, style-Form, explode-false, param type-Object
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Path, style-Label, explode-false, param type-Object
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Path, style-Label, explode-true, param type-Object
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Path, style-Matrix, explode-false, param type-Object
        
        Create application
        
        1 more item...
- - - - Create Scope
        
        Create REST Pool
        
        Create REST API
        
        Go to resource path
        
        Add parameters with -> parameter in-Path, style-Matrix, explode-true, param type-Object
        
        Create application
        
        1 more item...
- - - - Validate the gateway call with valid deepObject format
        
        Example: ?user[role]=admin&user[firstName]=Alex
        Expectation: backend receives object { "role": "admin", "firstName": "Alex" }.
      - Validate the gateway call with missing nested field
        
        Example: ?user[role]=admin (no firstName)
        Expectation: backend receives { "role": "admin" }.
      - Validate the gateway call with extra undefined nested field
        
        Example: ?user[role]=admin&user[lastName]=Smith (lastName not in spec)
        Expectation: gateway rejects request or ignores extra field.
      - Validate the gateway call with invalid nesting
        
        Example: ?user.role=admin (dot notation instead of brackets)
        Example: ?user.role=admin (dot notation instead of brackets)
    - - Form style, explode=true
        
        Validate the gateway call with multiple values as repeated keys
        
        Example: id=3; id=4; id=5
        Expectation: backend receives array [3,4,5].
        
        Validate the gateway call with single value
        
        Example: id=3
        Expectation: backend receives [3].
        
        Validate the gateway call with empty value
        
        Example: id=
        Expectation: backend rejects or handles as per spec (AllowEmptyValue).
      - Form style, explode=false
        
        Validate the gateway call with comma-separated values
        
        Example: id=3,4,5
        Expectation: backend receives [3,4,5].
        
        Validate the gateway call with single value
        
        Example: id=3
        Expectation: backend receives [3].
        
        Validate the gateway call with invalid delimiter
        
        Example: id=3|4|5
        Expectation: gateway rejects since | is not valid for form style.
  - - - Spec: parameter defined with default and required: false.
        Test: client does not send that parameter.
        Expectation: backend receives the default value.
    - - Spec: same as above.Test: client sends the parameter with a different valid value.Expectation: backend receives the sent value, not the default.
    - - Spec: default value must match the type defined (integer, string, etc.). swagger.io+1
        Test: default in spec is integer (e.g. default: 20), but a non-integer default is set (invalid spec) >> tool should reject spec or validation logic should fail.
    - - Spec: default used with required parameters is meaningless or invalid. swagger.io+1.
        Test: parameter is marked required: true and also has default.
        Expectation: default should be ignored; client must send value.
    - - For schema properties inside a complex object, default should apply where omitted.
        Test: send object missing a nested field; default inside schema should fill it.
    - - If param has default and also nullable: true, test that omission yields default, but explicit null if allowed.
    - - Spec: default can be an empty string "" or zero 0, if allowed by type. Stack Overflow+1. Test: omit param defined default: "" >> backend sees "".
  - - - Content-Type vs content-type
        Custom headers like X-Request-ID vs x-request-id
    - - application/json (valid)
        application/JSON / APPLICATION/JSON (should fail if strict)
    - - Enum: ["Male", "Female", "Other"]
        Input: male, FEMALE, OTHER (fail if case-sensitive)
    - - "patientId" (valid)
        "PatientID" or "PATIENTID" (invalid if strict JSON schema enforcement)
    - - Bearer tokens should always be treated as case-sensitive (AbCdEf123 ≠ abcdef123).
  - - - Spec: parameter or property marked nullable: true.
        Test: client sends "field": null (JSON null).
        Expectation: backend accepts it.
    - - Spec: parameter/property without nullable. Test: client sends "field": null. Expectation: gateway/backend rejects with 400 Bad Request.
    - - Spec: nullable parameter. Test: client omits parameter completely. Expectation: backend interprets as “not provided”, not null.
    - - Spec: parameter has both default and nullable: true. Test A: client omits parameter >> backend applies default. Test B: client sends explicit null >> backend accepts null, does not apply default.
    - - Spec: items schema marked nullable: true. Test: ["abc", null, "xyz"]. Expectation: backend accepts null elements.
    - - Spec: object schema has properties with nullable: true. Test: { "name": "Alex", "nickname": null }. Expectation: backend accepts null for nickname.
    - - Spec: parameter is string, not nullable. Test: "field": null. Expectation: rejected — null is not a valid string unless nullable: true.