mirror of
https://github.com/frappe/erpnext.git
synced 2026-08-28 22:28:24 +00:00
Email ID renamed to Email Address
This commit is contained in:
@@ -9,7 +9,7 @@ very simple and easy.
|
||||
Select the list that you want to send the email to. Fill in your content in
|
||||
the message box, and send your newsletter.If you wish to test your email, to
|
||||
see how it looks to the recepient, you can use the test function. Save the
|
||||
document before testing. A test email will be sent to your email id. You can
|
||||
document before testing. A test email will be sent to your Email Address. You can
|
||||
send the email to all the intended receipients by clicking on the send button.
|
||||
|
||||
<img class="screenshot" alt="Newsletter - New" src="{{docs_base_url}}/assets/img/crm/newsletter-new.png">
|
||||
|
||||
@@ -18,7 +18,7 @@ Note: Invoice/Order currency and Payment Gateway Account currency should be same
|
||||
---
|
||||
|
||||
##### Notify Customer
|
||||
You can notify customer from Payment Request with print format. If customer contact email is mentioned, it will automatically fetch email. If not so you can set email id on Payment Request.
|
||||
You can notify customer from Payment Request with print format. If customer contact email is mentioned, it will automatically fetch email. If not so you can set Email Address on Payment Request.
|
||||
|
||||
<img class="screenshot" alt="Payment Request" src="{{docs_base_url}}/assets/img/accounts/pr-details-2.png">
|
||||
|
||||
|
||||
@@ -28,6 +28,6 @@ Option to set document as recurring will be visible only after submission. Recur
|
||||
|
||||
In a situation where recurring invoice is not created successfully, user with System Manager role is notified about it via email. Also the document on which recurring event failed, "Is Recurring" field is unchecked for it. This means system doesn't try creating recurring invoice for that document again.
|
||||
|
||||
Failure in creation of recurring invoice could be due to multiple reasons like wrong email id mentioned in the Email Notification field in Recurring section etc.
|
||||
Failure in creation of recurring invoice could be due to multiple reasons like wrong Email Address mentioned in the Email Notification field in Recurring section etc.
|
||||
|
||||
On receipt of notification, if cause of failure is fixed (like correcting email id) within 24 hours, then recurring invoice will be generated automatically. If issue is not fixed within the said time, then document should be created for that month/year manually.
|
||||
On receipt of notification, if cause of failure is fixed (like correcting Email Address) within 24 hours, then recurring invoice will be generated automatically. If issue is not fixed within the said time, then document should be created for that month/year manually.
|
||||
@@ -51,7 +51,7 @@ monthly, quarterly, half-yearly or annual basis, you can check the “Recurring
|
||||
Invoice” box. Here you can fill in the details of how frequently you want to
|
||||
bill this Invoice and the period for which the contract is valid.
|
||||
|
||||
ERPNext will automatically create new Invoices and mail it to the email ids
|
||||
ERPNext will automatically create new Invoices and mail it to the Email Addresses
|
||||
you set.
|
||||
|
||||
#### POS Invoices
|
||||
|
||||
@@ -24,7 +24,7 @@ __Step 3:__ System will open the supplier quotation, user has to enter the rate
|
||||
|
||||
#### For Supplier
|
||||
|
||||
__Step 1:__ User has to create contact or enter email id against the supplier on request for quotation.
|
||||
__Step 1:__ User has to create contact or enter Email Address against the supplier on request for quotation.
|
||||
|
||||

|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
To login into the customer account, the customer has to use his email id and
|
||||
To login into the customer account, the customer has to use his Email Address and
|
||||
the password sent by ERPNext; generated through the sign-up process.
|
||||
|
||||

|
||||
|
||||
@@ -16,7 +16,7 @@ Customers have to log-in to the Company Website, and sign-up as a customer.
|
||||
|
||||

