User Tools

Site Tools

:: Version 2.7.0 ::

2_7_0:release:2_7_whats_new

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
2_7_0:release:2_7_whats_new [2019/12/20 09:41]
vdumas
2_7_0:release:2_7_whats_new [2020/01/10 09:56] (current)
Line 18: Line 18:
   * what is the size and type of the file.   * what is the size and type of the file.
  
-{{:2_6_0:​release:​attachment-write-short.png?​|}}+{{:2_7_0:​release:​attachment-write-short.png?​|}}
  
 <note tip>As before, you can drag and drop a file directly on an object. In the console, it works even if not on the ''​Attachment''​ tab.</​note>​ <note tip>As before, you can drag and drop a file directly on an object. In the console, it works even if not on the ''​Attachment''​ tab.</​note>​
  
-{{:2_6_0:​release:​attachment-write-portal.png?​|}}+{{:2_7_0:​release:​attachment-write-portal.png?​|}}
  
 ===== OQL: NOT IN SELECT ===== ===== OQL: NOT IN SELECT =====
Line 53: Line 53:
 You can set a different policy with a regex. More details: [[2_7_0:​feature:​password-policy]] You can set a different policy with a regex. More details: [[2_7_0:​feature:​password-policy]]
  
-===== Product updater ​=====+===== Application upgrade ​=====
  
 With iTop 2.7.0 and above, iTop administrators can upgrade or downgrade their iTop, directly from iTop web interface (console), without having access to the iTop server.\\ With iTop 2.7.0 and above, iTop administrators can upgrade or downgrade their iTop, directly from iTop web interface (console), without having access to the iTop server.\\
Line 64: Line 64:
 === New behaviors === === New behaviors ===
  
-  * A new icon, allow to copy the url to the displayed object, to provide it to a colleague or the support agent. +  * A new icon, allows ​to copy the url to the displayed object, to provide it to a colleague or the support agent. 
-  * When a user portal ​click outside of a pop-up window in which he has entered some data, he is asked with a confirmation message, instead of loosing his entries. +  * When a user portal ​clicks ​outside of a pop-up window in which he has entered some data, he is asked with a confirmation message, instead of loosing his entries. 
-  * When the user cancel ​or submit ​a Ticket form, it now displays a refreshed version of the ongoing tickets.+  * When the user cancels ​or submits ​a Ticket form, it now displays a refreshed version of the ongoing tickets.
   * Contacts linked to a Ticket and displayed within the Ticket form are limited to the contacts that the user is allowed to see.   * Contacts linked to a Ticket and displayed within the Ticket form are limited to the contacts that the user is allowed to see.
   * External keys attributes displayed in forms are now clickable as in the Console, to open the related object in his own pop-up above the current form.   * External keys attributes displayed in forms are now clickable as in the Console, to open the related object in his own pop-up above the current form.
Line 72: Line 72:
 === New customization possibilities === === New customization possibilities ===
  
-  * Navigation rules allow a Portal developer to specify where to go, when a Portal user cancel ​or submit ​a form, in modal or non-modal mode. +  * Navigation rules allows ​a Portal developer to specify where to go, when a Portal user cancels ​or submits ​a form, in modal or non-modal mode. 
   * The Browse Brick now supports to connect two levels not only with a 1:n relationship but also a n:n. So for example, you can define Customer Contracts as the first level, then Service as the second level, and Service Subcategory as the third one.   * The Browse Brick now supports to connect two levels not only with a 1:n relationship but also a n:n. So for example, you can define Customer Contracts as the first level, then Service as the second level, and Service Subcategory as the third one.
