10. Configuration

The configuration menu on Integria IMS redirects to the general configuration screen for the application. The menu on the left includes other features we call System Tools. We'll detail both, one as Configuration Options (the tabs inside the setup section) and the other as System Tools (menu options).

These sections are restricted and only the user marked as admin can 
access these settings.  

Configuration Options

General Configuration

In the General Configuration section different general aspects of Integria IMS can be configured.

  • Language: This will be the system's global language. Each user can have a personal language configuration, that overwrites the value defined here.
  • Site Name: website name, visible on the title of all windows. This name will also be placed in the subject for all messages. It can be left blank.
  • Error log: a file named integria.log. This file will compile errors generated by the application.
  • List of IP's with API access: IPs separated by commas, with access to the API. An [*] means “any”.
  • API Password: password needed to perform API requests.
  • Max. Upload Filesize: defines the size limit of a file that may be uploaded to the application. If it has a smaller size on the system (PHP configuration) this limit may be bypassed. If you encounter issues when uploading large files it can also be due to more advanced PHP parameters.
  • Enable Newsletter: you can entirely disable the newsletter feature from here.
  • First day of the week: For calendars and other application functions.
  • URL update manager: address of the update server for Integria
  • Enable HTTPS access: configure Integria IMS to use HTTPS protocol.
  • Access port: configure the access port to the server.
  • Public access to the server: URL for public access to the server. It can be an IP or a URL address. If used on a local environment this parameter will be the same IP as for server access.
The parameter for public access to the server is used when generating newsletters to gather the number of views. 
  • CSV encoding type: default coding type for the .csv files.
  • Enable update manager updates: enables update warnings when available.

Visual Configuration

In this section some of the options that define the general appearance of the system may be configured. You can modify the following options:

  • Site Logo. It's the logo that is shown on the login screen.
  • Graphs in Flash. Globally activates/deactivates the use of Flash graphs.
  • Header logo. Shown on the login screen, on the left.
  • PDF Font. This value can be changed in order to modify the font on PDF files. There is a special font named “unicode” which will allow all types of caligraphies for reports to be used (Japanese, Korean, Chinese, Arabic…).
  • Login background. Background image shown on the login screen.
  • Source for Graphs. For legends and characters available in graphs.
  • Size of page block. Quantity of listed elements. Don't place a very large value, since it'll affect the system's performance negatively.
  • Size of graph font. Dictates the size of the font for graphs.

Password Management Configuration

Managing the password policy excludes users considered administrators. It's an Enterprise feature.

  • Activate password policy. If inactive, the other parameters will not be applied.
  • Minimum password length
  • Numbers in password. The password must include numerals.
  • Symbols in the password. The password must include special characters.
  • Expiration date. In days.
  • Force password change upon first login.
  • User timeout timer. Measured in minutes. After a configurable number of failed login attempts, the user will not be able to login (even if he or she places the correct password) until the time marked has passed.
  • Máx. number of login attempts.

Ticket Configuration

Visual Options

  • Show ticket creator: same as above, applied to the ticket creator.
  • See ticket owner: shows the owner or user assigned to the ticket in the ticket search.
  • Max. tickets per search: limit on results in ticket searches, to avoid impacts on performance due to excessively large searches.
  • Enable Quick Edit Mode
  • Display the username instead of the id in the ticket search: real name instead of ID.
  • Date format: there are two format options: long format yyyy/mm/dd h:m:s (selected by default) and approximate format: 1day, 2hours
  • Date of completion: Ticking this option will display the 'Date of completion' field in the ticket workunits.
  • Sort WU by date of completion

