Introduction:
The SupplyOrderEmailSubject and SupplyOrderEmailBody settings define the Subject and Body of the email used to send a supply order using the OrderThirdPartyService transition.
Contents:
Information:
For instructions on how to locate these settings and make changes please refer to How to edit Email Message Template Settings. Please note, these settings are also available per FBO in the ‘FBO locations settings' page area. It’s also possible to use Email template variables in each setting.
The following field values override the SupplyOrderEmailSubject/SupplyOrderEmailBody setting defaults for OrderThirdPartyService transition:
-
The product's ‘Supply Order template’:
-
Email subject template - Overrides SupplyOrderEmailSubject
-
Message body template - Adds to the SupplyOrderEmailBody (if the ~SupplyOrderDetails~ variable is added).
-
-
Configuration string in service workflow, refer to OrderThirdPartyService transition:
-
Subject= ; - Overrides SupplyOrderEmailSubject
-
Body= ; - Adds to the SupplyOrderEmailBody (if the ~SupplyOrderDetails~ variable is added).
-
-
Orderline transition changes:
-
User edits in the ‘Supply order subject’ field - Overrides SupplyOrderEmailSubject
-
User edits in the ‘Supply order body’ field - Adds to the SupplyOrderEmailBody (if the ~SupplyOrderDetails~ variable is added).
-
SupplyOrderEmailSubject example:
Service Request ~OrderDisplayName~ / ~AircraftRegistrationCode~
SupplyOrderEmailBody example:
REF number: ~OrderKey~ ATTN: ~SupplierContactName~ Dear Duty manager, Please see our ~ProductCode~ request for <b>~RegistrationCode~</b> ~AircraftTypeShortName~. ~Supplyorderdetails~ In order to ensure timely payment please add order reference number ~OrderKey~ to all invoices pertaining this flight. Kind Regards, ~EmployeeFirstName~ ~Reports-Address1~ Phone: ~Reports-Phone~ Email: ~Reports-Email~ ~Reports-Internet~ <font size="1.5px"> <i>Timestamp: ~CurrentDateTime~</i></font>
Email example:
Note: A PDF copy of the service supply order is automatically attached to the email.
Comments
0 comments
Please sign in to leave a comment.