Advanced configuration

Go back to Integria IMS Documentation Index

The Integria IMS Configuration menu allows us to access both the Configuration Options and the System Tools.

Configuration options

General configuration

In this section you may customize the main configuration parameters of Integria IMS:

  • Language: Global for the system. It must be taken into account that each user can have a language defined in their data sheet and it prevails over the value defined in this general section.
  • Site name: Visible in the title of all windows. This name will also be in the subject of all messages.
  • Error log: File called integria.log with the errors generated by the application.
  • List of IP addresses with access to the API: separated by commas. An * means “anyone”.
  • Login hash: It is used to generate a unique URL to be used for pre-authentication.
  • API password: Password required to make requests via API.
  • Enable newsletter: The newsletter feature can be fully enabled or disabled from here.
  • First day of the week: For calendars and other uses of the application.
  • URL update manager: Integria IMS update server address.
  • Enable HTTPS access: Configure Integria IMS to use HTTPS and thus encrypt communications.
    • When activating the HTTPS protocol and increasing the security in the transport layers, it will be necessary to add a verification of the OpenSSL certificate. To do this, the following line will have to be added in the php.ini file:
openssl.cafile=/etc/ssl/certs/nombre_certificado.ca-bundle
  • Access port: Configure the server access port number.
  • Public access to the server: URL for public access to the server. It can be an IP address or an URL. If used in a local environment, this parameter will be the same server access IP address. The parameter Public access to the server is used in the generation of newsletters to be able to collect their number of views.
  • Enable the Update Manager check: It enables the notifications of updates available from Integria IMS.
  • Maximum direct download size: It defines the maximum size of a file to download in the application.
  • Max. File size to upload: It defines the maximum size of a file to upload to the application. If you have a lower size in the system (php.ini) this limit may not be respected. If you have problems uploading large files, it may also be due to other more advanced PHP parameters.
  • Max. File size to upload in tickets and CRM: It defines the maximum size of a file to upload to the application in the ticket and CRM sections. If you have a lower size in the system (php.ini) this limit may not be respected. If you have problems uploading large files, it may also be due to other more advanced PHP parameters.
  • CSV encoding type: Default encoding type for .csv files.
  • Data separator in .csv files: By default the comma ,.

visual configuration

In this section some of the options that modify visual aspects are configured:

  • Site logo: Logo displayed on the login screen.
  • Title that appears in the header.
  • Subtitle that appears in the header.
  • Header logo: It will be displayed on the left side of the header.
  • Header logo error: Alternative logo.
  • Main color.
  • General source: Both for interface and for PDF files.
  • Login background: Login screen background.
  • Global search limit: It is the number of elements that will appear in the lists when using any search.
  • Block size for paging: Number of elements in lists. It is recommended not to use high values as it affects performance.

Password settings

In this section you may configure the password policy of the system. Bear in mind that the password policy does not apply to administrator users.

We have the following options:

  • Activate password policy. If it is disabled, the rest of the parameters do not apply.
  • Minimum length that the password must have.
  • The password must contain numbers.
  • The password must contain symbols.
  • Password expiration time in days.
  • Force password change on first login.
  • User blocking time, in minutes, when the login fails after the retries configured in the following field.
  • Number of failed identification attempts.

As of OUM 95 there is an option to show the user's last login. By default it is disabled.

Ticket settings

Visual options

  • Show the creator of the ticket and show the owner of the ticket in ticket search list/view. In the ticket search view/list.
  • Max. tickets per search: Limit search results in tickets, to avoid impacts on performance by excessively large searches. A limit between 200 and 500 is recommended.
  • Enable quick edit mode: It allows you to quickly edit some elements of the ticket (user owner, criticality, status) without entering full edit mode.
  • Show username instead of identifier when searching for tickets: real name instead of ID.
  • Date format: Two format options, long format yyyy/mm/dd h:m:s (default option) and approximate format. Example: 1 day, 2 hours
  • Realization date: Checking this option will display the Date of realization field in the ticket workunits. This date can be different from the creation date of the Workunit.
  • Sort WU by completion date (in the WU list of a ticket).

  • Disable incident assessment.
  • Enable IW to change creator: Users with that access bit will be able to change the creator of the ticket .
  • Editor adds WU in ticket creation: A WU is added automatically when creating a ticket.
  • Change ticket type. If disabled, the type cannot be changed after it is created.
  • Allow to define the time/date of the ticket when creating it.
  • Ignore user defined by the group for the owner.
  • Type of issue required: It forces you to choose a ticket type.
  • Ignore the default creator user: It 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 from incident creator.
  • The creator user can see all users. With this you will be able to see users from other groups.
  • Auto assign ticket, based on group assignment rules.
  • Ticket editor is the first user to edit: If checked, the ticket editor user will always be set as the user who edited the ticket in the first place.

  • Ticket auto closing: Number of hours after which a ticket will be closed automatically.
  • Ticket by default WU time: Default value used when entering a work unit, in units of hours. Example: 0.25 will be 15 minutes.

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

Email sending options

  • Sending email with each ticket update.
  • Sending all the attachments associated with the ticket in each update notified by email.
  • Mask email addresses. With this option activated, the email addresses that are in the content of the ticket will not be displayed.

This configuration can be general or group-specific. To be specific by group, it is necessary to configure it in the group's own edition:

  • Send email for each ticket creation.
  • Send email for each ticket closure.
  • Send email for each update of the ticket status.
  • Send email for each update of the ticket owner.
  • Send email for each update of the ticket status.
  • Send email for each update of the ticket status.
  • Send email for each update of the ticket status.
  • Send email for each Workunit.
  • Send email for each attachment.
  • Send email for each work report validation.

Status labels and ticket resolutions can be modified. It is important to bear in mind that even if the label changes, the logic associated with the states remains the same, so the SLA rules, Workflow, or ticket colors according to their state (new/closed) will remain the same.

Non-working days are used to define local/national holidays, etc. They are not taken into account in SLAs (except those that also include holidays), and are displayed differently in calendars.

Email settings

Section for configurating sending automatic emails by Integria IMS. The SMTP protocol is used for sending emails, for example when there is a ticket change or an SLA is breached, and the POP/IMAP protocol is used to manage incoming tickets. This last option is only necessary if you want to enable ticket creation and management by email.

In this section you may also change email global parameters such as header, footer, delivery address, notification period, etc.

  • Notification period: Minimum time in hours that must go by between two SLA notifications.
  • Mailing address from the system: Sender to be used when sending emails from Integria IMS.