Ticket Behavior:

  • Disable incident ratings
  • Enable IW to change the creator: users with that access bit can change the ticket creator.
  • Editor adds WU in ticket creation: a WU is added automatically when a ticket is created.
  • Allow to change the ticket type: if it is deactivated, it will not be possible to change the type once it has been created.
  • Allow to set the time/date of the ticket when creating it
  • Ignore user defined by group for owner
  • Type of request required: obliges us to choose a ticket type.
  • Ignore default user creator: must be specified manually.
  • Allow modification of the creator user and the owner user
  • Allow external users (not grouped) to modify their tickets
  • Ignore group template to incident creator
  • Creator user can see all users
  • Auto-allocate ticket
  • Incident editor is the first editing user: if checked, the ticket's editor will be set as the user who edited the ticket in the first place.

WU Options:

  • Automatic ticket closure: Number of hours a ticket will be automatically closed after.
  • Default time WU of the ticket: default value used when entering a Workunit, in hours. 0.25 will be 15 minutes.

Workflows:

  • Process closed tickets: This option allows the Workflow rules to process closed tickets.
  • Days that closed tickets are checked: if the previous field is checked (Process closed tickets), closed tickets in the last XX days will be taken into account.

Email sending options:

  • Send email with each ticket update: emails will be sent when a ticket is modified.
  • Send by mail all attachments for each incident update

This configuration can be general or group-specific, so it will be necessary to configure it when editing each group:

  • Send email for each ticket creation
  • Send email for every ticket closure
  • Send email for each ticket status update
  • Send email for each ticket owner update
  • Send email for each ticket priority update
  • Send email for each ticket group update
  • Send email for each update of any ticket field
  • Send email for each Work Unit
  • Send email for every attachment
  • Send email for each validation of part of the work

Customization:

  • Tags attached to status and ticket resolutions can be modified. It is important to note that even if the tag changes, the logic associated with the status will remain the same, so the rules of SLA, workflow, or ticket colors according to their status (new/closed) will remain the same.
  • The non-working days are used to define local/national holidays, etc. and are displayed differently in calendars. They are not taken into account in SLAs (except those that also include public holidays).
  • The Anonymous Incidents option allows that when emails are sent, user addresses are hidden to prevent external users from seeing the email addresses of all recipients.

Email configuration

In the email configuration section many aspects referring to the emails that Integria IMS sends automatically on various occasions can be configured. SMTP protocol is used for email sending. For example, when changes are made on a ticket or an SLA is not met. POP/IMAP protocol is used to manage incoming tickets. This last option is only necessary if you want to manage the replies for emails or ticket creating via email.

In this section you may also change global paramaters for emails such as headers, footers, send address, notification period, etc.

  • Notification period: the minimum time that has to pass between two SLA notifications. Defined in hours.
  • Original system email address: address from which email will be sent via Integria.

SMTP configuration

Credentials and data are defined in order to connect to your SMTP server. If left blank, the system will try to create a local mail system on the same device on which Integria is running (generally sendmail or an equivalent).

  • SMTP resend tries: once the number set is exceeded, Integria will mark the message as “incorrect”.
  • Max. number of pending messages: once the number set is exceeded, Integria will show a warning on the systems alert area to indicate thtere may be problem with email delivery. This also can be monitored externally via the API.
  • Max. number of messages sent per execution: emails sent each time a background process is executed. Here we can specify for it not to send over a maximum number each time. Useful if our server won't allow us to send over X amount of messages per hour, for example.

Gmail:

  • No encryption: Gmail does not allow us to send emails without encryption, so at least we must configure the encryption as STARTTLS, which can be used in ports 25 or 587.
  • With encryption:
    • STARTTLS:
      • As we can see in the picture, we configure:
        • Encryption method: STARTTLS
        • SMTP Host: smtp.gmail.com
        • Port: 587 (25 could also be used)
    • SSL and different versions:
      • As we can see in the previous picture, we configure:
        • Encryption method: SSL/TLS.
        • SMPT Host: smptp.gmail.com.
        • Port: 465.
  • Note: With the test button, we can test if our configuration is valid.

