diff --git a/content/8.x/admin/administration-panel/Administration-Panel.adoc b/content/8.x/admin/administration-panel/Administration-Panel.adoc index 86be82814..676f2ff9e 100644 --- a/content/8.x/admin/administration-panel/Administration-Panel.adoc +++ b/content/8.x/admin/administration-panel/Administration-Panel.adoc @@ -68,7 +68,7 @@ image:Admin-Panel-Bottom.png[Admin-Panel-Bottom.png] * link:../../../../admin/administration-panel/developer-tools/#_display_modules_and_subpanels[Display Modules and Subpanels] ** Display Modules and Subpanels -* link:../../../../admin/administration-panel/developer-tools/#_history_subpanel[Hisotry Subpanel] +* link:../../../../admin/administration-panel/developer-tools/#_history_subpanel[History Subpanel] ** History Subpanel * link:../../../../admin/administration-panel/advanced-openadmin/#_aos_settings[Sales Module Settings] @@ -94,36 +94,36 @@ image:Admin-Panel-Bottom.png[Admin-Panel-Bottom.png] ==== Admin Tools -* link:../../../admin/administration-panel/system[System] +* link:../../../../admin/administration-panel/system/[System] ** Repair ** Backups ** Diagnostic Tool -* link:../../../user/introduction/user-interface/record-management/#_importing_records[Importing Records] +* link:../../../../user/introduction/user-interface/record-management/#_importing_records[Importing Records] ** Import Wizard -* link:../../../admin/administration-panel/developer-tools/#_module_loader[Module Loader] +* link:../../../../admin/administration-panel/developer-tools/#_module_loader[Module Loader] ** Module Loader ==== Developer Tools -* link:../../../admin/administration-panel/studio[Studio] +* link:../../../../admin/administration-panel/studio[Studio] ** Studio -* link:../../../admin/administration-panel/developer-tools/#_rename_modules[Developer Tools] +* link:../../../../admin/administration-panel/developer-tools[Developer Tools] ** Rename Modules ** Module Builder ** Dropdown Editor -* link:../../../user/advanced-modules/workflow[Workflows] +* link:../../../../user/advanced-modules/workflow[Workflows] ** Workflow Manager ==== Google Suite -* link:../../../admin/administration-panel/google-sync/#_overview[Google Credentials and Syncing] +* link:../../../../admin/administration-panel/google-sync/#_overview[Google Credentials and Syncing] ** Google Calendar Settings -* link:../../../admin/administration-panel/google-maps/#_google_map_setup[Google Maps] +* link:../../../../admin/administration-panel/google-maps/#_google_map_setup[Google Maps] ** Google Maps Settings ** Geocoding Test ** Geocode Addresses diff --git a/content/8.x/admin/configuration/Sessions-Configuration.adoc b/content/8.x/admin/configuration/Sessions-Configuration.adoc index cb0b4999f..fb8d443c7 100644 --- a/content/8.x/admin/configuration/Sessions-Configuration.adoc +++ b/content/8.x/admin/configuration/Sessions-Configuration.adoc @@ -7,7 +7,7 @@ weight: 30 == Option 1. Changing session dir in php.ini -It is possible to update the global session dir by changing php's link:session.save-path[https://www.php.net/manual/en/session.configuration.php#ini.session.save-path] directive on your php.ini file. +It is possible to update the global session dir by changing php's link:https://www.php.net/manual/en/session.configuration.php#ini.session.save-path[session.save_path] directive on your php.ini file. == Option 2. Changing session dir in SuiteCRM configuration diff --git a/content/8.x/admin/releases/8.5/_index.en.adoc b/content/8.x/admin/releases/8.5/_index.en.adoc index 25a0f16c2..a8f859e78 100644 --- a/content/8.x/admin/releases/8.5/_index.en.adoc +++ b/content/8.x/admin/releases/8.5/_index.en.adoc @@ -76,7 +76,7 @@ If you want to get involved and submit a fix, fork the repo and when ready pleas Please link:https://suitecrm.com/suitecrm-pre-release/[visit the official website] to find the appropriate upgrade package. -To report any security issues please follow our link:../../../community/security-policy[Security Policy] and send them directly to us via email security@suitecrm.com +To report any security issues please follow our link:../../../../community/security-policy[Security Policy] and send them directly to us via email security@suitecrm.com ''' @@ -102,7 +102,7 @@ Angular version has been updated to v16. For development purposes you will need With the upgrade to angular v16 the version of the `@angular-architects/module-federation` lib has also been updated. -Previously built extensions will need to be updated. Please read the link:../../../developer/extensions/frontend/migration/8.5[Frontend extension - Migrate to SuiteCRM 8.5+] guide for information on how to upgrade. +Previously built extensions will need to be updated. Please read the link:../../../developer/extensions/frontend/migration/migration-8.5/[Frontend extension - Migrate to SuiteCRM 8.5+] guide for information on how to upgrade. ==== icon:star[] Enhancements diff --git a/content/8.x/developer/extensions/backend/process-api/process-handler.en.adoc b/content/8.x/developer/extensions/backend/process-api/process-handler.en.adoc index 02be12e74..a75345370 100644 --- a/content/8.x/developer/extensions/backend/process-api/process-handler.en.adoc +++ b/content/8.x/developer/extensions/backend/process-api/process-handler.en.adoc @@ -43,7 +43,7 @@ As a best practice extension backend code should be added to `extensions/> after deployment. Disable this option only for backend modules which will never be shown in the user interface. {{% /notice %}} . Create new data fields. You can also rename default fields from the template. . Customize page layouts for List View, Edit View, Detail View, Sub-panels, Search form, and SuiteCRM Dashlets. -. Create relationships between the new module and other modules. -. Save the package and distribute it. +. Create relationships between the new module and other modules. +. Save the package and distribute it. {{%notice tip %}} Steps 3-5 are optional and can be done in Studio after deployment. {{% /notice %}} @@ -68,9 +68,9 @@ You can choose one of the following options to distribute the package: [cols = "20, 80", frame = "none", grid = "none"] |=== -| *Deploy* | This option is designed to install the custom module on your local SuiteCRM instance and make it available to users in your organization. After deployment, if needed, you can make further changes to the module in Module Builder and deploy it again to update the installed module. However, note that if you change a deployed custom module in Studio and then re-deploy it from Module Builder, all changes made prior in Studio will be lost. +| *Deploy* | This option is designed to install the custom module on your local SuiteCRM instance and make it available to users in your organization. After deployment, if needed, you can make further changes to the module in Module Builder and deploy it again to update the installed module. However, note that if you change a deployed custom module in Studio and then re-deploy it from Module Builder, all changes made prior in Studio will be lost. | *Publish* | This option is designed for distribution to specific users or customers. The system creates a zip file, which you can save on your local machine. You can then email it to one or more individuals who can use the Module Loader to upload the zip file into their SuiteCRM instance. After the module is installed through Studio, you can add or remove fields and make other changes to a published module. -| *Export* | This option is designed for distribution to developers. The system creates a zip file, which you can save on your local machine and share with others. Using the Module Loader, developers can install it on their SuiteCRM instance and customize it further in Module Builder if necessary. The package is visible only in Module Builder and, hence, only administrators can access it until it has been deployed. +| *Export* | This option is designed for distribution to developers. The system creates a zip file, which you can save on your local machine and share with others. Using the Module Loader, developers can install it on their SuiteCRM instance and customize it further in Module Builder if necessary. The package is visible only in Module Builder and, hence, only administrators can access it until it has been deployed. |=== @@ -78,20 +78,20 @@ You can choose one of the following options to distribute the package: image:HistorySubpanel.png["History subpanel settings"] -== Display Modules and Subpanels [[display_modules_subpanels]] +== Display Modules and Subpanels Control which modules and subpanels are visible in *SuiteCRM* by dragging and dropping modules or subpanels between the Displayed and Hidden columns. -This will show or hide modules in *SuiteCRM* for all users. Should you -wish to control access to particular modules, this can be done using -Role Management. See link:../roles-and-security-groups[Roles and Security Groups] +This will show or hide modules in *SuiteCRM* for all users. Should you +wish to control access to particular modules, this can be done using +Role Management. See link:../roles-and-security-groups[Roles and Security Groups] for more information. [cols = "40, 60", frame = "none", grid = "none"] |=== |*Allow users to select modules to apppear in the navigation bar* | -Selecting this option allows users to customise which module tabs are +Selecting this option allows users to customise which module tabs are visible from their User Settings. |=== @@ -99,14 +99,14 @@ image:DisplayModulesandSubpanels.png["Display Modules and Subpanels"] == Module Loader -Module Loader allows you to install and manage custom modules or plugins for your -*SuiteCRM* instance. +Module Loader allows you to install and manage custom modules or plugins for your +*SuiteCRM* instance. -Custom module packages that have been created and modified in Module Builder will +Custom module packages that have been created and modified in Module Builder will be displayed in Module Loader once they have been deployed. For more information on producing packages that can be uploaded using Module Loader, -see the link:../../../developer/module-installer[Developer Guide] +see the link:../../../developer/module-installer[Developer Guide] image:ModuleLoader6.png["Module Loader"] @@ -123,47 +123,47 @@ version number, a short description and whether or not the module can be uninsta btn:[UNINSTALL] and btn:[DELETE PACKAGE] options will appear. -Click btn:[INSTALL] to install the module. +Click btn:[INSTALL] to install the module. image:ModuleLoader2.png["Module Loader"] On the next screen, if there are no problems detected with the package and it is -ready to install you will be asked to click btn:[COMMIT] to complete the installation. +ready to install you will be asked to click btn:[COMMIT] to complete the installation. -If any errors occur during installation, they will be displayed here. -Otherwise, clicking the *Display Log* link will detail the steps +If any errors occur during installation, they will be displayed here. +Otherwise, clicking the *Display Log* link will detail the steps taken in the installation process. image:ModuleLoader5.png["Module Loader"] Click btn:[BACK TO MODULE LOADER] to return to the Module Loader screen where -the newly installed package will appear in the list of installed extensions. +the newly installed package will appear in the list of installed extensions. image:ModuleLoader4.png["Module Loader"] === Uninstall a Package For a package to be uninstallable it needs to be defined as uninstallable in the - package manifest file. For more information regarding the manifest file -see the link:../../../developer/module-installer[Developer Guide] + package manifest file. For more information regarding the manifest file +see the link:../../../developer/module-installer[Developer Guide] Uninstall a package by clicking the buttons next to the -package name. +package name. -As with the install procedure, you will be asked +As with the install procedure, you will be asked to confirm the uninstall on the next screen. If the package added any tables to your -database, you will be asked to if you wish to keep these, and any data within them, for +database, you will be asked to if you wish to keep these, and any data within them, for example if you are replacing an older version of a module with a new one. Click btn:[COMMIT] to uninstall the package. -If any errors occur during the uninstall they will be displayed here. +If any errors occur during the uninstall they will be displayed here. Otherwise, clicking the *Display Log* link will detail the process. Click btn:[BACK TO MODULE LOADER] to return to the Module Loader screen where -the newly installed package will appear in the list of installed extensions. +the newly installed package will appear in the list of installed extensions. -An uninstalled module will be listed in the lower panel from where it can be +An uninstalled module will be listed in the lower panel from where it can be re-installed or deleted. image:ModuleLoader8.png["Module Loader"] @@ -174,9 +174,9 @@ Use this section to configure the module menus on the top navigation bar. image:ConfigureModuleMenuFilters.png["Configure Module Menu Filters"] -Drag modules from the list to the required menu, or delete an item by dragging it to +Drag modules from the list to the required menu, or delete an item by dragging it to the wastepaper bin icon. -Edit the menu name by clicking the pencil icon next to the module name. +Edit the menu name by clicking the pencil icon next to the module name. Delete a menu entirely by clicking the wastepaper bin icon next to the module name. A new custom menu can be added by clicking btn:[ADD FILTER] @@ -188,9 +188,9 @@ Any changes made will not take effect until you click btn:[SAVE & DEPLOY] The Dropdown Editor shows all the dropdown lists currently installed on the system. -Click on the dropdown name to edit it. If you are unsure which dropdown you require, it can be +Click on the dropdown name to edit it. If you are unsure which dropdown you require, it can be easier to edit via Studio where you can find the dropdown by its field name. -See the link:../../administration-panel/studio/#_adding_a_dropdown_field[Studio guide] for full -instructions on adding or editing a dropdown list. +See the link:../../administration-panel/studio/#_adding_a_dropdown_field[Studio guide] for full +instructions on adding or editing a dropdown list. image:StudioDropdownEditor.png["Dropdown Editor"] diff --git a/content/admin/administration-panel/Emails/Email.adoc b/content/admin/administration-panel/Emails/Email.adoc index 43e2ad0e0..5b16ee429 100644 --- a/content/admin/administration-panel/Emails/Email.adoc +++ b/content/admin/administration-panel/Emails/Email.adoc @@ -113,8 +113,7 @@ Once the settings have been verified, click btn:[SAVE] so that these settings are retained before leaving the settings page. ==== Troubleshooting -If the test message was not sent successfully, check the log file in -link:../system#_system_settings[system settings] for any further error messages +If the test message was not sent successfully, check the log file for any further error messages which may assist with resolving the issue. Verify that all port/protocol settings are correct and that the username/password entered is correct and @@ -195,7 +194,7 @@ image:OAuthServerConfiguration.png[OAuth Server Configuration] When setting up with OAuth, you will need the username(email), password and mail server address for the account. -The other required field is `External OAuth Connection`, you can see how to configure this link:InboundEmail-OAuth-HowTo.adoc[here]. +The other required field is `External OAuth Connection`, you can see how to configure this link:../inboundemail-oauth-howto[here]. ==== Email Handling Options @@ -352,7 +351,7 @@ image:EmailCampaignSettings.png[Campaign Settings] Scheduled campaign emails are queued here until the scheduled job runs to send them out. By default this is the *Run Nightly Mass Email Campaigns* scheduled job. -See the link:../system/#_scheduler[Scheduler] section for +See the link:../../system/#_scheduler[Scheduler] section for further information on scheduled jobs. Click btn:[SEND QUEUED CAMPAIGN EMAILS] to send them immediately without waiting for the scheduler to do so. diff --git a/content/user/advanced-modules/Cases with Portal.adoc b/content/user/advanced-modules/Cases with Portal.adoc index 2265b5712..4f9c59d84 100644 --- a/content/user/advanced-modules/Cases with Portal.adoc +++ b/content/user/advanced-modules/Cases with Portal.adoc @@ -2,7 +2,7 @@ Title: Cases with Portal Weight: 250 --- - + :experimental: ////this is here to allow btn:[]syntax used below :imagesdir: /images/en/user @@ -33,13 +33,13 @@ threaded log of all updates Emails Advanced OpenPortal (AOP) uses the standard SuiteCRM functionality to send emails and create cases from inbound emails. Details on how to configure your outgoing email settings can be found -link:../../../admin/administration-panel/email/#_outgoing_mail_configuration[here]. +link:../../../admin/administration-panel/emails/email/#_outgoing_mail_configuration[here]. Details on how to set up a group email account which will -automatically generate cases can be found link:../../../admin/administration-panel/email/#_group_email_account[here]. +automatically generate cases can be found link:../../../admin/administration-panel/emails/email/#_group_email_account[here]. == Downloading -The plug-in can be downloaded for free from the SuiteCRM site at +The plug-in can be downloaded for free from the SuiteCRM site at the https://suitecrm.com/resources/suitecrm-joomla-portal-plug-in/[Joomla Portal Plug-in page^]. == Installation & Configuration diff --git a/content/user/core-modules/Emails.adoc b/content/user/core-modules/Emails.adoc index 5c4800a39..5e82bc0aa 100644 --- a/content/user/core-modules/Emails.adoc +++ b/content/user/core-modules/Emails.adoc @@ -11,133 +11,133 @@ Weight: 140 = Emails {{% notice note %}} -This documentation is for *SuiteCRM* versions 7.9.x and later. For earlier versions of *SuiteCRM*, +This documentation is for *SuiteCRM* versions 7.9.x and later. For earlier versions of *SuiteCRM*, please see link:../emails-lts/[Emails-LTS]. {{% /notice %}} -{{%notice warning %}}If you are upgrading from a version of *SuiteCRM* prior to 7.9.x, +{{%notice warning %}}If you are upgrading from a version of *SuiteCRM* prior to 7.9.x, please see the *Upgrading* section of this document.{{% /notice%}} == Overview -The *Emails* module in *SuiteCRM* allows Users to view, store, compose, send and receive email -from their own personal email account or a shared inbox, for example a Support or Sales inbox. -Emails can be imported and associated with a related *SuiteCRM* record, for example a Contact or an Account. +The *Emails* module in *SuiteCRM* allows Users to view, store, compose, send and receive email +from their own personal email account or a shared inbox, for example a Support or Sales inbox. +Emails can be imported and associated with a related *SuiteCRM* record, for example a Contact or an Account. These related emails can then be viewed on the history subpanel of the related record. {{% notice note %}} -You will need to set up and have access to at least one *personal* or *group* email account in order to use -the *Emails* module. See link:../../introduction/managing-user-accounts#_personal_email_account_settings[Personal Email Settings] -for information on setting up a personal email account. For information on configuring group, -bounce handling and the system outbound mail accounts, please see -the link:../../../admin/administration-panel/email[Emails] section of the Administrator Guide. +You will need to set up and have access to at least one *personal* or *group* email account in order to use +the *Emails* module. See link:../../introduction/managing-user-accounts#_personal_email_account_settings[Personal Email Settings] +for information on setting up a personal email account. For information on configuring group, +bounce handling and the system outbound mail accounts, please see +the link:../../../admin/administration-panel/emails[Emails] section of the Administrator Guide. {{% /notice %}} -The *Emails* Module can be found on the *ALL* menu on the top navigation bar. +The *Emails* Module can be found on the *ALL* menu on the top navigation bar. The module opens in List View, showing all the mail from the default mail account inbox in the main window. image:250EmailsListView.png[title="Emails Module List View"] [cols = "20,80",frame="none", grid="none" ] |=== -|image:251EmailsInboxButton.png[title="Current inbox indicator button"]|The current inbox name is displayed on -the button to the top right-hand side of the list view. Use this button to switch between accounts or other +|image:251EmailsInboxButton.png[title="Current inbox indicator button"]|The current inbox name is displayed on +the button to the top right-hand side of the list view. Use this button to switch between accounts or other monitored folders. |image:257aEmailsUnreadMail.png[title="Unread Email"]|Unread emails have a purple highlight. |image:257bEmailsAttachmentIcon.png[title="Email attachment icon"]|Attachments are indicated by a paperclip. -|image:257EmailsImportedIcon.png[title="Imported mail icon"]|Emails which have +|image:257EmailsImportedIcon.png[title="Imported mail icon"]|Emails which have been <> into *SuiteCRM* are indicated by a tick. -|image:258EmailsFlaggedIcon.png[title="Flagged mail icon"]|Emails which have been flagged for follow +|image:258EmailsFlaggedIcon.png[title="Flagged mail icon"]|Emails which have been flagged for follow up are indicated by an exclamation mark. |=== -As in other *SuiteCRM* modules, emails can be sorted by clicking on the column headings. Filter and column +As in other *SuiteCRM* modules, emails can be sorted by clicking on the column headings. Filter and column selections can also be made in the same way as for other modules. -The main actions for the *Emails* module are contained within the buttons on the *Emails* toolbar. Hover +The main actions for the *Emails* module are contained within the buttons on the *Emails* toolbar. Hover over these buttons to see the explanatory tooltip for each function. [cols="15,10,75",frame="none", grid="none"] |=== -|image:253EmailsBulkAction.png[title="Bulk Action button"]|*Bulk Action*|Use the Bulk Action dropdown to -bulk <>, to mark mail as read/unread or to flag mail for follow up. Multiple +|image:253EmailsBulkAction.png[title="Bulk Action button"]|*Bulk Action*|Use the Bulk Action dropdown to +bulk <>, to mark mail as read/unread or to flag mail for follow up. Multiple emails can be selected in list view using the checkboxes. -|image:252EmailsComposebutton.png[title="Compose Mail button"]|*Compose Mail* |Opens the <> window to +|image:252EmailsComposebutton.png[title="Compose Mail button"]|*Compose Mail* |Opens the <> window to create a new message. -|image:254EmailsSettingsButton.png[title="Mail Settings button"]|*Settings*|Shortcut to your user profile where -you can edit your link:../../introduction/managing-user-accounts#_personal_email_account_settings[user profile email settings]. +|image:254EmailsSettingsButton.png[title="Mail Settings button"]|*Settings*|Shortcut to your user profile where +you can edit your link:../../introduction/managing-user-accounts#_personal_email_account_settings[user profile email settings]. Add and remove accounts and select folders to view here. -|image:255EmailsCheckForMailButton.png[title="Check for Mail button"]|*Check For Mail*| For personal email -accounts, you can check for new mail with this button . Note that for Group email accounts, checking for email -is done automatically via the *Check Inbound Mailboxes* Scheduler. You will need to ensure that your cron +|image:255EmailsCheckForMailButton.png[title="Check for Mail button"]|*Check For Mail*| For personal email +accounts, you can check for new mail with this button . Note that for Group email accounts, checking for email +is done automatically via the *Check Inbound Mailboxes* Scheduler. You will need to ensure that your cron settings are correct for the scheduler to run. Please see link for further information on Schedulers. -|image:256EmailsChangeFolderButton.png[title="Select Folder button"]|*Select Folder*|This allows you to -select which monitored folder you wish to view. If you have more than one account set up, you can also -switch between accounts with this button. Expanding an account in the list will show all the monitored +|image:256EmailsChangeFolderButton.png[title="Select Folder button"]|*Select Folder*|This allows you to +select which monitored folder you wish to view. If you have more than one account set up, you can also +switch between accounts with this button. Expanding an account in the list will show all the monitored folders for the account. Select the required folder. |=== === Read Mail -Click on the subject line of an email to open it in *Detail* view. Use the *Actions* menu to reply to, +Click on the subject line of an email to open it in *Detail* view. Use the *Actions* menu to reply to, forward or <> the email. image:269EmailsActionMenu.png[title="Action menu"] === Compose Mail -Click the Compose Mail button or select *Compose* from the *Sidebar* to open a new compose window. +Click the Compose Mail button or select *Compose* from the *Sidebar* to open a new compose window. -Emails can also be composed directly from a *SuiteCRM* record by clicking the email address on the record. -This will open compose view in the *Emails* module. For new emails opened in this way, the *To:* field -will be automatically populated and the email will related to the relevant record. +Emails can also be composed directly from a *SuiteCRM* record by clicking the email address on the record. +This will open compose view in the *Emails* module. For new emails opened in this way, the *To:* field +will be automatically populated and the email will related to the relevant record. -{{% notice note %}}If you have opted to use an external email client in your link:../../introduction/managing-user-accounts#_personal_email_account_settings[user profile email settings], clicking an +{{% notice note %}}If you have opted to use an external email client in your link:../../introduction/managing-user-accounts#_personal_email_account_settings[user profile email settings], clicking an email address on a record in *SuiteCRM* will open a new email in your chosen editor. {{% /notice %}} image:260Emailcompose.png[title="Compose Email"] -* *Email Template:* Select a template if required. See link:../emailtemplates/[Email Templates] for more information -on creating and editing email templates. Once you have selected a template, a popup will warn you that the subject -line and body of the email will be replaced by the contents of the email template. If you are using a template with -variables, these will be populated with the relevant data from the related record when the email is sent. The *To:* field +* *Email Template:* Select a template if required. See link:../emailtemplates/[Email Templates] for more information +on creating and editing email templates. Once you have selected a template, a popup will warn you that the subject +line and body of the email will be replaced by the contents of the email template. If you are using a template with +variables, these will be populated with the relevant data from the related record when the email is sent. The *To:* field will also be automatically populated with the email address associated with the related record. // image:261EmailsAddtemplate.png[title="Adding Email template warning"] -* *Related To:* To associate the email with a particular record, select the module (e.g. Accounts, Contacts, Leads) -and then click the Search arrow to search for the record. Alternatively, you can begin typing the name into the field +* *Related To:* To associate the email with a particular record, select the module (e.g. Accounts, Contacts, Leads) +and then click the Search arrow to search for the record. Alternatively, you can begin typing the name into the field and select the relevant record from the auto-complete list which appears. -* *From:* If you have more than one email account configured, select the account from which to send the email. +* *From:* If you have more than one email account configured, select the account from which to send the email. The *Reply To* and *From* settings for the selected account are displayed alongside for information. -* *To:* Selecting a related record in the with a valid email address will automatically populate the *To:* field. -Alternatively, the *To:*, *Cc:* and *Bcc:* fields can be populated manually or via the select buttons which appear +* *To:* Selecting a related record in the with a valid email address will automatically populate the *To:* field. +Alternatively, the *To:*, *Cc:* and *Bcc:* fields can be populated manually or via the select buttons which appear when you click inside the fields. -* *Body:* If you have configured a signature for this account in your -link:../../introduction/managing-user-accounts/#_user_profile_email_settings[user profile email settings], this will appear +* *Body:* If you have configured a signature for this account in your +link:../../introduction/managing-user-accounts/#_user_profile_email_settings[user profile email settings], this will appear automatically in the body of the email. The toolbar at the bottom of the *Compose* view has the following buttons: [cols="10,10,80",frame="none", grid="none"] |=== -|image:263EmailsSendMailbutton.png[title="Send Mail button"]|*Send Mail* |A confirmation message will appear when +|image:263EmailsSendMailbutton.png[title="Send Mail button"]|*Send Mail* |A confirmation message will appear when the message has been sent. -|image:264EmailsAddFilesbutton.png[title="Add Files button"]|*Attach Files*| Use this button to browse for and attach +|image:264EmailsAddFilesbutton.png[title="Add Files button"]|*Attach Files*| Use this button to browse for and attach an *external* file to the email. -|image:265EmailsAddDocumentsbutton.png[title="Add Documents button"]|*Attach Documents*|Use this button to attach +|image:265EmailsAddDocumentsbutton.png[title="Add Documents button"]|*Attach Documents*|Use this button to attach a *SuiteCRM Document* to the email. Search for the required Document in the popup and click btn:[SELECT] to attach it. -|image:266EmailsSaveDraftbutton.png[title="Save Draft button"]|*Save Draft*|Drafts can be viewed +|image:266EmailsSaveDraftbutton.png[title="Save Draft button"]|*Save Draft*|Drafts can be viewed by changing the folder in *List* view. |image:267EmailsDiscardbutton.png[title="Discard button"]|*Discard*|Discards the draft email without sending. |=== === Import Mail -Email can be imported into *SuiteCRM* and associated with a relevant *SuiteCRM* record (e.g. a contact or account record). +Email can be imported into *SuiteCRM* and associated with a relevant *SuiteCRM* record (e.g. a contact or account record). This can be very useful in keeping a history of communication with a client, for example. Emails which have been imported and related to a record in *SuiteCRM* can be viewed from the record's history subpanel. @@ -149,46 +149,46 @@ image:268bEmailsImport.png[title="Import emails"] ==== Import One or More Emails -One or more emails can be imported at the same time from *List* view. +One or more emails can be imported at the same time from *List* view. -Select the email(s) you wish to import using the checkboxes to the left-hand side of the view. +Select the email(s) you wish to import using the checkboxes to the left-hand side of the view. Select *Import* from the *Bulk Action* menu. image:268aEmailsImport.png[title="Import emails"] -On importing, a dialog will open allowing you to select which record to relate the email(s) to. +On importing, a dialog will open allowing you to select which record to relate the email(s) to. image:268EmailsImportDialog.png[title="Import emails"] -First select the module type from the drop-down. Next, use the search arrow button to find and select the relevant record, +First select the module type from the drop-down. Next, use the search arrow button to find and select the relevant record, or begin typing the name into the field and select the required record from the auto-complete list. Click the btn:[OK] button. -Note that if you are bulk importing mail, all emails will be related to the record selected here. If you need to relate mail +Note that if you are bulk importing mail, all emails will be related to the record selected here. If you need to relate mail to different records you will need to import these individually. -*SuiteCRM* can also be configured to automatically import emails for group mail accounts. -See link:../../../admin/administration-panel/email/#_group_email_account[Group Email Accounts] for more information. +*SuiteCRM* can also be configured to automatically import emails for group mail accounts. +See link:../../../admin/administration-panel/emails/email/#_group_email_account[Group Email Accounts] for more information. === Delete Mail -As only imported emails are stored in *SuiteCRM*, only imported email records can be deleted from the *Emails* module. +As only imported emails are stored in *SuiteCRM*, only imported email records can be deleted from the *Emails* module. -To delete an imported email record, open the email and then select Delete from the Actions menu dropdown. Note that this -will only delete the SuiteCRM record and not the imap message. To remove emails from the Emails module, you will need to +To delete an imported email record, open the email and then select Delete from the Actions menu dropdown. Note that this +will only delete the SuiteCRM record and not the imap message. To remove emails from the Emails module, you will need to move or delete them using your external mail client. == Changes To Emails Module -Prior to version 7.9, *SuiteCRM* had to synchronise the email headers before users could view them. As of -version 7.9, *SuiteCRM* contacts the email server directly - retrieving only the minimal information needed to process an operation. -This eliminates the synchronisation process and significantly reduces amount of email information needed to be stored in the database. +Prior to version 7.9, *SuiteCRM* had to synchronise the email headers before users could view them. As of +version 7.9, *SuiteCRM* contacts the email server directly - retrieving only the minimal information needed to process an operation. +This eliminates the synchronisation process and significantly reduces amount of email information needed to be stored in the database. Note to developers and administrators: The 'email_cache' table is deprecated in *SuiteCRM* 7.9. === Upgrading -If you are upgrading from a version of *SuiteCRM* prior to *7.9.x*, you will need to use the *Sync Inbound Email Account Tool* on -upgrading. This tool will synchronise mail already imported into *SuiteCRM* with your current IMAP accounts so that you will not +If you are upgrading from a version of *SuiteCRM* prior to *7.9.x*, you will need to use the *Sync Inbound Email Account Tool* on +upgrading. This tool will synchronise mail already imported into *SuiteCRM* with your current IMAP accounts so that you will not have to synchronise in the future. We recommend taking a backup of your database and instance before upgrading. === Sync Inbound Emails Accounts Tool @@ -202,7 +202,7 @@ This will display a multiple selection box *Mail Account Name* listing all of th [cols="20,80",frame="none", grid="none"] |=== |image:SyncInboundEmailAccounts2.png[Select accounts to sync] -|Select the required accounts from the multiple selection box (use *ctrl + click* to select more than one) and click btn:[SYNC]. +|Select the required accounts from the multiple selection box (use *ctrl + click* to select more than one) and click btn:[SYNC]. |=== The page will refresh and list the progression of the tool.