Emails sent

Users can have a look at the list of the automatic emails sent.

emails sent screen

emails sent screen

All the information about the email, including the status showing whether the email was correctly sent or not.

You can see in the activity feed of the item the trace of the sending of the corresponding email with the subject and the text of the message.

Emails to send

You must enable the Activate email grouping option in the global parameters

The programmed emails will be grouped in this screen before their automatic sending based on the period entered in the global parameters

Scheduled report

In reports, you can schedule sending emails for accurate reports.

You can get the list and details of this programming on this screen

Click on Button Delete to cancelled the programmation

scheduled report screen

Scheduled report screen

See: Report Sending programmation


Users can have a look at the alerts sent.

By default, administrators can see all the alerts sent, and other users only see their own alerts.

Alert screen

Alert screen


You can define some message that will be displayed on the login and today screen.

Section Description

Required File legend Required Fields




Unique Id for the message

Required File Title

Header of the message

Required File Message type

Type of message

Sart Date

Date when the message begins

End Date

Date when the message ended


Complete text of the message

Detail section

You can apply visibility filters.

  • by profile

  • by project

  • by organization

  • by team

  • per user

Login screen with message

Login screen with message

Check the “Show on login screen” box to see your message on the login screen.

Import data

Imports data from CSV or XLSX files.

How to do

  1. Select the element type from the list.

  2. Select file format (CSV or XLSX).

  3. Select the file.

  4. Click on Import data button to start importing.

Report of the import

  • Data that is not imported because not recognized as a field appear in grey text in the result table.

  • Data that are voluntarily not imported (because must be calculated) appear in blue text in the result table.

Import users

  • The password field must be cut and pasted from the database because it is encrypted.

  • If you enter some readable password, the users will not be able to connect.


  • If you want to create new users don’t put any id because if id already exists, it will be overridden by the new (with possibility to erase admin user…).

  • Always keep in mind that your import may have some impact on administrator user.

  • So be sure to keep an operational admin access.

Importing document versions

  • Two ways to import document versions:

    • by describing only the version, with its standard fields.

    • by describing the document and the version (the name of the fields of the version will be followed by ‘(DocumentVersion)’, or its translation into the current language).


CSV import

  • The CSV import file may also include :
    • ‘importFile’ field that will give the link to the version file (this file will have to be reachable by the PHP server).

    • ‘target’ field that can be set to ‘DELETE’ (the file to be imported is deleted after import) or a directory name (the file to be imported is moved to this directory after import) or nothing (the file to be imported is not modified).

File format

The content of the imported file must fit the element type description.

To know the data that may be imported, click on the Help button.

Names of columns

  • The first line of the file must contain the name of the fields.

  • Names of columns can contain spaces (to have better readability).

  • The spaces will be removed to get the name of the column.


  • Look into the model class. The names are the same.

Date format

  • Dates are expected in format “YYYY-MM-DD”.

Data import process

Operations are performed, depending on whether the element type, the column or the column value.

Column Id

You may or may not add an “id” column in the file.

Column “id” exists and “id” is set in a line

  • The import will try to update the corresponding element, and will fail if it does not exist.

Column “id” does not exist or if “id” is not set in a line

  • The import will create a new element from the data.

Linked tables

For columns corresponding to linked tables (“idXxxx”), you can indicate as the column name either “idXxxx“ or “Xxxx” (without “id”) or the caption of the column (as displayed on screens).

Numeric value

  • If the value of the column is numeric, it is considered as the code of the item.

Non numeric value

  • If the value of the column contains non numeric value, it is considered as the name of the item, and the code will be searched for the name.

Columns with no data

  • In any case, columns with no data will not be updated.

  • Then you can update only one field on an element.

Clear data

  • To clear a data, enter the value “NULL” (not case sensitive).

Planning elements

  • Insertion into “Planning” elements (activity, project), automatically inserts an element in the table “PlanningElement”.

  • The data of this table can be inserted into the import file.


  • Do not import the value of “real work” on tickets, even if it is specified in the import file.

Automatic import

Imports can be automated.

Files placed on a defined directory will automatically be imported.


The files must respect some basic rules.

File name format

  • File name format is : “Class”_”Timestamp”.”ext”

  • Example of import file name: Ticket_20131231_235959.csv


  • The type of item to be imported (Ticket, Activity, Question, …).


  • Timestamp defined to be able to store several files in the directory.

  • Format is free.

  • The recommended format is “YYYYMMDD_HHMMSS”.


  • File extension, representing its format.

  • Valid extensions are CSV and XLSX.

File format

  • The files must follow the ProjeQtOr File format.

  • Files must be full and consistent.


  • The files should not be directly created in the import folder.

  • They must be created in a temporary folder and moved afterwards.

Import process

  • Correctly imported files are moved to a “done” sub folder of the import folder.

  • If an error occurs during import of a file, the full file is moved to “error” sub-folder of the import folder, even if there is only one error over many other items correctly integrated.

  • You can get the result as a log file and/or email summary.