Outlook

  • No encryption:
    • Outlook does not allow us to send emails without encryption, so at least we must configure the encryption as STARTTLS, which can be used in ports 25 or 587.
  • With encryption:
    • STARTTLS:
      • As we can see in the previous picture, we configure:
        • Encryption method: STARTTLS
  • SMTP Host: smtp-mail.outlook.com
  • Port: 587 (25 could also be used)
    • SSL and different versions: It does not allow this type of encryption, only STARTTLS.
  • Note:
    • With the test button, we can test if our configuration is valid.
    • Outlook does not allow to use users from other mail services , only their own ones , so it is necessary to specify the same mail that is used for the SMTP configuration.

Office365:

  • No encryption: Office365 does not allow us to send emails without encryption, soat least we must configure the encryption as STARTTLS, which can be used in ports 25 or 587.
  • With encryption:
    • STARTTLS:
      • As we can see in the previous picture, we have:
        • Encryption method: STARTTLS
        • SMTP Host: smtp.office365.com
        • Port: 587 (25 could also be used)
    • SSL and different versions: It does not allow this type of encryption, only STARTTLS.
  • Note:
    • With the test button, we can test if our configuration is valid.
    • Office does not allow to use users from other mail services , only their own ones , so it is necessary to specify the same mail that is used for the SMTP configuration.

Others:

  • Encryption: We can configure the mail server without encryption or with SSL/TLS, SSLv2, SSLv3 or STARTTLS.
  • Name: DNS name or IP address of the mail server.
  • Port: Port on which the mail server is listening.
  • User: User configured on the mail server.
  • Password: Password configured for the user indicated above.

IMAP/POP configuration

Important: Try not to use the IMAP/POP account of any internal Integria IMS user, as this may cause some strange behavior when creating and updating tickets in Integria IMS.

Gmail:

  • Allows only this setting: (SSL/TLS):
    • IMAP:
    • POP:
  • Name: imap.gmail.com / pop.gmail.com
  • Port: 993(IMAP)/995(POP)
  • Protocol Selection: POP/IMAP
  • Compatibility: Gmail.
  • Note: It is not recommended to use the accept all certificates option as it would not validate certificates for encryption.
  • Once configured, we need to choose a group of Integria IMS in which we want the tickets of the emails of this account to be created and we edit the group:
    • People → Access Control → Group Management → Edit the group that we want:
    • In order for a user (external from Integrate IMS) to create a ticket through an email:
      • User self-creation: Allows you to create a new Integria IMS user, Which will match the name of the email. This option must be enabled.
      • User access permissions to create tickets Allows the user to create the necessary permissions for ticket editing. This option must be enabled.
      • Welcome message: Send a welcome message to the created user. This option is optional.
      • Ticket Status: Allows you to choose the status of the created ticket. New is the default option.
      • User type: It allows to choose the type of user that will be the created user. External user is the default option.
      • Company: It allows to select to which company the created ticket will belong. This option is optional.
      • Specific profile: Allows you to select the profile of the created user. External is the default option.
      • Ticket type: Select the type of ticket to which the ticket created will belong. This option is optional.
      • Email Queue: It must match with the name of the POP/IMAP configuration.
  • Gmail settings: You must enable the protocol to use (POP/IMAP) in the email account and in the case of using POP, allow it to delete the mails so that the tool can work correctly.

