User Tools

Site Tools


extensions:request-templates

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
extensions:request-templates [2018/05/23 11:18]
vdumas
extensions:request-templates [2019/04/23 12:18]
vdumas
Line 4: Line 4:
 description_wiki : Define personalized request forms based on the service catalog. Add extra fields for a given type of request. description_wiki : Define personalized request forms based on the service catalog. Add extra fields for a given type of request.
 index_hidden ​    : yes index_hidden ​    : yes
-version ​         : 2.0.10 +version ​         : 2.0.14 
-release_dt ​      : ​2018-01-26+release_dt ​      : ​2019-01-24
 itop-version-min : 2.3.2 itop-version-min : 2.3.2
-dependencies_s ​  : itop-service-mgmt/​2.0.0 or itop-service-mgmt-provider/​2.0.0,​ itop-request-mgmt/​2.0.0 or itop-request-mgmt-itil/​2.0.0 
-download_url ​    : http://​www.combodo.com/​itop-extensions/​combodo-customized-request-forms-2.0.10-292.zip 
 code             : combodo-customized-request-forms code             : combodo-customized-request-forms
 +state            : stable
 +product_hidden ​  : included
 alias-code_hidden : request-templates alias-code_hidden : request-templates
 alternate-name ​  : Request Templates alternate-name ​  : Request Templates
