User Tools

Site Tools


extensions:approval_extended

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:approval_extended [2019/09/18 10:40]
vdumas
extensions:approval_extended [2020/04/15 14:15] (current)
Line 4: Line 4:
 description_wiki : Control your approval process with predefined rules based on service catalog description_wiki : Control your approval process with predefined rules based on service catalog
 index_hidden ​    : yes index_hidden ​    : yes
-version ​         : 1.4.5 +version ​         : 2.0.1 
-release_dt ​      : ​2019-03-26+release_dt ​      : ​2020-03-18
 itop-version-min : 2.4.0 itop-version-min : 2.4.0
 +download_hidden ​ : http://​www.combodo.com/​itop-extensions/​combodo-approval-process-automation-2.0.1-553.zip
 code             : combodo-approval-process-automation code             : combodo-approval-process-automation
 state            : stable state            : stable
Line 12: Line 13:
 alias-code_hidden : approval-extended alias-code_hidden : approval-extended
 alternate-name ​  : Approval Extended alternate-name ​  : Approval Extended
-module-lists_hidden : approval-base/​2.6.1, combodo-approval-extended/​1.2.6, combodo-sla-computation/​2.2.1, itop-approval-portal/​1.0.4+module-lists_hidden : approval-base/​3.0.1, combodo-approval-extended/​1.3.0, combodo-sla-computation/​2.3.0, itop-approval-portal/​1.0.4
 diffusion ​       : iTop Hub diffusion ​       : iTop Hub
 ---- ----
 +
  
 <​note>​For iTop versions older than 2.2.0 use [[approval_extended_1_1|1.1.3]]. \\ <​note>​For iTop versions older than 2.2.0 use [[approval_extended_1_1|1.1.3]]. \\
Line 29: Line 31:
 ===== Features ===== ===== Features =====
  
-  * **New in 1.4.0** Tickets waiting for Approval and bulk approval available in Portal.+
   * Automated, rule based, approval mechanism.   * Automated, rule based, approval mechanism.
   * Supports passive or active approval and configurable timeout delay.   * Supports passive or active approval and configurable timeout delay.
   * Two levels of approbation with several approvers in parallel at each level.   * Two levels of approbation with several approvers in parallel at each level.
-  * Approvers can approve or reject a request in one click from an email (no need to have an iTop account) or multiple requests pending for their approval ​either on the console.+  * Approvers can approve or reject a request in one click from an email (no need to have an iTop account) or multiple requests pending for their approval ​in Console or Portal.
   * Graphical view of the approval status on each ticket.   * Graphical view of the approval status on each ticket.
   * Configurable approval email message, with multi-language capabilities.   * Configurable approval email message, with multi-language capabilities.
Line 40: Line 42:
  
 ^ Date ^ Version ^ Description ^ ^ Date ^ Version ^ Description ^
 +|  2020-03-18 ​ |  2.0.1  | * Bring compatibility with iTop 2.7 \\ * Fix TWIG template not found when trying to open object form |
 +|  2020-03-05 ​ |  2.0.0  | * Add compatibility with iTop 2.7+ \\ * Update DE translations \\ * Enable Notification management delegation \\ * ActionEmailApprovalRequest : default sender for sample email actions \\ * Fix: Approval reminder in edit mode : double pop-up \\ * from and reply_to can be specified in ActionEmailApprovalRequest objects (were only available in approval_base module settings) \\ * New methods in EnhancedSLAComputation to ease extensibility \\ * Open Hours mandatory for Coverage Window |
 |  2019-03-26 ​ |  1.4.5  | * Fix: Approval reminder in edit mode : double pop-up | |  2019-03-26 ​ |  1.4.5  | * Fix: Approval reminder in edit mode : double pop-up |
 |  2018-12-13 ​ |  1.4.4  | * Fix spanish translation files encoding \\ * Add missing reconciliation key to the ApprovalScheme class \\ * Add missing reconciliation key to the ExtendedApprovalScheme class \\ * Fix UI glitch on approval form \\ * Improve jQuery compatibility (jQuery 3 since iTop 2.6) | |  2018-12-13 ​ |  1.4.4  | * Fix spanish translation files encoding \\ * Add missing reconciliation key to the ApprovalScheme class \\ * Add missing reconciliation key to the ExtendedApprovalScheme class \\ * Fix UI glitch on approval form \\ * Improve jQuery compatibility (jQuery 3 since iTop 2.6) |
Line 61: Line 65:
 ===== Requirements ===== ===== Requirements =====
  
-Requires at least iTop 2.4.0.+  * Requires at least iTop 2.4.0. 
 +  * [[latest:​admin:​cron|cron.php]] must be running to enable processing of approval timeout. 
  
 ===== Installation ===== ===== Installation =====
Line 75: Line 81:
 ^ Module ^ Parameter ​ ^  Type  ^  Description ​ ^  Default Value  ^ ^ Module ^ Parameter ​ ^  Type  ^  Description ​ ^  Default Value  ^
 | approval-base | email_sender | string | Sender eMail address, as seen in the approval email. If left blank, sending the email will fail. |  | | approval-base | email_sender | string | Sender eMail address, as seen in the approval email. If left blank, sending the email will fail. |  |