Outlook:

  • Allows only this setting: (SSL/TLS):
    • IMAP:
    • POP:
  • Name: imap-mail.outlook.com / pop-mail.outlook.com
  • Port: 993(IMAP)/995(POP)
  • Protocol Selection: POP/IMAP
  • Compatibility: outlook.
  • Note: It is not recommended to use the accept all certificates option as it would not validate certificates for encryption.
  • Once configured, we need to choose a group of Integria IMS in which we want the tickets of the emails of this account to be created and we edit the group:
    • People → Access Control → Group Management → Edit the group that we want:
    • In order for a user (external from Integrate IMS) to create a ticket through an email:
      • User self-creation: Allows you to create a new Integria IMS user, Which will match the name of the email. This option must be enabled.
      • User access permissions to create tickets Allows the user to create the necessary permissions for ticket editing. This option must be enabled.
      • Welcome message: Send a welcome message to the created user. This option is optional.
      • Ticket Status: Allows you to choose the status of the created ticket. New is the default option.
      • User type: It allows to choose the type of user that will be the created user. External user is the default option.
      • Company: It allows to select to which company the created ticket will belong. This option is optional.
      • Specific profile: Allows you to select the profile of the created user. External is the default option.
      • Ticket type: Select the type of ticket to which the ticket created will belong. This option is optional.
      • Email Queue: It must match with the name of the POP/IMAP configuration.
  • Outlook settings: You must enable the protocol to use (POP/IMAP) in the email account and in the case of using POP, allow it to delete the mails so that the tool can work correctly.

Office365:

  • Allows only this setting: (SSL/TLS):
    • IMAP:
    • POP:
  • Name: outlook.office365.com valido tanto para POP/IMAP
  • Port: 993(IMAP)/995(POP)
  • Protocol Selection: POP/IMAP
  • Compatibility: Office365.
  • Note: It is not recommended to use the accept all certificates option as it would not validate certificates for encryption.
  • Once configured, we need to choose a group of Integria IMS in which we want the tickets of the emails of this account to be created and we edit the group:
    • People → Access Control → Group Management → Edit the group that we want:
    • In order for a user (external from Integrate IMS) to create a ticket through an email:
      • User self-creation: Allows you to create a new Integria IMS user, Which will match the name of the email. This option must be enabled.
      • User access permissions to create tickets Allows the user to create the necessary permissions for ticket editing. This option must be enabled.
      • Welcome message: Send a welcome message to the created user. This option is optional.
      • Ticket Status: Allows you to choose the status of the created ticket. New is the default option.
      • User type: It allows to choose the type of user that will be the created user. External user is the default option.
      • Company: It allows to select to which company the created ticket will belong. This option is optional.
      • Specific profile: Allows you to select the profile of the created user. External is the default option.
      • Ticket type: Select the type of ticket to which the ticket created will belong. This option is optional.
      • Email Queue: It must match with the name of the POP/IMAP configuration.
  • Office365 settings: You must enable the protocol to use (POP/IMAP) in the email account and in the case of using POP, allow it to delete the mails so that the tool can work correctly.

Others:

  • Encryption: We can configure the POP/IMAP server without encryption or with SSL/TLS, SSLv2, SSLv3 or STARTTLS.
  • Name: IP or DNS of the POP/IMAP server.
  • Port: Port on which the POP/IMAP server is listening.
  • User: User configured on the mail server.
  • Password: Password configured for the user indicated above.
  • Protocol: POP o IMAP
  • Compatibility: other
  • Accept all certificates: Click if you want to accept any certificate, even the self-signed ones.

Configuring the message sending queue

Integria queues emails which are then sent (by default) every five minutes (integria cron) by a maintenance script. To adjust this behavior there are a series of special paramaters, alongside a queue manager for pending outgoing messages.

* **Message Header**: sets the header for the message that will be sent through the automatic process on Integria IMS. It does not support macros.
* **Message Footer**: footer for the message that will be sent through the automatic process on Integria IMS. It may be left  blank, as can the header. It's sent as plain text (simple ASCII).

Email sending queue management

This system allows viewing of those messages that are pending delivery and their status. Plus, here we can delete the current queue and/or resend those email marked as invalid.

Message Templates

This section is meant to be able to edit message templates that Integria will use to compose emails as well as “subject” templates for messages. Message templates are generic and are used for all groups.

