...

"""
Input for `createRuleEngineRule` mutation.

User must have a scope **rule_engine_rule:write**
"""
input CreateRuleEngineRuleInput {
  "Signed data to create rule engine set"
  signedContent: SignedContent!
}

"""
Return type for `createRuleEngineRule` mutation.
"""
type CreateRuleEngineRulePayload {
  "Created `RuleEngineRule`."
  ruleEngineRule: RuleEngineRule
}

...

1. Save signed content to media storage

2. Save data to rule_engine_rules collection (Mongo DB) according to https://e-health-ua.atlassian.net/wiki/spaces/EH/pages/17049387155

Request structure

...

See on Apiary

Authorize

• Verify the validity of access token

  • in case of error - return 401 (“Invalid access token”) in case of validation fails

• Verify that token is not expired

  • in case of error - return 401 (“Invalid access token”)

• Check user scopes in order to perform this action (scope = 'rule_engine_rule:write')

  • return 403 (“Your scope does not allow to access this resource. Missing allowances: rule_engine_rule:write”) in case of invalid scope(s)

...

• Check name, code and value block is submitted

  • in case of error - return 422 ('required property <property> was not present')

• Check that rule engine rule with code is unique (extract active rule_engine_rule with the same code.system and code.value)

  • in case of error - return 409 ("Rule engine rule with such code and system already exists")

Processing

...

Response structure

...

See on Apiary

Post-processing processes

...

HTTP status codes

...