Release 0.19
Email & Communication
Email & Communication - 1 item delivered in v0.19
What Was Delivered
- Reason codes for FTS User ONLY
- Update the Order Form so that the reason field is a Textarea. The client intends to paste entire email communication into this field.
- This should be visible to the FTS Customer when they are viewing a rejected Order.
- Create a OneToMany relationship with ReasonCode.
- This should only be visible to the FTS User.
Detailed Items
Checklist
- CkEditor for reason which should be visible as readonly to the client.
- Create RejectionReasonCode Entity: with the following attributes: Code (string), TItle (string), Service (OneToMany relation with ServiceCategory), Type (relationship with RejeactionReasonCodeType), use TimestampableEntity
- Only FTS User Portal users should be able to see the reasons. This should not be visible from client portal as it is sensitive information.
- Upload the attached Rejection_reasons.xls file to the RejectionReasonsCode. Use the worksheet name to identify the category / service.
- Create RejectionReasonCodeType entity with the following attirbutes: name, tag
Impact
Strengthened communication workflows, ensuring stakeholders receive timely and accurate updates.