To edit a template choose one and click on the “edit” button. You can see that there are special markings in the style of _sitename_. We call these macros. These macros are variables that will be substituted at the moment of composing the message for a concrete and real value. At this time the following macros are defined:

  • _sitename_: sitename as has been previously defined in the Setup.
  • _incident_title_: ticket title.
  • _username_: name of the user who receives the email (login name)
  • _fullname_: full name of the recipient.
  • _incident_id: ticket ID.
  • _url_: ticket URL.
  • _creation_timestamp_: date/time of ticket creation.
  • _update_timestamp_: timestamps last time a ticket was updated.
  • _owner_: User that controls a ticket.
  • _group_: group assigned to a ticket.
  • _author_: ticket author
  • _priority_: ticket priority
  • _status_: ticket status
  • _resolution_: ticket solution
  • _time_used_: total time used on a ticket
  • _incident_main_text_: main descriptive text for a ticket
  • _wu_user_: User who reports on a WorkUnit
  • _wu_text_: WorkUnit text
  • _havecost_: for reports on the project's WorkUnits only.
  • _taskname_: for project reports only
  • _projectname_: for project reports only
  • Custom field templates: this allows, when creating an object type, for the names of custom fields that are added to be included as a macro, which in turn will show the value for said field: _custom field name_.

This option has the purpose of “hiding” certain parts of Integria from certain user groups. This is an Enterprise feature. The following levels of visibility can be configured for each section or group:

  • Hidden: won't be shown for whoever has permissions over the selected group.
  • Minimum: will be shown for those who have permissions over the selected group, but it's limited only to the section's basic parts.
  • Limited: will be shown for whoever has permissions over the selected group although, certain parts of the section may be hidden.
  • Complete: users with permissions over the selected group will have total access to the section.

Additional information:

  • If a section doesn't have any visibility configuration, by default the access will be complete for all users.
  • Each section has a profile assigned. This profile is checked alongside the user group in order to know if it has visibility or not. The links or associations are as follows:
    • Projects ⇒ 'PR'
    • Tickets ⇒ 'IR'
    • Inventories ⇒ 'VR'
    • KB ⇒ 'KR'
    • File releases ⇒ 'KR'
    • Planner ⇒ 'AR'
    • People ⇒ Any profile
    • Work Orders ⇒ 'WOR'
    • Configuration ⇒ Any profile
  • If the user is an admin they'll always have complete access, independent from the menu's visibility settings.
  • If a user has profiles assigned to various groups that have different levels of visibility in one section, visibility for that user in that section will be the least restrictive.
  • If a visibility level is created for a section by selecting all groups (group 'ALL') all settings for that section will be deleted, and only the one entered will remain.

Pandora FMS inventory

This section includes both the inventory options and the automatic integration of Pandora's inventory with Integria's, and the management of remote inventory (data processing sent to Integria by Pandora agents, without installing Pandora FMS).

Inventory options

  • Duplicated inventory names: It allows you to have names of inventory objects with the same name but by default this will be disabled.
  • CSV import compatibility: If the option is disabled, CSVs will be displayed as a report showing the inventory objects previously selected by the user just as they are shown in the list. But by default it will be activated to allow import, therefore ids will be shown, etc.

Data processing on the inventory from Pandora FMS agents

  • Default owner: the default owner for those objects.
  • Related company and associated user: Companies with access to those objects, and users with access to those objects.

Authentication

  • Authentication type: LDAP, Active Directory or local. If LDAP or AD are used, local admin type users will be the only users to function “locally” without authenticating through LDAP. If anything fails, you may do this locally with admin users.

If LDAP login or Active Directory are configured Integria will “ask” those platforms if the user exists and if the password is correct, trying to login via an LDAPO query. If successful, the user will be able to access Integria. The fields that can be configured (once the LDAP option is enabled).

  • Session Timeout: in seconds.
  • Autocreate remote users: This option makes it possible for first-time users to be created automatically if they are an LDAP/AD user. If the option isn't enabled, the user should already exist in Integria, and the password coincide with the LDAP one.
  • Autocreate profile: this field makes it possible to assign a profile type to users that are created automatically.
  • Autocreate profile group: this field makes it possible to assign a group to the users that are created automatically.
  • Autocreate blacklist: list of users, separated by commas, who won't be able to access.
  • LDAP server: IP or FQDN of the LDAP server is defined.
  • LDAP port
  • LDAP version
  • Start TLS: it will use the Transport Layer Security (TLS) protocol in communications between client and server.
  • Base DN: Distinguised Name (DN) used by the LDAP server. For example: ou=People,dc=example,dc=com
  • Login attribute: Login attribute that LDAP uses during the authentication process. For example UID (User Identification Code).
  • Domain (AD only)