|
||||
|
||||
After the sign up process, a mail will be sent to the customers email id with
|
||||
After the sign up process, a mail will be sent to the customers Email Address with
|
||||
the password details.
|
||||
|
||||
{next}
|
||||
|
||||
@@ -16,7 +16,7 @@ system shall create a New Job Applicant against each email received on the mailb
|
||||
|
||||
> Setup > Email Account > New
|
||||
|
||||
* Enter the email id and the password, and select 'Enable Incoming'
|
||||
* Enter the Email Address and the password, and select 'Enable Incoming'
|
||||
|
||||
* In 'Append To' select 'Job Applicant'
|
||||
|
||||
|
||||
@@ -80,7 +80,7 @@ Here you can fill in the details like; of how frequently you want to generate an
|
||||
|
||||
On updating the Sales Order, a Recurring ID will be generated which will be same for all recurring orders generated from this particular Sales Order.
|
||||
|
||||
ERPNext will automatically create new Order and mail a notification to the email IDs you set in the 'Notification Email Address'field.
|
||||
ERPNext will automatically create new Order and mail a notification to the Email Addresses you set in the 'Notification Email Address'field.
|
||||
|
||||
<img class="screenshot" alt="Reccuring Sales Order" src="{{docs_base_url}}/assets/img/selling/recurring-sales-order.png">
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
#Rename User
|
||||
|
||||
Renaming functionality allows you to edit id of specific record. User is saved with person's email id. Only User with System Manager's role will be able to rename User IDs.
|
||||
Renaming functionality allows you to edit id of specific record. User is saved with person's Email Address. Only User with System Manager's role will be able to rename User IDs.
|
||||
|
||||
Following are the steps to rename user id.
|
||||
|
||||
@@ -18,7 +18,7 @@ From Menu, select Rename.
|
||||
|
||||
#### Step 3: Update
|
||||
|
||||
Enter valid email id and click on Rename.
|
||||
Enter valid Email Address and click on Rename.
|
||||
|
||||
<img alt="Update" class="screenshot" src="{{docs_base_url}}/assets/img/articles/rename-user-2.png">
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ To setup an incoming Email Account, check on **Enable Incoming** and set your PO
|
||||
|
||||
### How ERPNext handles replies
|
||||
|
||||
In ERPNext when you send an email to a contact like a customer, the sender will be the user who sent the email. In the **Reply-To** property, the email id will be of the default incoming account (like `replies@yourcompany.com`). ERPNext will automatically extract these emails from the incoming account and tag it to the relvant communication
|
||||
In ERPNext when you send an email to a contact like a customer, the sender will be the user who sent the email. In the **Reply-To** property, the Email Address will be of the default incoming account (like `replies@yourcompany.com`). ERPNext will automatically extract these emails from the incoming account and tag it to the relvant communication
|
||||
|
||||
### Notification for unreplied messages
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ To setup an Email Alert:
|
||||
3. Value Change: When a particular value in the selected type changes.
|
||||
4. Days Before / Days After: Trigger this alert a few days before or after the **Reference Date.** To set the days, set **Days Before or After**. This can be useful in reminding you of upcoming due dates or reminding you to follow up on certain leads of quotations.
|
||||
3. Set additional conditions if you want.
|
||||
4. Set the recipients of this alert. The recipient could either be a field of the document or a list of fixed email ids.
|
||||
4. Set the recipients of this alert. The recipient could either be a field of the document or a list of fixed Email Addresses.
|
||||
5. Compose the message
|
||||
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ Or just type "Auto Email Report" on the Search bar.
|
||||
|
||||
#### Step 1
|
||||
|
||||
Select the Report, the user for which you want to create this report (permissions will apply for this user), the email ids where you want this report emailed and the frequency of the report.
|
||||
Select the Report, the user for which you want to create this report (permissions will apply for this user), the Email Addresses where you want this report emailed and the frequency of the report.
|
||||
|
||||
<img class="screenshot" alt="Make Auto Email Report" src="{{docs_base_url}}/assets/img/setup/email/auto-email-1.png">
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@ Issue is an incoming query from your Customer, usually via email or
|
||||
from the “Contact” section of your website. (To fully integrate the Support
|
||||
Ticket to email, see the Email Settings section).
|
||||
|
||||
> Tip: A dedicated support email id is a good way to integrate incoming
|
||||
> Tip: A dedicated support Email Address is a good way to integrate incoming
|
||||
queries via email. For example, you can send support queries to ERPNext at
|
||||
support@erpnext.com and it will automatically create a Issue in the
|
||||
Frappe system.
|
||||
|
||||
@@ -6,4 +6,4 @@
|
||||
|
||||
A newsletter is a short written report that tells about the recent activities of an organization. It is generally sent to members of the organization, potential clients, customers or potential leads.
|
||||
|
||||
This video walks you through managing Newsletter List, master containing email id's to whom Newsletter will be sent. You can compose Newsletter using rich text editor, and also in HTML editor.
|
||||
This video walks you through managing Newsletter List, master containing Email Address's to whom Newsletter will be sent. You can compose Newsletter using rich text editor, and also in HTML editor.
|
||||
|
||||
Reference in New Issue
Block a user