SMTP configuration

Credentials and data are defined to connect to your SMTP server. If left blank, it will try to use a local postfix / sendmail mail system, if enabled.

  • Mail queue forwarding retries: Exceeded this number, it will mark the email in the queue as incorrect.
  • Maximum number of pending emails: Exceeded this number, it will display a warning in the system notifications area to indicate that there may be a problem with the mailing.
  • Maximum number of emails sent per execution: The maximum number of emails is delimited in each periodic execution of the maintenance script.

Gmail (SMTP)

  • No encryption: Gmail does not allow sending emails without encryption so at least configure the encryption as STARTTLS, which can be used on ports 25 or 587.
  • Encrypted:

STARTTLS:

As we see in the previous image we configure:

  • Encryption method:STARTTLS.
  • SMTP Host: smtp.gmail.com
  • Port: 587 (25 could also be used).

SSL and different versions

As we see in the previous image, configure:

  • Encryption method:SSL/TLS.
  • SMPT Host: smtp.gmail.com.
  • Port: 465.

Outlook (SMTP)

  • No encryption:

Outlook does not allow sending emails without encryption ,so at least configure the encryption as STARTTLS, which can be used on ports 25 or 587.

  • Encrypted:

STARTTLS:

As we see in the previous image, configure:

  • Encryption method:STARTTLS.
  • SMTP Host: smtp-mail.outlook.com .
  • Port: 587 (25 could also be used).
  • Compatibility: Outlook.

SSL and different versions It does not allow this type of encryption, only STARTTLS.


Outlook does not allow the use of users from other mail services, only its own, so it is necessary to specify the same mail that is used for the SMTP configuration.

Office 365 (SMTP)

  • No encryption:

Office 365 does not allow sending emails without encryption, so at least configure the encryption as STARTTLS, which can be used on ports 25 or 587.

  • Encrypted:

STARTTLS:

As you see in the previous image, you have:

  • Encryption method:STARTTLS.
  • SMTP Host: smtp.office365.com .
  • Port: 587 (25 could also be used).
  • Compatibility: Office 365.

SSL and different versions It does not allow this type of encryption, only STARTTLS.


Office 365 does not allow the use of users from other mail services, only its own, so it is necessary to specify the same mail that is used for the SMTP configuration.

Others (SMTP)

  • Encryption: You may 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 listens.
  • User: User configured on the mail server.
  • Password: Password configured for the user indicated above.

IMAP/POP settings


It is recommended, as far as possible, not to use the IMAP/POP account of any internal Integria IMS user, as this may cause some unusual performances when creating and updating tickets in Integria IMS.

Gmail (IMAP/POP)

  • It only allows this configuration: (SSL/TLS):
    • IMAP:

  • POP:

  • Name: imap.gmail.com / pop.gmail.com .
  • Port: 993 (IMAP) or 995 (POP)
  • Protocol selection: POP or IMAP.
  • Compatibility: Gmail.


The option to accept all certificates is not recommended to be used as it will not validate the certificates for encryption.

  • Once configured, choose an Integria IMS group in which you want for the tickets of the emails of this account to be created and edit the group:
  • PeopleAccess controlGroup managementEdit the group you wish:

  • So that a user external to Integria IMS can create a ticket through an email:
    • User auto-creation: It allows creating a new user in Integria IMS. Which will match the name of the email. This option must be enabled.
    • User access permissions to create tickets: It allows giving the created user the necessary permissions to edit tickets. This option must be enabled.
    • Welcome message: It allows you to send a welcome message to the created user. It is optional.
    • Ticket status: It allows you to choose the status of the created ticket. The default status is New.
    • Type of user: It allows you to choose the type of user created. The default user type is Grouped User.
    • Company: It allows you to select which company the created ticket belongs to. It is optional.
    • Determined profile: It allows you to select the profile of the created user. The default option is Support operator.
    • Ticket type: It allows you to select the type of ticket the created ticket belongs to. It is optional.
    • Email queue: Very important, it must match the name of the POP/IMAP settings.
    • Gmail own configuration: The protocol to be used (POP/IMAP) must be enabled within the email account and, in the case of using POP, allow it to delete emails so that the tool can work correctly.

Outlook (IMAP/POP):

It only allows this configuration: (SSL/TLS):

IMAP:

POP:

  • Name: imap-mail.outlook.com / pop-mail.outlook.com .
  • Port: 993 (IMAP)/995 (POP) .
  • Protocol Selection: POP/IMAP .
  • Compatibility: Outlook.


The option to accept all certificates is not recommended to be used as it will not validate the certificates for encryption.


Within the Outlook settings it is necessary to have the option Allow devices and applications to use the POP settings enabled.

  • Once configured, choose an Integria IMS group in which you want for the tickets of the emails of this account to be created and edit the group:
  • PeopleAccess controlGroup managementEdit the group you wish:

  • So that a user external to Integria IMS can create a ticket through an email:
    • User auto-creation: It allows creating a new user in Integria IMS. Which will match the name of the email. This option must be enabled.
    • User access permissions to create tickets: It allows giving the created user the necessary permissions to edit tickets. This option must be enabled.
    • Welcome message: It allows you to send a welcome message to the created user. It is optional.
    • Ticket status: It allows to choose the status of the created ticket. The default status is New.
    • Type of user: It allows you to choose the type of user created. The default user type is Grouped User.
    • Company: It allows you to select which company the created ticket belongs to. It is optional.
    • Determined profile: It allows you to select the profile of the created user. The default option is Support operator.
    • Ticket type: It allows to select the type of ticket the created ticket belongs to. It is optional.
    • Email queue: Very important, it must match the name of the POP/IMAP settings.
  • Outlook own configuration: The protocol to be used (POP/IMAP) must be enabled within the email account and, in the case of using POP, allow it to delete emails so that the tool can work correctly.

Office 365 (IMAP/POP)

It only allows this configuration: (SSL/TLS).

IMAP:

POP:

  • Name: outlook.office365.com valid both for POP/IMAP.
  • Port: 993 (IMAP)/995 (POP).
  • Protocol selection: POP or IMAP.
  • Compatibility: Office 365.