-  * When n:n related objects (''​AttributeLinkedSetIndirect''​) are displayed in a form, a new parameter ​allow to limit the displayed objects to those allowed to the user, or to display all of them (//as it was done before 2.7//).+  * When n:n related objects (''​AttributeLinkedSetIndirect''​) are displayed in a form, a new parameter ​allows ​to limit the displayed objects to those allowed to the user, or to display all of them (//as it was done before 2.7//).
   * Number of displayed objects in a page for a Browse and a Managed Brick, can be specified.   * Number of displayed objects in a page for a Browse and a Managed Brick, can be specified.
  
Line 82: Line 82:
  
 If you are a Web developper, you can now more easily customize iTop Look & Feel thanks to new attributes added to html tags within iTop pages. If you are a Web developper, you can now more easily customize iTop Look & Feel thanks to new attributes added to html tags within iTop pages.
-See [[2_7_0:​feature:​markup-html|here for more]]+See [[2_7_0:​feature:​markup|here for more]]
  
 +===== Configuration =====
  
 +The administrator can use variables within the Configuration file. When editing the Configuration file within iTop, those variables are now preserved when saving the file. This allows to define a Configuration file, applicable regardless of the environment in which you will deploy your iTop. This follows recommendations for deployment on modern cloud platforms: [[https://​12factor.net/​config|Best practice]].
 +<code PHP Configuration>​
 +    '​db_host'​ => $_ENV['​DB_HOST'​],​
 +</​code>​
 +
 +
 +We have added a parser to prevent an administrator to put active code in the Configuration file (function calls, system commands,​...) within the online editor of the Configuration file. If you want to do this, which is not recommended,​ you must edit the file on your system and disable the online edition.
 ===== API authentication ===== ===== API authentication =====
  
Line 93: Line 101:
   * Customize login/​logoff forms to align them to your corporate standards   * Customize login/​logoff forms to align them to your corporate standards
   * Apply Security Policies on Local users   * Apply Security Policies on Local users
 +
 +
  
 === Authentication === === Authentication ===
Line 135: Line 145:
  
 [[2_7_0:​customization:​authentication|All details here]] [[2_7_0:​customization:​authentication|All details here]]
 +
  
  
Line 176: Line 187:
  
  
 +===== Miscellaneous =====
  
 +  * Security: restrict access over /env-xxx
  
 +==== For extension developers ====
  
 +=== Access to object modifications ===
 +  * Improve customization possibilities by providing a list of changes within ​
 +  * in [[2_7_0:​customization:​api:​extensions:​iapplicationobjectextension#​ondbupdate|\iApplicationObjectExtension::​OnDBUpdate]] using \DBObject::​ListChangesUpdated()
 +  * in \DBObject::​AfterUpdate using \DBObject::​ListChangesUpdated()
  
-===== Miscellaneous ===== 
- 
-  * OQL : Peformances (eg: Counts) and Transactions 
-  * Improve customization possibilities by providing a list of changes within [[2_7_0:​customization:​api:​extensions:​iapplicationobjectextension#​ondbupdate|API OnDBUpdate]] 
  
-  * Security: prevent browsing of /env-xxx 
  
 ==== Logs filtering ===== ==== Logs filtering =====
Line 191: Line 204:
  
 When writing logs you can now pass new parameters :  When writing logs you can now pass new parameters : 
-  * channel: enable log filtering ​(see below). Examples: channel could be an extension, a feature, a class name or a PHP namespace.+  * channel: enable log filtering ​based on an extension, a feature, a class namea PHP namespace,...
     * If not given, the default channel is the class log name (''​IssueLog'',​ ''​SetupLog'',​ ...)     * If not given, the default channel is the class log name (''​IssueLog'',​ ''​SetupLog'',​ ...)
   * context: if given, the context will be written alongside the log.   * context: if given, the context will be written alongside the log.
  
  
-The default ​behavior ​is to all log levels ​except ''​Debug''​.+The default ​log level is all of them except ''​Debug''​.
 This can be tuned using the configuration parameter ''​log_level_min'':​ it leverages the possibility to filter the logs below a given level on a per channel basis. This can be tuned using the configuration parameter ''​log_level_min'':​ it leverages the possibility to filter the logs below a given level on a per channel basis.
  
Line 223: Line 236:
   * \MetaModel::​EnumLinksClasses   * \MetaModel::​EnumLinksClasses
   * \MetaModel::​EnumLinkingClasses   * \MetaModel::​EnumLinkingClasses
 +  * \MetaModel::​GetNextKey : see [[2_7_0:​release:​2_7_whats_new#​ticket_ref_generation]]
  
 === Customer portal === === Customer portal ===
  - Tags <​submit>​ and <​cancel>​ will no longer be supported in action rules, use navigation rules instead.  - Tags <​submit>​ and <​cancel>​ will no longer be supported in action rules, use navigation rules instead.
  
2_7_0/release/2_7_whats_new.1576831274.txt.gz · Last modified: 2019/12/20 09:41 by vdumas

";