Differences

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

--- en:software:component:parallel_approval [2014/12/04 09:34]
felix.studnitz
+++ en:software:component:parallel_approval [2021/07/01 09:52] (current)
@@ Line 1: / Line 1: @@
-FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)//
+FIXME **This page is not fully translated, yet. Please help completing the translation.** \\
+//(remove this paragraph once the translation is finished)//
 ===== Description =====
-Often with many processes an approval by several different persons working for the same company is necessary. This page will therefore provide useful tips and guidance on how to facilitate the approval of processes by at least one or more person(s).
+For many processes an approval by several different persons within the same company is necessary. This page will therefore provide useful tips and guidance on how to facilitate the approval of processes by at one to three people.
 ----
-===== Decision on granting parallel approval via pop-up window ======
+===== Decision on granting parallel approval via pop-up window =====
-The basic setup should be implemented in such a way that every user will receive a message via a pop-up window. This new window should give each user the option to decide wether to approve the process. If some users may have disapproved the process during this selection procedure, the process should take a different direction than if there had been an unanimous approval by all users. For this to be successfully implemented the model has to be designed according to the following way:
-{{ en:software:component:basic_parallel_approval.png?800 |}}
+The basic setup should be implemented in such a way that every user will receive a message via a pop-up window. This new window should give each user the option to decide whether or not to approve the process. If all users disapprove of the process during this selection procedure, the process should take a different direction than if approval had been unanimous. For this to be successfully implemented the model has to be designed according to the following: {{  :en:software:component:basic_parallel_approval.png?800  }}
-=== Explanation of the elements ====
+=== Explanation of the elements ===
-^ Nummer ^ Description ^
-^  1  | At this stage, the responsibiliy to assign an approval has to be granted to a distinct group of people. By using the [[en:software:tim:Smartform]] the membership for this group can be selected. By executing the command [[en:software:tim:smartform:selectusersbygroupbyclass|selectusersbygroupbyclass]] a maximum of three drop-down menus can be edited to select up to three users to give approval. |
-^  2  | To assign corresponding Swimlanes to selected group members the command [[en:software:tim:actionhandler:VariableAssignmentActionHandler]] has to be used. At this script node three Swimlanes named "Approval User 1-3" can be dedicated for the three aforementioned users. |
-^  3  | At this stage it has to be made sure if an individual user should participate in the process by giving his approval. If only two persons are required to give approval the third [[en:software:tim:Swimlanes|Swimlane]] dedicated to the so-called **Approval User 3** would not be necessary. The exclusive gateway [[en:software:tim:actionhandler:VariableExistsDecisionHandler]] can always be used to ensure that a flexible number of people become involved in the procedure. If in the drop-down menu no corresponding selection has been made then the task in this Swimlane will not be activated. |
-^  4  | The command [[en:software:tim:actionhandler:ProcessVariableSetter]] can be executed at the script node to generate a [[en:software:tim:process_variables|process variable]]. This process variable may then adopt the value **rejected**. This process variable will again be important at a later stage regarding Element **6**.  |
-^  5  | An Actionhandler does not necessarily have to be executed at this particular node. Although, the node may for example be connected to the command [[en:software:tim:actionhandler:GenerateIdentityProcessVariablesHandler]] to store data written by the user and which then is supposed to be sent as a [[en:software:tim:actionhandler:wordtemplatehandler|PDF ((WordTemplateHandler)]]. |
-^  6  | The command [[en:software:tim:actionhandler:VariableExistsDecisionHandler]] can be used at this exclusive gateway to check if the [[en:software:tim:process_variables|process variable]] encountered earlier at Stage 4 has in fact been properly executed. If this is the case, then this process will use the "true" pathway. |
-^  7  | At this stage, the process can be changed or extended as desired. |
------
+^Nummer^Description|
+^  1  |Because the parties responsible for granting approvals typically rotates, the user responsible for granting approval can be selected in this portion of the [[:en:software:tim:smartform|Smartform]]. In combination with the [[:en:software:tim:smartform:selectusersbygroupbyclass|selectusersbygroupbyclass]] cue, dropdowns may be created in which up to three users may be selected and granted approval rights.|
+^  2  |To assign corresponding Swimlanes to selected group members the command [[:en:software:tim:actionhandler:variableassignmentactionhandler|VariableAssignmentActionHandler]] has to be used. At this script node three Swimlanes named "Approval User 1-3" can be dedicated to the three aforementioned users.|
+^  3  |At this stage a check should be made, in order to see is a user is needed for clearance. If only two people are required to give approval, then the third [[:en:software:tim:swimlanes|Swimlane]] dedicated to the so-called **Approval User 3** would not be necessary. The exclusive gateway [[:en:software:tim:actionhandler:variableexistsdecisionhandler|VariableExistsDecisionHandler]] can always be used to ensure that a flexible number of people become involved in the procedure. If no selection has been made in the drop-down menu then the task in this Swimlane will not be activated.|
+^  4  |The command [[:en:software:tim:actionhandler:processvariablesetter|ProcessVariableSetter]] can be executed at the script node to generate a [[:en:software:tim:process_variables|process variable]]. This process variable may then adopt the value **rejected**. This process variable will be used again in Element **6**.  |
+^  5  |An Actionhandler does not necessarily have to be executed at this particular node. However, the node may, for example, be combined with the command [[:en:software:tim:actionhandler:generateidentityprocessvariableshandler|GenerateIdentityProcessVariablesHandler]] to store data written by the user and then send it as a [[:en:software:tim:actionhandler:wordtemplatehandler|PDF ((WordTemplateHandler)]].|
+^  6  |The command [[:en:software:tim:actionhandler:variableexistsdecisionhandler|VariableExistsDecisionHandler]] can be used at this exclusive gateway to check if the [[:en:software:tim:process_variables|process variable]] encountered earlier at Stage 4 has in fact been properly executed. If this is the case, then this process continue using the "true" pathway.|
+^  7  |At this stage, the process can be changed or extended as desired.|
-===== Rejecting and giving reasons for this via the Smartform =====
+----
-If giving reasons for a rejection is supposed to be mandatory this can be done by using the [[en:software:tim:Smartform]]. To accomplish this, the [[en:software:tim:Smartform]] has to be amended either by a [[en:software:tim:smartform_basics#auswahlbox_radiobuttons|radio button]] or a [[en:software:tim:smartform_basics#auswahlbox_checkboxes| check box]] or a [[en:software:tim:smartform_basics#auswahlfeld_selectbox|drop-down menu]]. In addition, [[en:software:tim:smartform_basics#eingabefelder|text areas]] will be required to write down any reasons for a rejection. \\
+===== Noting a justification for a rejection via Smartform =====
+If a justification for a rejection is considered necessary, this can be done by using the [[:en:software:tim:smartform|Smartform]]. To do this, the [[:en:software:tim:smartform|Smartform]] has to be amended either by a [[:en:software:tim:smartform_basics#auswahlbox_radiobuttons|radio button]], a [[:en:software:tim:smartform_basics#auswahlbox_checkboxes| check box]] or a [[:en:software:tim:smartform_basics#auswahlfeld_selectbox|drop-down menu]]. In addition, [[:en:software:tim:smartform_basics#eingabefelder|text areas]] will be required in order to note any reasons related to a rejection.\\
 \\
-The new HTML elements will have to be designed as [[en:software:tim:smartform_basics#pflichtfelder_beim_instanzstart|mandatory fields]] to ensure that a selection has been made and reasons for the rejection provided. To accomplish this the HTML attribute has only to be amended by entering **required="true**. \\
+The new HTML elements will have to be designed as [[:en:software:tim:smartform_basics#pflichtfelder_beim_instanzstart|mandatory fields]] to ensure that a selection is made and that the reasons for the rejection are provided. To accomplish this the HTML attribute has only to be amended by entering **required="true**.\\
-The process will then have the following design:
+The process will then have the following design setup: {{  :en:software:component:basic_parallel_approval_decline_via_sf.png?800  }}
-{{ en:software:component:basic_parallel_approval_decline_via_sf.png?800 |}}
-The red-colored area is the field in which a check will be conducted if any of the elements in the [[en:software:tim:Smartform]] has been assigned the status "rejected". If this is the case, then the process can be processed correspondingly. Checking the [[en:software:tim:process_variables|process variables]] may be done by using the [[en:software:tim:actionhandler:VariableDecisionHandler]] (formerly known as the SmartFormDecissionHandler).
+The framed area, marked in red, is the field in which a check is conducted to see if any of the elements in the [[:en:software:tim:smartform|Smartform]] were classified as "rejected". If this is the case, then the process can be executed correspondingly. The inspection of the [[:en:software:tim:process_variables|process variables]] may be performed using the [[:en:software:tim:actionhandler:variabledecisionhandler|VariableDecisionHandler]] (formerly known as the SmartFormDecisionHandler).
+\\

TIM Wiki / NEW TIM 6 Documentation

User Tools

Site Tools

Differences

Page Tools