The option to accept all certificates is not recommended to be used as it will not validate the certificates for encryption.

  • Once configured, choose an Integria IMS group in which you want the tickets of the emails of this account to be created and edit the group:
  • PeopleAccess controlGroup managementEdit the group you wish:

  • So that a user external to Integria IMS can create a ticket through an email:
    • User auto-creation: It allows creating a new user in Integria IMS. Which will match the name of the email. This option must be enabled.
    • User access permissions to create tickets: It allows giving the created user the necessary permissions to edit tickets. This option must be enabled.
    • Welcome message: It allows you to send a welcome message to the created user.It is optional.
    • Ticket status: It allows you to choose the status of the created ticket. The default status is New.
    • Type of user: It allows you to choose the type of user created. The default user type is Grouped User.
    • Company: It allows you to select which company the created ticket belongs to. It is optional.
    • Determined profile: It allows you to select the profile of the created user. The default option is Support operator.
    • Ticket type: It allows you to select the type of ticket the created ticket belongs to. It is optional.
    • Email queue: Very important, it must match the name of the POP/IMAP settings.
  • Office 365 own configuration: The protocol to be used (POP/IMAP) must be enabled within the email account and, in the case of using POP, allow it to delete emails so that the tool can work correctly.

Others (IMAP/POP)

  • Encryption: You may configure the POP/IMAP server without encryption or with SSL/TLS, SSLv2, SSLv3 or STARTTLS.
  • Name: IP address or DNS of the POP/IMAP server.
  • Port: Number of the port where the POP/IMAP server is listening.
  • User: User configured on the mail server.
  • Password: Password configured for the user indicated above.
  • Protocol: POP or IMAP.
  • Compatibility: others.
  • Accept all certificates: Checked if you wish to accept any certificate, even self-signed ones.

Email forwarding queue settings

The emails sent by Integria IMS are queued until the maintenance script sends them by default every 5 minutes. To adjust this performance there are a series of special parameters as well as a pending-to-be-sent queue manager.

  • Email header: It will be used in any automatic Integria IMS email. It does not admit macros.
  • Email footer: It will be used in any automatic Integria IMS email. It does not admit macros.

Email forwarding queue management

This system allows to see the emails yet to be sent and their status. In addition you may delete and/or resend those emails marked as non-valid, and emails may be selected for said operation individually by checking the associated checkbox.

Email templates

This section is used to edit the email templates that Integria IMS will use to generate emails, as well as the message subject templates. Mail templates are generic and used for all groups.

To edit a template, choose one and click edit. You may see that there are some special _sitename_ marks we call macros. Macros are variables that will be replaced at the time of composing the message with a specific real value. At this moment the following macros are defined:

  • _sitename_ : Name of the site, as defined in the Setup.
  • _incident_title_ : Ticket title.
  • _username_ : Name of the user who receives the mail (login name).
  • _fullname_ : Full name of the user who receives the mail.
  • _incident_id : Ticket identifier.
  • _url_ : Ticket URL.
  • _creation_timestamp_ : Ticket creation date and time.
  • _update_timestamp_ : Last time the ticket was updated.
  • _owner_ : User who controls the ticket.
  • _group_ : Group assigned to the ticket.
  • _author_ : Ticket creator.
  • _priority_ : Ticket priority.
  • _status_ : Ticket status.
  • _resolution_ : Ticket resolution.
  • _time_used_ : Total time spent on this ticket.
  • _incident_main_text_ : Main descriptive text of the ticket.
  • _wu_user_ : User reporting a work unit.
  • _wu_text_ : Workunit text.
  • _havecost_ : For project work unit reports only.
  • _taskname_ : For project work unit reports only.
  • _projectname_ : For project work unit reports only.
  • Custom fields: This allows that when creating an item type, the name of the fields that are added can be included as a macro which will show the value of said field: _custom field name_.

Visibility Menu

This option is used to “hide” certain parts of Integria IMS from user groups. The following visibility levels can be configured for each section and user group:

  • Hidden: It will not be shown for those users who belong to the indicated group.
  • Full: Users who belong to the indicated group will have full access to the section.

Additional Information:

If a section does not have any visibility settings, by default the access will be Full for all users.

Each section is associated with a profile, this being the one that is checked together with the user's group to find out if it is visible or not, the associations are as follows:

  • Projects ⇒ 'PR'.
  • Tickets ⇒ 'IR'.
  • Inventories ⇒ 'VR'.
  • BC ⇒ 'KR'.
  • File releases ⇒ 'KR'.
  • Planner ⇒ 'AR'.
  • People ⇒ Any profile.
  • Work Orders ⇒ 'WOR'.
  • Configuration ⇒ Any profile.

If the user is an administrator, they will always have full access regardless of the menu visibility settings.

If a user has profiles in multiple groups that have different levels of visibility in a section, the 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 (All group), all settings for that section will be removed, leaving only the one entered.

Pandora FMS Inventory

This section controls both the inventory options and the remote inventory management (data processing sent by Pandora FMS agents to Integria IMS, without the need to install Pandora FMS).

Inventory options

  • Duplicate inventory names: It allows the option of having inventory item names with the same name. Option disabled by default.
  • CSV import support: If the option is deactivated, it allows the CSVs to be displayed as a report showing the inventory objects previously selected by the user as they appear in the list. By default it will be active to allow import.

Inventory data processing from Pandora FMS agents

  • Default owner: Default owner for those items.
  • Associated user and company. Companies with access to those items, and users with access to those items.

Authentication

Authentication type: LDAP, Active Directory, or local. If LDAP or AD is used.

Admin users will be the only ones that work “locally” without authenticating against an LDAP, so that if there is any problem when connecting with LDAP for user validation, administrators will always be able to access the tool.

If the LDAP or Active Directory login is configured, Integria IMS will “ask” these platforms if the user exists and the password is correct, making a login attempt through an LDAP query. If successful, it will allow the user access to Integria IMS.

configuration parameters:

  • Session timeout: In seconds.
  • Automatically create remote users: So that new users can access the tool from the first attempt if they have an LDAP/AD user. If it is not enabled, the user must already exist in Integria IMS, and the password must match the LDAP password.
  • Auto-create profile: Profile to assign to automatically created users.
  • Auto-create group: Group assigned to the automatically created user, with the profile used in the previous field.
  • Automatically create a blacklist: List of users, separated by commas, that will not be able to access.
  • LDAP/AD server: IP address or FQDN of the LDAP/AD server.
  • LDAP/AD Port.
  • LDAP version (LDAP only).
  • Start TLS: It will use the Transport Layer Security (TLS) protocol in communications between the client and the server to encrypt communications.
  • DN Base (LDAP only): Distinguished Name (DN) used by the LDAP server. For example: ou=People,dc=example,dc=com.
  • Login attribute (LDAP only): Login attribute that LDAP uses during the authentication process. For example UID (User Identification Code).
  • Domain (AD only).