-| approval-base | email_reply_to | string | Default "reply to" eMail address for the approval email. ​| (optional) ​defaults to email_sender |+| approval-base | email_reply_to | string | Default "reply to" eMail address for the approval email. ​If empty defaults to ''​email_sender''​ |  ​|
 | approval-base | comment_attcode | string | Attribute into which the user comments will be reported. Can be a case log or text. The comments are all aggregated. Note: the comment can also be viewed as a tooltip. | (optional) | | approval-base | comment_attcode | string | Attribute into which the user comments will be reported. Can be a case log or text. The comments are all aggregated. Note: the comment can also be viewed as a tooltip. | (optional) |
 | approval-base | list_last_first | boolean | In case several executions occur, drives the order in which the results of the executions are displayed (vertically). | false | | approval-base | list_last_first | boolean | In case several executions occur, drives the order in which the results of the executions are displayed (vertically). | false |
 | approval-base | enable_reminder | boolean | Enable the feature "send a reminder"​. | true | | approval-base | enable_reminder | boolean | Enable the feature "send a reminder"​. | true |
 | approval-extended| enable-admin-abort | boolean| Allow defined profiles to bypass the approval process. Profiles allowed to bypass the process are defined in the variable bypass_profiles. |true | | approval-extended| enable-admin-abort | boolean| Allow defined profiles to bypass the approval process. Profiles allowed to bypass the process are defined in the variable bypass_profiles. |true |
-| approval-extended| target_state | string | state that may trigger the approval process ​| default "​new"​Warning: the transition wait_for_approval has to be defined for this state. |+| approval-extended| target_state | string | state that may trigger the approval process. ​The event ''​ev_wait_for_approval''​ must exist on this state, ending on ''​wait_for_approval'' ​state. ​| new |
 | approval-extended| bypass_profiles | string | CSV list of profiles. Having any of the given profiles is sufficient to be allowed to bypass approval processes. Set to an empty string to deny the feature to anybody. | Administrator,​ Service Manager | | approval-extended| bypass_profiles | string | CSV list of profiles. Having any of the given profiles is sufficient to be allowed to bypass approval processes. Set to an empty string to deny the feature to anybody. | Administrator,​ Service Manager |
 | approval-extended| reuse_previous_answers | boolean | If a person is approver at both level then his level 1 decision is reused at level 2 | true | | approval-extended| reuse_previous_answers | boolean | If a person is approver at both level then his level 1 decision is reused at level 2 | true |
Line 151: Line 157:
 The pages show a list of already defined approval rules. Click on the button "​new"​ to create a new one: The pages show a list of already defined approval rules. Click on the button "​new"​ to create a new one:
  
-{{ :​extensions:​approvalruleedit.png?​direct&​900 ​|}}+{{ :​extensions:​approvalruleedit.png?​nolink ​|}}
  
  
Line 182: Line 188:
 Once the approval rule has been defined, you can assign it to a service subcategory,​ either from the approval rule itself (tab //Service subcategory//​) or from the service subcategory:​ Once the approval rule has been defined, you can assign it to a service subcategory,​ either from the approval rule itself (tab //Service subcategory//​) or from the service subcategory:​
  
-{{ :​extensions:​combodo-approval-extended-servicesubcategory.png?​direct&​400 ​|}}+{{ :​extensions:​combodo-approval-extended-servicesubcategory.png?​direct |}}
  
 ===== Approving process ===== ===== Approving process =====
  
 Approver with an iTop login can connect anytime and check if they have Requests pending their approval. From the Helpdesk menu, click on Ongoing approvals: Approver with an iTop login can connect anytime and check if they have Requests pending their approval. From the Helpdesk menu, click on Ongoing approvals:
-{{ :latest:products:​professional:​approval_menu.png?nolink ​|}} +{{ :extensions:approval-menu.png?direct ​|}}
-FIXME //move image under extensions//​+
  
 The page shows a list of the User Requests having an approval process running, and for which your approval is being requested: The page shows a list of the User Requests having an approval process running, and for which your approval is being requested:
-{{ :latest:products:​professional:​approval_monitoring.png?nolink&​600 ​|}} +{{ :extensions:approval-monitoring.png?direct ​|}}
-FIXME //move image under extensions//​+
  
 Approver without iTop login, can still approve or reject Request, but they must have received the notification for this. Approver without iTop login, can still approve or reject Request, but they must have received the notification for this.
Line 257: Line 261:
  
  
 +===== Question & Answers =====
 +
 +**Question: What happen if the approval rule returns zero approvers, on all level of approval?** \\
 +Answer: The request is never entering the approval cycle.
 +
 +**Question: How to automatically send a reminder to Approvers after a given delay?** \\
 +Answer: There is no easy way to do this today.
 +  * add a date field //​approval-requested-on//​ on the to be approved object class, let say a Ticket. ​
 +  * When the Ticket enter the state ''​waiting for approval'',​ on the transition set the //​approval-requested-on//​ date with now().
 +  * Create a daily background task, which retrieve Ticket in ''​waiting on approval'',​ since exactly ''​delay*n''​ days, and send a reminder (assuming there is an accessible PHP function to trigger this reminder FIXME) -> with delay = 7 this would trigger a reminder every seven days as long as not approved.
extensions/approval_extended.txt · Last modified: 2020/04/15 14:15 (external edit)

";