Cloned Environnement

You can duplicate the complete environment (data and code) to form a simulation environment.


The CRON program must be started and running so that the simulation request can be taken into account and can be generated.

Administration of simulation requests

Cloned environment parameters

Cloned environment parameters

This parameters are also be accessible from simulated environments.

Click on Parameter on the Simulation Management screen

Management of rights and limitations per profils

Definition of profiles that have the right to create a simulation.

You can limit the number of total simulations per profiles.

This limitation can have some advantages:

  • Avoid saturating the server.

  • Force users to clean up their files.

  • Limit performance degradation caused by the creation of a simulated environment

The removal requests are decremented. If the limits are reached, the request screen to create a simulated environment is blocked.

Invalid Request

Example of a invalid request due to too much creation request.

Sequencing of the creation of simulations

The time required to create a simulation space may vary. Depending on your database, your servers or even if several requests are generated simultaneously. It is an operation which can take time. That is why you can set frequencies for creation requests.

  • Fixed frequency

    Analyzes creation requests at regular intervals and starts the generation of simulation environment as soon as a request is encountered.

  • At a given time

    In order to avoid any slowing down of the database, you can program the generations of the spaces at a specific time of the day. This allows these to be programmed outside working hours.

Copying datas

It is necessary to copy the code and the data because the simulations created in a version could no longer be compatible with the code of the main instance that has migrated.

The creation of a simulation instance is a heavy process for the server: duplication of code, duplication of data…

That’s why when generating your simulation space, not all data is copied.

Is not copied

  • Archived data (closed)

  • Update history

  • Attached documents and files

Copy of the code

  • Disabling all automation and notifications.

  • Update the simulations table to record the actual creation:

    • Date and time of actual creation,

    • Flag “available environment”

    • Instance access URL

The cloned Environment managment

Cloned Environment managment

Cloned environment managment

This screen allows you to manage your queries for new simulation environments, to follow them or to request the deletion of a particular simulation.

You can also track requests from other users based on your profiles and your rights.

Generating a simulation environment

To request the creation of a new simulation area, click on Add

A pop up will appear allowing you to make your request.

Add request

Add request

Identify the profile making the request, name your space (required) and confirm your request by clicking on OK

The simulated databases will always have a name prefixed by simu_ followed by the name of the simulation.


  • Creation dates: Indicate precisely the date on which you made your request for simulation space.

  • Availability dates: Indicates the date on which your space was actually generated. They are indicated to you when your request is taken into account.

  • Delation dates: Indicates the date on which your space will be completely deleted. The simulation space must actually be generated for the deletion request status to appear. If the database is in the request phase and therefore not yet generated, then the deletion is immediate and the deletion request status does not appear..

Color code

  • Blue: Request being created

  • Orange: Warning (delete request)

  • Red: Error creating the environment (path, rights …)

  • Green: Environment creates

Go to the cloned Environment

When your simulation is ready, green status, you can open your cloned environment. Click on icon goto to launch the environment.

A new tab opens with a new ProjeQtOr session. Authenticate yourself, you can start working in your environment.

Cloned environment session

Cloned environment session

The instance area turns red when you are in a simulation space.

Not all screens or functions will be accessible in this space.

For example, you will not be able to request and create a new simulation space in your cloned environment.

Copy a cloned Environment

You did a successful simulation on one of your cloned environment.

You want the copy to run other tests but without touching the simulation.

Just copy this environment.

The origin of the copy will then be indicated in the list with a shortcut to access it.

Deleting a simulation environment

Deletion requests are stored in the simulation table.

They are processed in the same process as creations, but always with priority to free up space before allocating new resources to new instances.


To avoid overly broad rights management and server invasion problems, all simulations (code) will be placed in a “simulation” directory outside of the main ProjeQtOr directory.

Thus, if the main instance is accessible via the url “”, the simulations will be accessible via the url “”.


You can defined manually notifications in this screen.



You receive notifications as soon as you authenticate on the login screen

Connection screen with notification

When you are logged in, you have a reminder at the top of the screen.

You have the number of unread notifications

Hover over it for the list of notifications to appear

A slight color line in front of the name indicates the type of notification

  • Red = alert

  • Blue = information

  • Yellow = warning

Click on the name of the notification to display its detail screen.


You can also display the notification in the part below the menu.

See: Secondary menu - Notifications section

Click on an unread notification for discover the details.

  • The first icon indicates the type of notification

  • the second icon indicates how the notification was created
    • System Notification

    • Manual Notification

  • The third icon indicates if the notification has a definition. see: Notification System

  • Click on the fourth icon for display the detail of the notification


Type of alert

  • infos type information

  • Warning type Warning

  • Alert type alert

  • Sum sum - Records all the type

Audit connections

Audit connection proposes a view of “who is online”.

you can know which platform the user has logged on to, his browser and dates of his first and last access, as well as the duration of the connection

Audit connection screen


The administrator has the possibility to force the disconnection of any user (except his own current connection, see: admin-console.