User Tools

Site Tools


start

This is an old revision of the document!


WHAT IS EMAIL CONFIGURATION

Email configuration is receiving an email and being able to do something about it.

1.1 Contextualize a message for the consultant
example:
	institutionId: 22
		This is the institution Id
	subject: Chemical Engineering Assessment
	intent: ConsultantMessage
		The intent is meant to send the contextualized "message" to a consultant
	scope: []
	message: "Urgent: UP Engineering Assessment. Encourage the learner to take the assessment before the closing date". 
	QA: true
		If QA is true, the config has been tested and is working. If false, the config has not been tested
	bodyFilter: Chemical Engineering Assessment
		This is a unique text taken from the Body/HTML of the email
	pdfFilter: Online Chemical Engineering Assessment
		This is a unique text taken from the attachment of the email. Recommended that you use REster, pdftext API to select the text
		
1.2 Contextualize a message for the learner
	example:
		institutionId: 22
			This is the institution Id
		subject: Chemical Engineering Assessment
		intent: ApplicantMessage
			The intent is meant to send the contextualized "message" to the learner
		scope: []
		message: "Hi {name},
				Thank you for paying your booking fee. Your room is secured! πŸŽ‰
				In the new year, if you choose to reside at the Respublica residence of your choice, you will have to check in before lectures commence. 
				Tips on check-in will be provided, closer to the time."
				
			This is the message that will be on the ticket
		QA: true
			If QA is true, the config has been tested and is working. If false, the config has not been tested
		bodyFilter: "Chemical Engineering Assessment"
			This is a unique text taken from the Body/HTML of the email
		pdfFilter: "Online Chemical Engineering Assessment"
			This is a unique text taken from the attachment of the email. Recommended that you use REster, pdftext API to select the text

NB: This email configuration will create a ticket for a consultant/ team. The ticket will be sent via email to the technical support consultant. Then the technical support consultant will forward it to the relevant team lead

1.3 Validate the status of an application
	example:
		institutionId: 22
		subject: Acceptance Letter
		intent: ValidStatus
			Check what is the current status of the application 
		scope: [
				name: applicationstatus
					name: reference relates to what will be extracted from the email
				section: constant
					constant means this value remains the same
				value: Provisionally Accepted
				]
		pdfFilter: been conditionally allocated to you
		QA: true

This email config verifies that when we receive this email with all these settings it will create an intent_discovery for the user to the value Provisionally Accepted as well as add the institution to the PAInstitution & SoftOffer columns for the user

	
	
1.4 Validating the data
	example:
	institutionId: 22
		subject: Confirmation of Application
		intent: ValidData
			Verify if the data from an email was captured correctly to the matrix
		scope: [
				name: username
					name: reference relates to what will be extracted from the email
				section: body
					body means everything that appears in the freeform box, including salutation and all the content in the email
				startafter: enter your username (
					startafter setting tells the code to start after the words
				endlength: 9
					endlength is how long the username is
				endbefore: ) and newly
					endbefore setting tells the code to end before the words
				]
		QA: true

This email config verifies that when we receive this email with all these settings it will create an intent_discovery for the user to have username. It will include the password and reference if the settings for these were included.

1.5 Ignoring an email
	example:
		institutionId: 22
		subject: Chemical Engineering Webinar
		intent: Igonre
			Do nothing once this type of email has been received
		scope: []
		QA: true
			If QA is true, the config has been tested and is working. If false, the config has not been tested
			

This email config will ignore the email if it comes through and do nothing about it. Of course, you are allowed to include more settings like pdfFilter or bodyFilter

NB: All email configurations should be unique so that there is no confusion in the code. All ApplicantMessage intents should be reviews yearly as some of them contains date and these needs to be reviewed.

USEFUL INFORMATION

Please review this yearly and always read the emails as this is subject to change

  1. SMU Offers: +/-3 days β€”- Sent both SMS and email
  2. UWC Offers: +/-3 days
  3. Wits Offers: +/-5 days
  4. Unisa Offers: +/- 10 days
  5. UFS Science Faculty Offers: +/- 5 days
  6. UFS Other Faculties: +/- 3 days
  7. SPU Offers: +/- 5 days β€”- Sent by SMS first then by email
  8. VUT Offer: +/ 5 Days

When you search for an email from the message collection

1. Wits(Attachment): (exact match)

  1. UW_AD_UGAA_N.pdf β€”- Outstanding Docs (Application fee, HS certificate)
  2. UW_AD_UGF0_N.pdf β€”- Firm Offer
  3. UW_AD_UGD6_N.pdf β€”- Waiting for Gr12 results
  4. UW_AD_UGD4_N.pdf β€”- Submit final academic record and certificate of good conduct
  5. UW_AD_UGD3_N.pdf β€”- Waiting for Gr12 results (Education)
  6. UW_AD_UGPR_N.pdf β€”- Provisional Acceptance
  7. UW_AD_UGS2_N.pdf β€”- NBT reminder for HS
  8. UW_AD_UGS1_N.pdf β€”- NBT reminder for BSc & Speech
  9. UW_AD_UGS4_N.pdf β€”- Architectural Studies' exercise β†’ link provided in the attachment
  10. UW_AD_UGR15N.pdf β€”- ???
  11. UW_AD_PGDF5.pdf β€”- Postgraduate Outstanding documents (For learners applied for PG studies)
  12. UW_AD_UGR11N.pdf β€”- Architectural Rejection based on not submitting the exercise or attending the interview
  13. UW_AD_UGD8_N.pdf β€”- Waitlist
  14. UW_AD_UGR19N.pdf β€”- Rejected
  15. UW_AD_UGD4_N.pdf β€”- registered learner applying for another qualification
  16. UW_SF_BALSPO.pdf β€”- Overdue fees for registered learners
  17. UW_AD_UGR7_N.pdf β€”- Rejected (Grade 14 or transitioning from another university)
  18. UW_AD_PGA2_N.pdf β€”- Postgraduate qualifications

