Pre-defined response

Incoming requests matching a pre-defined rule gets an automated response

1. Goal is to provide E-Helpdesk application with automatic responding rules features, as follows:
a. The EHELPDESK_NM_USER operator can define one or more automatic response rules
b. An automatic response rule is made of a mandatory name, regulation id, a list of included/excluded request types and an applicability period
c. The applicability period is limited in duration - does NOT depend on the regulation state (active or not)
d. Buffer time is required before submitting the automatic response
2. When the request is submitted, CUA.STORE flags it as "automatic" if it matches a rule (the first one if there are multiple matches). Note that even if the rule is cancelled before the request is locked or responded, the request will still be locked and responded automatically. This flag is persisted together with its rule reference.
3. In addition, when the request is stored and flagged as automatic, CUA.STORE computes the earliest lock time (but the request is not locked yet) and the earliest response time. The earliest lock time is the submission time plus a random number in [ MIN_AUTO_LOCK_TIME, MAX_AUTO_LOCK_TIME ] (both defined in WIND). The earliest response time is the lock time plus a random number in [ MIN_AUTO_RESPONSE_TIME,

///

 Goal is to provide E-helpdesk application with automatic rejection of slot improvement E-helpdesk request type.
 
The EHELPDESK_ADMIN_USER operator can define the SLOT_IMPROVEMENT_REQUEST_AUTOMATIC_PROCESSING_ENABLED.
 
The EHELPDESK_ADMIN_USER operator can define the LOCAL_AVERAGE_DELAY_THRESHOLD
 
When the SLOT_IMPROVEMENT_REQUEST_AUTOMATIC_PROCESSING_ENABLED is set to false, the automatic processing of the slot improvement E-helpdesk request is disabled and none the below action will be performed.
 
When the EHELPDESK_AO_USER operator submits a request for slot improvement and the SLOT_IMPROVEMENT_REQUEST_AUTOMATIC_PROCESSING_ENABLED is true, if the DLA is lower than the LOCAL_AVERAGE_DELAY_THRESHOLD and if the flight is not in READY state, the request is automatically rejected. The rejected request is displayed in the MASTER AREA (for both EHELPDESK_AO_USER and EHELPDESK_NM_USER) list of request with a state "Unable" and a red cross icon.
 
The automatic response message is "Sorry, the delay of this flight is deemed to be too low for manual processing. Regards."
 
To be on the safe side and because one can modify these WIND values, in the case where the controller needs to respond a request that was not locked yet, the controller locks it and does not respond it - it will be duly responded in the next controller execution.

RULE create

a. Name:
i. A rule can be name
ii. Mandatory
b. REGUL+:
i. A rule must be associated to a regulation id
ii. Mandatory
c. Description:
i. A rule can be associated to a description
ii. Mandatory
d. Request Type Group:
i. Rule can be associated to a list of request types
ii. Can match all request types or only a selection
iii. Selection can be inclusive or exclusive
iv. Mandatory
e. Applied Till:
i. Date/Time
ii. Applicability period (actually start of period is equal to initial submission time)
iii. Mandatory
f. Response:
i. All elements that form a (human) response (similar to E-Helpdesk Response type):
• – Response text
• - Indication if the response if “unable”
• - Indication if the response is to be made of general interest
• - Protected status
• - Internal CFMU comment
ii. Mandatory
g. Status:
i. Choice between ACTIVE, CANCELLED, DONE
h. Submitter
i. Token id of submitter of the rule
i. Submission Time and Last Update Time
j. Version