Configuration Example for LDAP

Configuration Example for Active Directory

CRM

In the configuration section, you will find a tab for CRM management:

You may activate or deactivate invoice ID automatic generation and modify its infrastructure:

In field Invoice ID pattern a text string that will bes used as pattern to generate identifiers will be saved. This pattern will contain a fixed part and a variable. The variable part must be numerical and work as the first element from which to calculate a sequence. The variable part will go between square brackets. The rest will be constant on all invoices.

Pattern example: 15/[1000]

In this case, the first three invoices to be generated will be 15/1000, 15/1001 and 15/1002.

Invoice ID generation applies only to Sent invoices.

You may also modify your invoice data, including the logo (to upload images, you may do so using the integrated file manager, under SettingsFile Manager), in the Custom logos folder.

In the configuration section of the CRM you may also rename the states of the leads to customize your pipeline.

Maintaining old data

It allows the system to specify how to manage history information.

  • Days to delete events: Old events will be deleted from the indicated days. If the specified value is zero 0, the data will never be erased (this applies to all other options in this section).
  • Days to delete closed tickets: Tickets with a closing date older than the days indicated will be deleted. Related data will also be erased.
  • Days to delete Work Units: Work hours older than the days indicated will be deleted, as long as they belong to disabled projects.
  • Days to delete Work orders: Work orders with an update date older than the days indicated will be deleted.
  • Days to clear audit information: Audit data older than the specified days will be erased.
  • Days to delete sessions: Sessions older than the days indicated will be deleted.
  • Days to delete Workflow events: Old workflow events will be deleted from the indicated days.
  • Days to delete old shared files: Uploaded files that are older than the specified days will be deleted.
  • Days to delete file tracking data: Audit data older than the specified days will be erased.
  • Days to delete backups.
  • Days to delete invalid emails that could not be sent.
  • Days to delete scheduled reports.

The Restore to default values option will return the initial values of all the configuration parameters in this section.


The Delete all data option will delete ALL the data from the database and also the attached files.

Project management

  • Users without UT completion: List of users who do not have working hours autocomplete, separated by commas.
  • Working hours per day: To calculate metrics.
  • UT autocomplete (days): This feature will autocomplete UTs on unassigned days for all users except those listed in Users without UT completion. Days that will autocomplete backward from the current moment. If not specified manually, the working hours will be auto-completed by default. The hours entered are not assigned to any task in any project, but to the “Unexcused” hours. For example, if you set 15 days, they will be completed with the number of Hours of work per day, for all days in which the hours entered are lower than that number, for the previous 15 days from the current date.
  • Default time for a project WU: When creating a WU, it will use that amount of time by default (in hours).
  • Default currency.
  • Total vacation days: Number of vacation days that will be used for the corresponding calculations in the vacation report section.

License

Enter in this section Integria IMS license. Once entered, click Update license for Integria IMS to verify whether it is valid.

If you click on the padlock you may see the details of your license.

If the maximum number of allowed users of the license is exceeded, the users' login will be automatically disabled.

Once the license has been corrected or extended, just return to this section and click Allow session start (login).

eHorus

Chatbot

To activate ChatBot and configure the server and channels.

GitLab

For integration with GitLab you need an access token that belongs to a GitLab user with permissions to see the tickets of the project that interest you.

Creation of personal access token in GitLab:

  1. Login in GitLab.
  2. In the upper right corner, select the avatar icon.
  3. Edit profile.
  4. Access tokens.
  5. Enter name and optional expiration date for the token.
  6. Select the desired scopes.
  7. Keep the personal access token in a safe place. After leaving the page, you will no longer have access to the token.


You also need the project's URL. Example:

https://example.es:8080/api/v4/projects/1/

And the base URL of the images to be able to load the images that contain the tickets in their description and in their comments. Example:

https://example.es:8080/artica/integria/

System tools

The tools mentioned here can only be accessed by system administrator users due to their power. Some tools, if misused, can render the system inoperative (e.g. SQL manager, file manager).

Update

The online Update Manager allows you to automatically update Integria IMS with the latest product patches and versions with a single click.

Update offline

The offline updater allows you to upload update packages to installations that do not have Internet access. This tool supports .oum files, packages that contain the files that will be updated in Integria IMS console, they only contain the files that have been modified.

To allow uploading of large packages, it may be necessary to increase the value of the upload_max_filesize, memory_limit and post_max_size of php.ini file to a value higher than the size of the packages to be uploaded.

File manager

The file manager is used to upload and delete files to Integria IMS internal system. This is useful for conveniently uploading new logos or user avatars. It is also the easiest way to upload new files to Integria IMS integrated file distribution system. These files are located in the /attachment/downloads directory.

To upload avatar images, you may do so in the /images/avatars directory.

You may change the default icons in the /images directory.

Global news

It allows adding small system news, which will be visible to all users when they log in. Useful for example to notify of changes in the platform or notices about interventions, service disconnection or others.

Database manager

It is a direct interface against the system database, in SQL.


For the exclusive use of expert users as its misuse can cause irreversible damage to the tool and the deletion of data.

Links can be added and removed and displayed in the Links section of the main menu.

System events

History of events that took place in the system, such as sending scheduled reports, executing cron tasks, system failures, etc.


It does not save user activity information, as it is stored in the audit log.

Audit log

All the actions of each user in each section will be reflected in this record. If someone modifies a customer's data, it will be known when and what was changed. If someone deletes an invoice, it will be known when and what invoice, and so on. Allows you to search by a specific substring.

Error log

It displays the error log (if it is enabled), useful for identifying possible system code errors. In case of query or ticket, provide the last entries (by date) of this log.

Custom string translation

It allows replacing any text that appears in Integria IMS interface by a customized one.

In the interface there is a combo where you may select the language you want to modify and a free field to search for the text. The search is carried out on the original language which is English, all translations are based on this language.

Custom screens

Defining a home screen with links to specific sections of Integria IMS or external pages:

It can be visible either as a new section of the upper horizontal menu or as an Integria IMS home screen.

It is global for the system, appearing as main one when logging in or clicking on the upper left logo of the tool. The editor allows us a high customization level of the screen and the widgets to be displayed.

Backups

The backup section allows Integria IMS users to make manual or scheduled backups of their attachments and their database.

The first one consists of a list of existing backups in your backup folder within Integria IMS directory. From here you may delete a backup, download it to your machine or restore your Integria IMS system from a backup from the list (you must be especially careful when performing this action as the backup will replace the database information with the one you had in that backup, making the information added between the backup and the system in its current state disappear). The second section allows you to schedules things so that, after a specific time, your Integria IMS system is backed up. To create a backup schedule, you must include a name for the schedule, a backup mode (there are three modes, only database, only attachments or both), a backup periodicity (weekly by default) and a backup address. Email to which you will receive notifications if something goes wrong in this backup. Also in the same section you will have available the list of schedules for editing or deleting, as appropriate.

The third and last section is responsible for making manual backups at the moment, giving the possibility of creating a backup with the name and the desired mode (and optionally an email address for error notifications) right away without having to wait for to a scheduled one. This backup will be created in your backup folder within Integria IMS directory and will be available in the backup list.

It also has the possibility of uploading your own previously downloaded backups, these must have the same structure that the tool generates to keep consistency and not be previously in the database.

This is a highly sensitive feature, we always recommend having the backups physically (in addition to having them in their corresponding folder within Integria IMS directory) to have a backup if something goes wrong when restoring the system to a previous version.

Go back to Integria IMS Documentation Index

Password settings

In this section you may configure the password policy of the system. Bear in mind that the password policy does not apply to administrator users.

There are the following options:

  • Activate password policy. If it is disabled, the rest of the parameters do not apply.
  • Minimum length that the password must have.
  • The password must contain numbers.
  • The password must contain symbols.
  • Password expiration time in days.
  • Force password change on first login.
  • User blocking time, in minutes, when the login fails after the retries configured in the following field.
  • Number of failed identification attempts.

Ticket settings

Visual options

  • Show the creator of the ticket and show the owner of the ticket in ticket search list/view. In the ticket search view/list.
  • Max. tickets per search: Limit search results in tickets, to avoid impacts on performance by excessively large searches. A limit between 200 and 500 is recommended.
  • Enable quick edit mode: It allows you to quickly edit some elements of the ticket (user owner, criticality, status) without entering full edit mode.
  • Show username instead of identifier when searching for tickets: real name instead of ID.
  • Date format: Two format options, long format yyyy/mm/dd h:m:s (default option) and approximate format. Example: 1 day, 2 hours
  • Realization date: Checking this option will display the Date of realization field in the ticket Work Units. This date can be different from the creation date of the Work Unit.
  • Sort WU by completion date (in the WU list of a ticket).

  • Disable incident assessment.
  • Enable IW to change creator: Users with that access bit will be able to change the creator of the ticket.
  • Editor adds WU in ticket creation: A WU is added automatically when creating a ticket.
  • Change ticket type. If disabled, the type cannot be changed after it is created.
  • Allow to define the time/date of the ticket when creating it.
  • Ignore user defined by the group for the owner.
  • Type of issue required: It forces you to choose a ticket type.
  • Ignore the default creator user: It 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 from incident creator.
  • The creator user can see all users. With this you will be able to see users from other groups.
  • Auto assign ticket, based on group assignment rules.
  • Ticket editor is the first user to edit: If checked, the ticket editor user will always be set as the user who edited the ticket in the first place.

  • Ticket auto closing: Number of hours after which a ticket will be closed automatically.
  • Ticket by default WU time: Default value used when entering a work unit, in units of hours. Example: 0.25 will be 15 minutes.

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

Email sending options

  • Sending email with each ticket update.
  • Sending all the attachments associated with the ticket in each update notified by email.
  • Mask email addresses. With this option activated, the email addresses that are in the content of the ticket will not be displayed.

This configuration can be general or group-specific. To be specific by group, it is necessary to configure it in the group's own edition:

  • Send email for each ticket creation.
  • Send email for each ticket closure.
  • Send email for each update of the ticket status.
  • Send email for each update of the ticket owner.
  • Send email for each update of the ticket status.
  • Send email for each update of the ticket status.
  • Send email for each update of the ticket status.
  • Send email for each Work Unit.
  • Send email for each attachment.
  • Send email for each work report validation.

Status labels and ticket resolutions can be modified. It is important to bear in mind that even if the label changes, the logic associated with the states remains the same, so the SLA rules, Workflow, or ticket colors according to their state (new/closed) will remain the same.

Non-working days are used to define local/national holidays, etc. They are not taken into account in SLAs (except those that also include holidays), and are displayed differently in calendars.

Email settings

Section for configurating sending automatic emails by Integria IMS. The SMTP protocol is used for sending emails, for example when there is a ticket change or an SLA is breached, and the POP/IMAP protocol is used to manage incoming tickets. This last option is only necessary if you want to enable ticket creation and management by email.

In this section you may also change email global parameters such as header, footer, delivery address, notification period, etc.

  • Notification period: Minimum time in hours that must go by between two SLA notifications.
  • Mailing address from the system: Sender to be used when sending emails from Integria IMS.

SMTP configuration

Credentials and data are defined to connect to your SMTP server. If left blank, it will try to use a local postfix / sendmail mail system, if enabled.

  • Mail queue forwarding retries: Exceeded this number, it will mark the email in the queue as incorrect.
  • Maximum number of pending emails: Exceeded this number, it will display a warning in the system notifications area to indicate that there may be a problem with the mailing.
  • Maximum number of emails sent per execution: The maximum number of emails is delimited in each periodic execution of the maintenance script.

Gmail (SMTP)

  • No encryption: Gmail does not allow sending emails without encryption so at least configure the encryption as STARTTLS, which can be used on ports 25 or 587.
  • Encrypted:

STARTTLS:

As we see in the previous image we configure:

  • Encryption method: STARTTLS.
  • SMTP Host: smtp.gmail.com
  • Port: 587 (25 could also be used).

SSL and different versions

As we see in the previous image, configure:

  • Encryption method:SSL/TLS.
  • SMPT Host: smtp.gmail.com.
  • Port: 465.

Outlook (SMTP)

  • No encryption:

Outlook does not allow sending emails without encryption ,so at least configure the encryption as STARTTLS, which can be used on ports 25 or 587.

  • Encrypted:

STARTTLS:

As we see in the previous image, configure:

  • Encryption method:STARTTLS.
  • SMTP Host: smtp-mail.outlook.com .
  • Port: 587 (25 could also be used).
  • Compatibility: Outlook.

SSL and different versions It does not allow this type of encryption, only STARTTLS.


Outlook does not allow the use of users from other mail services, only its own, so it is necessary to specify the same mail that is used for the SMTP configuration.

Office 365 (SMTP)

  • No encryption:

Office 365 does not allow sending emails without encryption, so at least configure the encryption as STARTTLS, which can be used on ports 25 or 587.

  • Encrypted:

STARTTLS:

As you see in the previous image, you have:

  • Encryption method:STARTTLS.
  • SMTP Host: smtp.office365.com .
  • Port: 587 (25 could also be used).
  • Compatibility: Office 365.

SSL and different versions: It does not allow this type of encryption, only STARTTLS.


Office 365 does not allow the use of users from other mail services, only its own, so it is necessary to specify the same mail that is used for the SMTP configuration.

Others (SMTP)

  • Encryption: You may 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 listens.
  • User: User configured on the mail server.
  • Password: Password configured for the user indicated above.

IMAP/POP settings


It is recommended, as far as possible, not to use the IMAP/POP account of any internal Integria IMS user, as this may cause some unusual performances when creating and updating tickets in Integria IMS.

Gmail (IMAP/POP)

  • It only allows this configuration: (SSL/TLS):
    • IMAP:

  • POP:

  • Name: imap.gmail.com / pop.gmail.com .
  • Port: 993 (IMAP) or 995 (POP)
  • Protocol selection : POP or IMAP .
  • Compatibility: Gmail.


The option to accept all certificates is not recommended to be used as it will not validate the certificates for encryption.

  • Once configured, choose an Integria IMS group in which you want for the tickets of the emails of this account to be created and edit the group:
  • PeopleAccess controlGroup managementEdit the group you wish:

  • So that a user external to Integria IMS can create a ticket through an email:
    • User auto-creation: It allows creating a new user in Integria IMS. Which will match the name of the email. This option must be enabled.
    • User access permissions to create tickets: It allows giving the created user the necessary permissions to edit tickets. This option must be enabled.
    • Welcome message: It allows you to send a welcome message to the created user. It is optional.
    • Ticket status: It allows you to choose the status of the created ticket. The default status is New.
    • Type of user: It allows you to choose the type of user created. The default user type is Grouped User.
    • Company: It allows you to select which company the created ticket belongs to. It is optional.
    • Determined profile: It allows you to select the profile of the created user. The default option is Support operator.
    • Ticket type: It allows you to select the type of ticket the created ticket belongs to. It is optional.
    • Email queue: Very important, it must match the name of the POP/IMAP settings.
    • Gmail own configuration: The protocol to be used (POP/IMAP) must be enabled within the email account and, in the case of using POP, allow it to delete emails so that the tool can work correctly.

Outlook (IMAP/POP):

It only allows this configuration: (SSL/TLS):

IMAP:

POP:

  • Name: imap-mail.outlook.com / pop-mail.outlook.com .
  • Port: 993 (IMAP)/995 (POP) .
  • Protocol Selection: POP/IMAP .
  • Compatibility: Outlook.


The option to accept all certificates is not recommended to be used as it will not validate the certificates for encryption.


Within the Outlook settings it is necessary to have the option Allow devices and applications to use the POP settings enabled.

  • Once configured, choose an Integria IMS group in which you want for the tickets of the emails of this account to be created and edit the group:
  • PeopleAccess controlGroup managementEdit the group you wish:

  • So that a user external to Integria IMS can create a ticket through an email:
    • User auto-creation: It allows creating a new user in Integria IMS. Which will match the name of the email. This option must be enabled.
    • User access permissions to create tickets: It allows giving the created user the necessary permissions to edit tickets. This option must be enabled.
    • Welcome message: It allows you to send a welcome message to the created user. It is optional.
    • Ticket status: It allows to choose the status of the created ticket. The default status is New.
    • Type of user: It allows you to choose the type of user created. The default user type is Grouped User.
    • Company: It allows you to select which company the created ticket belongs to. It is optional.
    • Determined profile: It allows you to select the profile of the created user. The default option is Support operator.
    • Ticket type: It allows to select the type of ticket the created ticket belongs to. It is optional.
    • Email queue: Very important, it must match the name of the POP/IMAP settings.
  • Outlook own configuration: The protocol to be used (POP/IMAP) must be enabled within the email account and, in the case of using POP, allow it to delete emails so that the tool can work correctly.

Office 365 (IMAP/POP)

It only allows this configuration: (SSL/TLS).

IMAP:

POP:

  • Name: outlook.office365.com valid both for POP/IMAP.
  • Port: 993 (IMAP)/995 (POP).
  • Protocol selection: POP or IMAP.
  • Compatibility: Office 365.


The option to accept all certificates is not recommended to be used as it will not validate the certificates for encryption.

  • Once configured, choose an Integria IMS group in which you want the tickets of the emails of this account to be created and edit the group:
  • PeopleAccess controlGroup managementEdit the group you wish:

  • So that a user external to Integria IMS can create a ticket through an email:
    • User auto-creation: It allows creating a new user in Integria IMS. Which will match the name of the email. This option must be enabled.
    • User access permissions to create tickets: It allows giving the created user the necessary permissions to edit tickets. This option must be enabled.
    • Welcome message: It allows you to send a welcome message to the created user.It is optional.
    • Ticket status: It allows you to choose the status of the created ticket. The default status is New.
    • Type of user: It allows you to choose the type of user created. The default user type is Grouped User.
    • Company: It allows you to select which company the created ticket belongs to. It is optional.
    • Determined profile: It allows you to select the profile of the created user. The default option is Support operator.
    • Ticket type: It allows you to select the type of ticket the created ticket belongs to. It is optional.
    • Email queue: Very important, it must match the name of the POP/IMAP settings.
  • Office 365 own configuration: The protocol to be used (POP/IMAP) must be enabled within the email account and, in the case of using POP, allow it to delete emails so that the tool can work correctly.

Others (IMAP/POP)

  • Encryption: You may configure the POP/IMAP server without encryption or with SSL/TLS, SSLv2, SSLv3 or STARTTLS.
  • Name: IP address or DNS of the POP/IMAP server.
  • Port: Number of the port where the POP/IMAP server is listening.
  • User: User configured on the mail server.
  • Password: Password configured for the user indicated above.
  • Protocol: POP or IMAP.
  • Compatibility: others.
  • Accept all certificates: Checked if you wish to accept any certificate, even self-signed ones.

Email forwarding queue settings

The emails sent by Integria IMS are queued until the maintenance script sends them by default every 5 minutes. To adjust this performance there are a series of special parameters as well as a pending-to-be-sent queue manager.

  • Email header: It will be used in any automatic Integria IMS email. It does not admit macros.
  • Email footer: It will be used in any automatic Integria IMS email. It does not admit macros.

Email forwarding queue management

This system allows to see the emails yet to be sent and their status. In addition you may delete and/or resend those emails marked as non-valid, and emails may be selected for said operation individually by checking the associated checkbox.

Email templates

This section is used to edit the email templates that Integria IMS will use to generate emails, as well as the message subject templates. Mail templates are generic and used for all groups.

To edit a template, choose one and click edit. You may see that there are some special _sitename_ marks we call macros. Macros are variables that will be replaced at the time of composing the message with a specific real value. At this moment the following macros are defined:

  • _sitename_: Name of the site, as defined in the Setup.
  • _incident_title_: Ticket title.
  • _username_ : Name of the user who receives the mail (login name).
  • _fullname_ : Full name of the user who receives the mail.
  • _incident_id : Ticket identifier.
  • _url_ : Ticket URL.
  • _creation_timestamp_ : Ticket creation date and time.
  • _update_timestamp_ : Last time the ticket was updated.
  • _owner_: User who controls the ticket.
  • _group_: Group assigned to the ticket.
  • _author_: Ticket creator.
  • _priority_: Ticket priority.
  • _status_: Ticket status.
  • _resolution_: Ticket resolution.
  • _time_used_ : Total time spent on this ticket.
  • _incident_main_text_ : Main descriptive text of the ticket.
  • _wu_user_ : User reporting a work unit.
  • _wu_text_ : Workunit text.
  • _havecost_ : For project work unit reports only.
  • _taskname_ : For project work unit reports only.
  • _projectname_ : For project work unit reports only.
  • Custom fields: This allows that when creating an item type, the name of the fields that are added can be included as a macro which will show the value of said field: _custom field name_.

Visibility Menu

This option is used to “hide” certain parts of Integria IMS from user groups. The following visibility levels can be configured for each section and user group:

  • Hidden: It will not be shown for those users who belong to the indicated group.
  • Full: Users who belong to the indicated group will have full access to the section.

Additional Information:

If a section does not have any visibility settings, by default the access will be Full for all users.

Each section is associated with a profile, this being the one that is checked together with the user's group to find out if it is visible or not, the associations are as follows:

  • Projects ⇒ 'PR'.
  • Tickets ⇒ 'IR'.
  • Inventories ⇒ 'VR'.
  • BC ⇒ 'KR'.
  • File releases ⇒ 'KR'.
  • Planner ⇒ 'AR'.
  • People ⇒ Any profile.
  • Work Orders ⇒ 'WOR'.
  • Configuration ⇒ Any profile.

If the user is an administrator, they will always have full access regardless of the menu visibility settings.

If a user has profiles in multiple groups that have different levels of visibility in a section, the 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 (All group), all settings for that section will be removed, leaving only the one entered.

Pandora FMS Inventory

This section controls both the inventory options and the remote inventory management (data processing sent by Pandora FMS agents to Integria IMS, without the need to install Pandora FMS).

Inventory options

  • Duplicate inventory names: It allows the option of having inventory item names with the same name. Option disabled by default.
  • CSV import support: If the option is deactivated, it allows the CSVs to be displayed as a report showing the inventory objects previously selected by the user as they appear in the list. By default it will be active to allow import.

Inventory data processing from Pandora FMS agents

  • Default owner: Default owner for those items.
  • Associated user and company. Companies with access to those items, and users with access to those items.

Authentication

Authentication type: LDAP, Active Directory, or local. If LDAP or AD is used.

Admin users will be the only ones that work “locally” without authenticating against an LDAP, so that if there is any problem when connecting with LDAP for user validation, administrators will always be able to access the tool.

If the LDAP or Active Directory login is configured, Integria IMS will “ask” these platforms whether the user exists and the password is correct, making a login attempt through an LDAP query. If successful, it will allow the user access to Integria IMS.

Configuration parameters:

  • Session timeout: In seconds.
  • Automatically create remote users: So that new users can access the tool from the first attempt if they have an LDAP/AD user. If it is not enabled, the user must already exist in Integria IMS, and the password must match the LDAP password.
  • Auto-create profile: Profile to assign to automatically created users.
  • Auto-create group: Group assigned to the automatically created user, with the profile used in the previous field.
  • Automatically create a blacklist: List of users, separated by commas, that will not be able to access.
  • LDAP/AD Server : IP address or FQDN of the LDAP/AD server.
  • LDAP/AD Port.
  • LDAP version (LDAP only).
  • Start TLS: It will use the Transport Layer Security (TLS) protocol in communications between the client and the server to encrypt communications.
  • DN Base (LDAP only): Distinguished Name (DN) used by the LDAP server. For example: ou=People,dc=example,dc=com.
  • Login attribute (LDAP only): Login attribute that LDAP uses during the authentication process. For example UID (User Identification Code).
  • Domain (AD only).

Configuration Example for LDAP

Configuration Example for Active Directory

CRM

In the configuration section, you will find a tab for CRM management:

You may activate or deactivate invoice ID automatic generation and modify its structure:

In the Invoice ID pattern field, a text string is saved, which will be used as pattern to generate identifiers. This pattern will contain a fixed part and a variable. The variable part must be numerical and work as the first element from which to calculate a sequence. The variable part will go between square brackets. The rest will be constant on all invoices.

Pattern example: 15/[1000]

In this case, the first three invoices to be generated will be 15/1000, 15/1001 and 15/1002.

Invoice ID generation applies only to Sent invoices.

You may also modify your invoice data, including the logo (to upload images, you may do so using the integrated file manager, under SettingsFile Manager), in the Custom logos folder.

In the configuration section of the CRM you may also rename the states of the leads to customize your pipeline.

Maintaining old data