2. SU(Attachment): (partial match)

  1. PROVISIONAL_OFFER_LETTER_ β€”- Provisional Acceptance
  2. Offer_Letter_ β€”- Firm Offer

3. UCT(HTML): (partial match)

  1. CONDITIONAL OFFER OF A STUDY PLACE FOR β€”- Provisional Acceptance
  2. OFFER: CONDITIONAL OFFER OF A STUDY PLACE β€”- Provisional Acceptance
  3. OFFER: STUDY PLACE FOR β€”- Firm Offer
  4. CONFIRMATION OF OFFER β€”- Firm Offer

4. RU (Attachment): (partial match)

  1. TT β€”- deposit has been waived because, on the application, you indicated you would be applying for NSFAS
  2. AP β€”- Waitlist
  3. O1 β€”- Provisional Acceptance (Ask Lusani, this is a conditional offer between
  4. FF β€”- Outstanding documents
  5. RE β€”- Rejected
  6. LW β€”- Offer that will expire in the next two weeks

5. UP(Attachment): (partial match)

  1. _M06.PDF β€”- Medicine email that only you will be considered if medicine was the first choice
  2. _M08.PDF β€”- HS Scie Conditional Acceptance
  3. ??.PDF β€”- HS Waitlist
  4. _A67.PDF β€”- Confirmation email that you meet the minimum requirements and doesn't guarantee admission to the program
  5. _AA5.PDF β€”- Confirmation email containing student number
  6. _M40.PDF β€”- Biographical Information for Health Qualification
  7. _A44.PDF β€”- Conditionally Admitted
  8. _A42.PDF β€”- Conditionally Admitted (Computer Science & Engineering) - department specific
  9. _A41.PDF β€”- Admitted
  10. _A31.PDF β€”- Rejected because Medicine or HS qualification was not a 1st choice
  11. _W00.PDF β€”- Residence placement reservation
  12. _V00.PDF β€”- Vet Scie
  13. _H17.PDF β€”- Drama auditions
  14. _H12.PDF β€”- Mandotary selection ID
  15. _AI5.PDF β€”- Visa Issuity Authority (Not config)
  16. _A68.PDF β€”- Waitlist or Programme Full (For Engineering and Computer Science) - department-specific

6. NWU(pdf): (exact match)

  1. PVA006.pdf β€”- Conditionally Acceptance
  2. PVA014.pdf β€”- Acceptance
  3. PVA002.pdf β€”- Programme Full (Met requirements, however, due to capacity) for education
  4. PVA002.pdf β€”- Rejected based on a selection process (For selection programs)
  5. PVA007.pdf β€”- Assessment/Interview
  6. PVA018.pdf β€”- Outstanding Docs
  7. PVA003.pdf β€”- Referred to the relevant faculty (Pending) β€” could also mean that there are docs missing
  8. AAA103.pdf β€”- Application deleted (welcome to apply again)

7. UFS (Attachment): (exact match)

  1. DENYUGRD2019.pdf β€”- Rejected
  2. UFS_DDEF.pdf β€”- Pending
  3. CONDLETCOV.pdf β€”- Conditional
  4. UV_ADMIT_COV.pdf β€”- Accepted

CPANEL NAVIGATION

What to do when emails are stuck, and no user is receiving any incoming emails?

  1. Log in to the cPanel account
  2. Click on β€œEmail Accounts”
  3. In the search textbox, enter β€œunlimited”
  4. Click β€œCheck Email” for the respective domain. This action will lead you to the unlimited account

Check if the mailbox is empty. If it is, this indicates that emails are coming through. Alternatively, the emails might be in the spam filters.

Navigating to Spam Filters

You would only use this if a specific email doesn't come through. Examples of emails that were stuck here in the past were Sasol emails, WSU emails, and mostly bursary emails.

  1. From cPanel, navigate to Professional Spam Filters
  2. Click on the admin.bridgeapp.co.za domain
  3. n the left-side menu bar, click on β€œSpam Quarantine”

Use the Query Rules:

  • You can search using a From, Recipient, Subject, etc. These options can be selected from the drop-down menu. Use any information available.
  • You can decide whether to use an exact match or contains. These options can be chosen from the drop-down list.
  • Then, in the textbox, you may paste the From, Recipient, or Subject.

If the email(s) are found, you need to add the email address to Global Filters (This is explained at the bottom, describing what it is and how to work with it). Adding it to Global Filters ensures that the From address is not considered as spam anymore.

If the email is not found in the spam quarantine. Navigate to Track Delivery

Track Delivery Navigation

Here you are checking if the email did come through however, it is not visible to the user.

  1. From cPanel, navigate to Track Delivery

Here you'll see all emails that have come through for users

  • The Event column is color-coded, the green email has been received, the red email did not get sent however, we received it, and grey the email has been deleted. The list gets deleted every 10 days. In this case, reach out to Lusani

This is to check if the email was received or not. If also, the email address does not appear here, it means the issue is not Gradesmatch but the external

start.1704701208.txt.gz Β· Last modified: 2024/01/08 10:06 by admin

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki