1.

Changes in Cost Survey distribution email

 Cost Survey distribution email should be modified to include the Parts Chairs/Co-Chairs in the
mailing list of recipients
 indicate the survey due date in letters, for example: June 13, 2021
 for Parts and Equipment Pooling cost survey emails

Modifications in:
usp_EQ_CostSurvey X and usp_PP_CostSurvey X

@strMode = 'NEW'

 ufn_FormatDate added to format the dates

 @strDateFromFormated and @strDateToFormated for due date in letters
 Added PPPoolChair for usp_PP_CostSurvey and EPPoolChair for usp_EQ_CostSurvey in the
@strMailTo querry
 Fixed issue with end date > start date validation in IATP_Moon\P_EquipPool\
EQCostInitiate.aspx

2. Limitation in adding participants for Parts and Equipment Pooling

Preventing the provider from adding participants in Parts and E-pool when creating a new pool at
station. The platform should maintain the possibility for the provider to create a new pool at a station,
only having the provider as participant (advertise pool).

 The platform should only allow the providers to add themselves as pool participant when setting
up a new pool at station.

Modifications in:
IATP_Moon/P_EquipPool/EQPoolUpdate.aspx.cs

IATP_Moon/P_PartsPool/PartsPoolUpdate.aspx.cs

 Controls for adding participants on create new station hidden.

3. Sending a notification email when a user is assigned the role of Senior Delegate
 to the IATP Board, staff and other Senior Delegates
 on the user creation and modification
 email subject: “IATP Senior Delegate Notification”
 email body:
This is a notification email to inform you that Mr./Ms. First-Name Middle-Name Last-Name has
been assigned the role of Senior Delegate for the airline Airline-Name or Associate Member
Associate Member-Name.
The above message has been delivered to the below reported IATP Members:
AA, BB, CC, DD, EE,…..
IATP PROPRIETARY INFORMATION - FOR COMPANY USE ONLY-
IATP email message disclaimer.
 Modifications in:

usp_SA_User_Update X
@strMode = 'EDIT' at line 503

 e-mail added in usp_EML_SysAdmin X @strTranType = 'UPT_SD'

 e-mail is sent to all with roles SeniorDelegate and ActingSeniorSelegate

4. Update of user deactivation procedure

 to enforce the one-year period of password expiration rule after the user has been reactivated
by IATP staff and/or platform provider
 Two different emails should be sent from the platform to inform the user about the
deactivation reason, one for password expiration and one due to one year of inactivity.

a) Message to send in case of Deactivation for non-logging in in one year:

“Dear IATP Platform User,

Due to one year of non-activity in the IATP Platform, your Platform user account has been
deactivated.

Please contact the IATP CorporateOffice by sending an e-mail to info@iatp.com in order to re-
activate your account in the IATP Platform.
Upon re-activation of the account, you will need to reset the password from the www.iatp.com
Login page.

Sincerely,
IATP Support”

b) Message to send in case of Deactivation for not having changed the password after 5
reminders:

“Dear IATP Platform User,

Due to not having changed the password after 5 reminders sent before the password expiration
(one per week sent for 5 weeks), your Platform user account has been deactivated.

Please contact the IATP Corporate Office by sending an e-mail to info@iatp.com in order to re-
activate your account in the IATP Platform.
Upon re-activation of the account, you will need to reset the password from the www.iatp.com
Login page.

Sincerely,
IATP Support”
 When a user is reactivated a message should be sent to all office team (info@iatp.com)
A new validation control should be added on the login screen of the platform that should check
whether the user has changed his password after the reminders sent by the platform and/or
once the account was reactivated.
The login should not be allowed in case the password of the user has not been changed upon
reactivation and the user should get a notification message on the screen informing him that the
password should be changed immediately by clicking the “Reset password” link in the login
screen.
When the user enters a new password, the platform should enforce the rule that the new
password should be different from the last used: the platform should have a popup informing
the user in case she/he is using the same password like the previous one.
The password should follow the normal practice used for passwords (number of characters,
special one, etc.), and an explanation on the required password should be provided e.g.: Your
password should contain at least xx characters, at least one special character etc
If those requirements are not met, then the platform should have a popup message informing
the user what is still required for the correct reset (e.g. if a special character is missing, then the
message: “Your password should contain at least 1 (one) special character like “ _ !_?” should
appear.

5. Mail List with logos

Modifications in:
IATP_Moon/P_SysAdmin/CompanyUpdate.aspx.cs

 Changed the check for gif into png for logo upload

IATP_Moon/P_SysAdmin/MailingList.aspx

IATP_Moon/P_SysAdmin/MailingList.aspx.cs

 Added IATP_Moon/CompanyLogo/logo_placeholder.png as a placeholder when no logo is

exists

usp_Sys_CompanyInfo X

@strMode = 'MAILMA'
@strMode = 'MAILAM'

 Created ufn_ToProperCase X to get the Company Name field in proper case

 Added CompanyName, LogoName and URL to the querry for associate members and member
airlines
 URL is not needed now but will be needed when changes will be transfered to the
homepage