It allows the system to specify how to manage history information.

  • Days to delete events: Old events will be deleted from the indicated days. If the specified value is zero 0, the data will never be erased (this applies to all other options in this section).
  • Days to delete closed tickets: Tickets with a closing date older than the days indicated will be deleted. Related data will also be erased.
  • Days to delete Work Units: Work hours older than the days indicated will be deleted, as long as they belong to disabled projects.
  • Days to delete Work Units: Work orders with an update date older than the days indicated will be deleted.
  • Days to clear audit information: Audit data older than the specified days will be erased.
  • Days to delete sessions: Sessions older than the days indicated will be deleted.
  • Days to delete Workflow events: Old workflow events will be deleted from the indicated days.
  • Days to delete old shared files: Uploaded files that are older than the specified days will be deleted.
  • Days to delete file tracking data: Audit data older than the specified days will be erased.
  • Days to delete backups.
  • Days to delete invalid emails that could not be sent.
  • Days to delete scheduled reports.

The Restore to default values option will return the initial values of all the configuration parameters in this section.


The Delete all data option will delete ALL the data from the database and also the attached files.

Project management

  • Users without UT completion: List of users who do not have working hours autocomplete, separated by commas.
  • Working hours per day: To calculate metrics.
  • UT autocomplete (days): This feature will autocomplete UTs on unassigned days for all users except those listed in Users without UT completion. Days that will autocomplete backward from the current moment. If not specified manually, the working hours will be auto-completed by default. The hours entered are not assigned to any task in any project, but to the “Unexcused” hours. For example, if you set 15 days, they will be completed with the number of Hours of work per day, for all days in which the hours entered are lower than that number, for the previous 15 days from the current date.
  • Default time for a project WU: When creating a WU, it will use that amount of time by default (in hours).
  • Default currency.
  • Total vacation days: Number of vacation days that will be used for the corresponding calculations in the vacation report section.

License

Enter Integria IMS license in this section. Once entered, click Update license for Integria IMS to verify whether it is valid.

If you click on the padlock you may see the details of your license.

If the maximum number of allowed users of the license is exceeded, the users' login will be automatically disabled.

Once the license has been corrected or extended, just return to this section and click Allow session start (login).

eHorus

Chatbot

To activate ChatBot and configure the server and channels.

GitLab

For integration with GitLab you need an access token that belongs to a GitLab user with permissions to see the tickets of the project that interest you.

Creation of personal access token in GitLab:

  1. Login in GitLab.
  2. In the upper right corner, select the avatar icon.
  3. Edit profile.
  4. Access tokens.
  5. Enter name and optional expiration date for the token.
  6. Select the desired scopes.
  7. Keep the personal access token in a safe place. After leaving the page, you will no longer have access to the token.


You also need the project's URL. Example:

https://example.es:8080/api/v4/projects/1/

And the base URL of the images to be able to load the images that contain the tickets in their description and in their comments. Example:

https://example.es:8080/artica/integria/

System tools

The tools mentioned here can only be accessed by system administrator users due to their power. Some tools, if misused, can render the system inoperative (e.g. SQL manager, file manager).

Update

The online Update Manager allows you to automatically update Integria IMS with the latest product patches and versions with a simple click.

Update offline

The offline updater allows you to upload update packages to installations that do not have Internet access. This tool supports .oum files, packages that contain the files that will be updated in Integria IMS console, they only contain the files that have been modified.

To allow uploading of large packages, it may be necessary to increase the value of the upload_max_filesize, memory_limit and post_max_size of php.ini file to a value higher than the size of the packages to be uploaded.

File manager

The file manager is used to upload and delete files to Integria IMS internal system. This is useful for conveniently uploading new logos or user avatars. It is also the easiest way to upload new files to Integria IMS integrated file distribution system. These files are located in the /attachment/downloads directory.

To upload avatar images, you may do so in the /images/avatars directory.

You may change the default icons in the /images directory.

Global news

It allows adding small system news, which will be visible to all users when they log in. Useful for example to notify of changes in the platform or notices about interventions, service disconnection or others.

Database manager

It is a direct interface against the system database, in SQL.


For the exclusive use of expert users as its misuse can cause irreversible damage to the tool and the deletion of data.

Links

Links can be added and removed and displayed in the Links section of the main menu.

System events

History of events that took place in the system, such as sending scheduled reports, executing cron tasks, system failures, etc.


It does not save user activity information, as it is stored in the audit log.

Audit log

All the actions of each user in each section will be reflected in this record. If someone modifies a customer's data, it will be known when and what was changed. If someone deletes an invoice, it will be known when and what invoice, and so on. Allows you to search by a specific substring.

Error log

It displays the error log (if it is enabled), useful for identifying possible system code errors. In case of query or ticket, provide the last entries (by date) of this log.

Custom string translation

It allows replacing any text that appears in Integria IMS interface by a customized one.

In the interface there is a combo where you may select the language you want to modify and a free field to search for the text. The search is carried out on the original language which is English, all translations are based on this language.

Custom screens

Defining a home screen with links to specific sections of Integria IMS or external pages:

It can be visible either as a new section of the upper horizontal menu or as an Integria IMS home screen.

It is global for the system, appearing as main one when logging in or clicking on the upper left logo of the tool. The editor allows us a high customization level of the screen and the widgets to be displayed.

Backups

The backup section allows Integria IMS users to make manual or scheduled backups of their attachments and their database.

The first one consists of a list of existing backups in your backup folder within Integria IMS directory. From here you may delete a backup, download it to your machine or restore your Integria IMS system from a backup from the list (you must be especially careful when performing this action as the backup will replace the database information with the one you had in that backup, making the information added between the backup and the system in its current state disappear).The second action allows scheduling so that, after a specific time interval, your Integria IMS system is backed up. To create a backup schedule, you must include a name for the schedule, a backup mode (there are three modes, only database, only attachments or both), a backup periodicity (weekly by default) and a backup address. Email to which you will receive notifications if something goes wrong in this backup. Also in the same section you will have available the list of schedules for editing or deleting, as appropriate.

The third and last section is responsible for making manual backups right away, offering the possibility of creating a backup with the name and the desired mode (and optionally an email address for error notifications) right away without having to wait for to a scheduled one. This backup will be created in your backup folder within Integria IMS directory and will be available in the backup list.

It also has the possibility of uploading your own previously downloaded backups, these must have the same structure that the tool generates to keep consistency and not be previously in the database.

This is a highly sensitive feature, we always recommend having the backups physically (in addition to having them in their corresponding folder within Integria IMS directory) to have a backup if something goes wrong when restoring the system to a previous version.

Go back to Integria IMS Documentation Index