LDAP configuration example

The domain will be example.com and the LDAP server IP 192.168.X.X. This is what the configuration is like:

Configuration example for the Active Directory

CRM

This section controls the entire CRM-specific configuration.

  • Logo for invoice headers
  • Tax name. In Spain, for example, this would be IVA; in the UK, VAT.
  • Invoice header. Data that we wish to show on the invoice header.
  • Invoice footer. Text that is added in small print on the footer of the invoice page.
  • Number of days before warning about inactive leads. Starting at the set number of days without updating a lead, a red background will be shown.
  • Lead status names. You can redefine these texts. Some types are special (marked with *) and others, such as the first, unless they are redefined, they will be used with default values. The rest when left blank are not shown.

Maintaining old data

This is meant to specify to the system how to manage historic information.

  • Days for event deletion. Starting at this number of days of antiquity, events are deleted. This does not delete unclosed tickets. If the value indicated is 0 the data won't be deleted (applicable to all options in this section).
  • Days for ticket deletion: deletes incidents when the time limit expires, plus all related data.
  • Days for WU deletion: deletes working hours when the time limit expires, provided the projects are finished/abandoned.
  • Days for Work Order deletion: deletes WOs, independent of their status. Also deletes attached files.
  • Days for auditing deletion. Similar to events in this aspect.
  • Days for session data deletion. A special chart that keeps track of open sessions.
  • Days to delete work flow events: old work flow events will be deleted.
  • Days for shared file deletion: uploaded files older than the days marked here will be deleted.
  • Days for followup data deletion

Project management

  • Users that don't use the autocomplete system for WUs. Specifying the user ID, separated by commas.
  • Number of hours per day. Used to calculate metrics.
  • WU autocomplete (days). This feature autocompletes Workunits for unassigned days for all users except those listed as “No Workunit completion users”. Autofilled days are counted backward from the current date. If the number of work hours are not manually inputted the system will autocomplete them by default. Hours inputted are not assigned to any project, but instead are classified as “Not justified”. For example, if 15 days are used this means that the system will automatically fill out a WU with the figure for Work hours per day, for all days when inputted hours are lower than THIS number, for the 15 days prior to the present date.
  • Default time for a project's WU. When a WU is created, this is amount of time (in hours) by default.
  • Default currency: Euros, Yens, Dollars, etc.

License

In this section we must introduce our Integria license key. Once introduced, press the Update license button so that Integria can verify if the license is valid.

Click on the lock icon to see the details of your license.

If the maximum number of allowed users is surpassed user's login will 
be automatically deactivated.   

Once the license has been corrected or extended, return to this section 
and click on the button marked "Allow Login". 

System tools

All the tools mentioned here can only be accessed in the same way as the configuration options, by the general system administrator. Some tools, wrongly used, can disable the entire system (SQL manager, file manager).

Update

The online updater (Update Manager) makes it possible to automatically update Integria with the latest patches and versions with just one click.

Offline updater

The offline updater makes it possible to upload update packages to installments that don't have internet access. This tool supports .oum files which are zip files that contain the folders that are meant to be updated on the Integria IMS console. This file has an identical structure to the console files, keeping respect for folder embedment, but only containing the files that need to be updated.

To allow the system to upload large packages it may be necessary to raise the value of the variables upload_max_filesize, memory_limit and post_max_size from the file php.ini on the server, to a size larger than the packages that will be uploaded.

File manager