-module-lists_hidden : templates-base/​3.0.13, itop-request-template/​2.0.1, itop-request-template-portal/​1.0.0+module-lists_hidden : templates-base/​3.0.17, itop-request-template/​2.0.5, itop-request-template-portal/​1.0.0 
 +diffusion ​       : iTop Hub
 ---- ----
 +
  
 <note warning>​**Compatibility issue**: for iTop version lower than 2.4.0, there is a [[installation#​itop_before_240|special installation/​upgrade process]].</​note>​ <note warning>​**Compatibility issue**: for iTop version lower than 2.4.0, there is a [[installation#​itop_before_240|special installation/​upgrade process]].</​note>​
Line 46: Line 48:
  
 ===== Revision History ===== ===== Revision History =====
-^  ​Version ​ ​^  ​Release Date  ​^ ​ Comments ​ ^ +^  ​Release Date  ​^  ​Version ​ ​^ ​ Comments ​ ^ 
-|  2.0.10 ​ |  2018-01-26 ​  | Ticket fields can now be used in customized forms. Also fixed 2 bugs for usage in notifications templates ($service_details$) : N°1079 When the user leaves it undefined, then this is shown as an error message in the email: "​Custom field error: Wrong format: missing template_data"​ ; N°1080 When a field aims at selecting an object, the email body shows the id of the selected object. | +|  2019-01-30  ​|  ​2.0.14 ​ | Fix regression introduced in 2.0.10: custom date formats no longer working | 
-|  2.0.9  ​|  2018-01-05 ​  | Customized forms are now compatible with Incident | +|  2018-12-19 ​ |  2.0.13 ​ | - Fix unnecessary error messages popping on the screen when a DoCheckToWrite fails \\ - Fix execution notice (check array existence) \\ - Update spanish translations (thanks to Miguel Turrubiates!) | 
-|  2.0.8  ​| ​ 2017-11-13 ​ | Service_details is now documented on UserRequest creation before notification | +| 2018-06-27 | 2.0.12 | Add DE translation | 
-|  2.0.7  ​|  2017-09-08 ​ | Request template value not set in notification when creating an object | +| 2018-06-26 | 2.0.11 | ES + BR translations,​ default search attributes | 
-|  2.0.6  ​|  2017-03-01 ​ | Added module setting to reset template fields value when changing to a different template that contains fields with same codes | +|  2018-01-26 ​  |  2.0.10  ​| Ticket fields can now be used in customized forms. ​\\ Also fixed 2 bugs for usage in notifications templates ($service_details$) : \\ - N°1079 When the user leaves it undefined, then this is shown as an error message in the email: "​Custom field error: Wrong format: missing template_data"​ ; \\ - N°1080 When a field aims at selecting an object, the email body shows the id of the selected object. | 
-|  2.0.5  ​|  2016-12-13 ​ | Fixed issues when used in cunjunction with the legacy portal. Requires iTop > 2.3.2 for the date/time pickers to work fine | +|  2018-01-05 ​  |  2.0.9  | Customized forms are now compatible with Incident | 
-|  2.0.4  ​|  2016-11-29 ​ | Implemented placeholders (e.g. $this->​html(service_details)$. Requires iTop > 2.3.1 for the placeholders to work fine. | +|  2017-11-13  ​|  2.0.8  | Service_details is now documented on UserRequest creation before notification | 
-|  2.0.3  ​|  2016-09-08 ​ | Added validation pattern to Date and DateTime fields. Fixed a PHP Warning when launching the cron manually. | +|  2017-09-08 ​ ​| ​ 2.0.7  | Request template value not set in notification when creating an object | 
-|  2.0.2  ​|  2016-09-02 ​ | Hidden and Read-only fields are now rendered like multiline strings (like a textarea, though it is read-only) - Note that this will work fine in the console with iTop 2.3.0+, but requires iTop > 2.3.1 to take advantage of this enhancement in the enhanced customer portal (no change in the legacy portal!) | +|  2017-03-01 ​ ​| ​ 2.0.6  | Added module setting to reset template fields value when changing to a different template that contains fields with same codes | 
-|  2.0.1  ​|  2016-08-03 ​ | Support of the console and the enhanced customer portal (both require iTop 2.3.0, otherwise the behavior is the same as 1.0.5) | +|  2016-12-13 ​ ​| ​ 2.0.5  | Fixed issues when used in cunjunction with the legacy portal. Requires iTop > 2.3.2 for the date/time pickers to work fine | 
-|  1.0.5  ​|  2015-11-26 ​ | Fix for crash when submitting a ticket from the portal for a template with an ENUM field containing some special characters. | +|  2016-11-29 ​ ​| ​ 2.0.4  | Implemented placeholders (e.g. $this->​html(service_details)$. Requires iTop > 2.3.1 for the placeholders to work fine. | 
-|  1.0.4  ​|  2015-09-29 ​ | Fix for a crash when a "​drop-down list" field contains some weird characters (accents, question marks...) at the beginning of the list of values. | +|  2016-09-08 ​ ​| ​ 2.0.3  | Added validation pattern to Date and DateTime fields. Fixed a PHP Warning when launching the cron manually. | 
-|  1.0.3  ​|  2014-12-10 ​ | Cosmetics on the module name. | +|  2016-09-02  |  2.0.2  | Hidden and Read-only fields are now rendered like multiline strings (like a textarea, though it is read-only) - Note that this will work fine in the console with iTop 2.3.0+, but requires iTop > 2.3.1 to take advantage of this enhancement in the enhanced customer portal (no change in the legacy portal!) | 
-|  1.0.2  ​|  2014-04-03 ​ | Minor fix to allow non admin users to import Template fields in CSV. | +|  2016-08-03 ​ ​| ​ 2.0.1  | Support of the console and the enhanced customer portal (both require iTop 2.3.0, otherwise the behavior is the same as 1.0.5) | 
-|  1.0.1  ​|  2014-03-10 ​ | Bug fix for template fields with the same name as an attribute of the object. | +|  2015-11-26 ​ ​| ​ 1.0.5  | Fix for crash when submitting a ticket from the portal for a template with an ENUM field containing some special characters. | 
-|  1.0.0  ​|  2014-02-05 ​ | First version, never validated. |+|  2015-09-29 ​ ​| ​ 1.0.4  | Fix for a crash when a "​drop-down list" field contains some weird characters (accents, question marks...) at the beginning of the list of values. | 
 +|  2014-12-10 ​ ​| ​ 1.0.3  | Cosmetics on the module name. | 
 +|  2014-04-03 ​ ​| ​ 1.0.2  | Minor fix to allow non admin users to import Template fields in CSV. | 
 +|  2014-03-10 ​ ​| ​ 1.0.1  | Bug fix for template fields with the same name as an attribute of the object. | 
 +|  2014-02-05 ​ ​| ​ 1.0.0  | First version, never validated. |
  
  
Line 164: Line 170:
  
 Assuming that //this// is a UserRequest:​ Assuming that //this// is a UserRequest:​
-  * $this->​service_details$:​ a plain text representation of the selected values. This is suitable for a plain text email. Though it seems possible to use it within an HTML document, by using a PRE tag, this is NOT recommended because HTML entities (like <) still need to be escaped. +  * <​nowiki>​$this->​service_details$:​</​nowiki> ​a plain text representation of the selected values. This is suitable for a plain text email. Though it seems possible to use it within an HTML document, by using a PRE tag, this is NOT recommended because HTML entities (like <) still need to be escaped. 
-  * $this->​html(service_details)$:​ an HTML representation of the selected values.+  * <​nowiki>​$this->​html(service_details)$:​</​nowiki> ​an HTML representation of the selected values.
  
 Hidden fields are forcibly excluded from the placeholders. Hidden fields are forcibly excluded from the placeholders.
  
 When a template value corresponds to an object selected into iTop, the returned value will be the friendly name of the object. When a template value corresponds to an object selected into iTop, the returned value will be the friendly name of the object.
extensions/request-templates.txt · Last modified: 2019/04/23 12:18 by vdumas

";