The file manager is meant for uploading and deleting files on Integria's internal system. This is particularly useful to upload logos or user avatars. It's also the simplest way to upload new files onto the File Distribution System, which is integrated in Integria IMS. Said files can be found under the directory /attachment/downloads.

To upload avatar images, go to /images/avatars directory.

You can change the default icons on the /images directory

Global system news

This will allow you to add small system news that will be visible for all users upon entering. This is useful, for example, to warn about platform changes or interventions, service disconnection or other aspects.

Database Manager (SQL)

This is a direct interface for the system DB in SQL. Not recommended for inexpert users. An incorrect use of this interface can cause the system to crash and data to be lost.

In the Link section you can manage existing links to other websites. You can edit, add and delete existing links (see following section from side menu):

doc59.jpg

System Events

A history log of all events on the system, such as sending scheduled reports, performing CRON checkups, etc. It doesn't store information from user activity which is stored in the auditing log.

Auditing log

In this registry all actions for each user on each section will be stored. If anyone modifies customer data, you'll know when and what has changed. If anyone deletes an invoice, you'll know when and which invoice, and so on. Specific subchains can be searched.

Error log

Shows a view of the error log (if enabled). Useful for identifying possible errors in the system code. In case of a query or ticket, you must provide the latest entries (by date) from this regristry.

Chain translation

Allows you to change any text that appears on the Integria interface for a custom one.

In the interface there is a combination in which to select the language you wish to modify and a free field to search for the text. The search will be done in the reference language which is English. Any translation will be based on this language.

Custom screens

Define a screen with links to internal sections of Integria, or external links with custom texts and icons:

Example of a customized page

The custom screen can be viewed as a new section from the top horizontal menu or as the start screen for Integria.

Customizations will be global throughout the system. It's the screen that will appear upon login, and also the screen that will be seen if we click on the system logo (upper left corner). The editor enables a high degree of personalization, both of the screen setup and widgets.

Tag management

This section allows you to add or edit tags that can be used for filtering elements in lead sections (opportunities). To add a tag, it's necessary to select a name (ficticious) and a color. Click on a previously created tag and editing and deleting options will be enabled.

Backup system in Integria IMS

The backup section is for Integria IMS users to make a security copy of their attached files and database either manually or automatically.

You can find it in Configuration. Open the side menu and you’ll see where to access the section and you’re ready to start using the function.

Backup is itself divided into three tabs, each with a different purpose and each accessible from direct access at the top right corner.

The first one shows a list of the backups you already have in your “backup” folder in the Integria IMS directory. From here you can delete backups, download them or restore your Integria IMS system from a backup from the list (be careful when performing this action as the new backup will replace the backed up information with information from the database, causing any data added between the moment you made the last backup and the system in its current status to be lost).

The second section lets you program scheduled backups got your Integria IMS system. You need to assign a name to the schedule, a backup mode (there are three; database only, attached files only, or both), a scheduled backup time (weekly, by default) and an email address to receive error notifications pertaining to the backup. In the same section there is a scheduling list for you to edit or delete as convenient.

The third and last section covers manual backups, offering the possibility of creating a backup with the name and mode you like (plus, optionally, an email address to receive error notifications) as and when and without the need to wait for a scheduled backup. This kind of backup is created in your “backup” folder in the Integria IMS directory and will afterward be available from the backups list.

You can also upload our own proprietary backups (previously downloaded). These should have the same structure as those generated by the tool in order to maintain uniformity and not have already been in the database.

This is a very sensitive function, and we recommend always having physical backups (as well as in the corresponding folder in the Integria IMS directory) in case of errors when restoring your system to a previous version.

Alert and notification system

This system informs, using a yellow circular icon on the heading, of problems that can appear on Integria. It warns when:

  • There is a large number of emails pending delivery. This parameter is defined in the General Configuration, and by default has a queue of up to 15 messages. When this limit is surpassed, the system shows an alert.
  • The cronjob isn't installed.
  • The cronjob has been running for over ten minutes.


Integria Documentation