Plugin installed incorrectly. Rename plugin directory 'swiftmail.backup' to 'swiftmail'.
en:software:tim:deploy_processdefinition
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:software:tim:deploy_processdefinition [2016/04/21 14:25] amanda.zens |
en:software:tim:deploy_processdefinition [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)// | ||
| ====Deploying a Process Definition==== | ====Deploying a Process Definition==== | ||
| - | In order for a process definition to be successfully integrated into TIM and be ready to use, it first has to be deployed/uploaded. The [[http://tim.taskinmotion.de/loom-portal/deploy.htm | Deployment interface ]] is used to issue a process definition in TIM. | + | In order for a process definition to be successfully integrated into TIM and be ready to use, it first has to be deployed/uploaded. The Deploy-interface is used to issue a process definition in TIM. The interface can be called under: |
| + | <code> http://<server>:<port>/loom-portal/deploy.htm </code> | ||
| \\ | \\ | ||
| - | For this procedure to be successfully implemented, the user has to be registered as a **deployer** in Signavio and have the [[roles| rights ]] of a **deployer**.\\ | + | The Process definition itself must have either the appropriate [[en:software:tim:user_profile_properties|user]] or one of its [[en:software:tim:user_profile_properties|groups]] listed as the [[en:software:tim:roles|deployer]]. Additionally, this user or group must have the role of [[en:software:tim:roles|deployer]] in TIM. Lastly, the process definition has to be passed to TIM as either a .zip file or as a bpmn file.\\ |
| Also, the process definition has to be exported as a .zip file and released in TIM. \\ | Also, the process definition has to be exported as a .zip file and released in TIM. \\ | ||
| + | <note tip>An SVG Graphic for a bpmn is optional. A zip-file already contains a graphic and therefore a graphic does not need to be added </note> \\ | ||
| + | | ||
| + | {{:software:tim:deployment_default.png?400 |}} | ||
| - | {{ :software:tim:deployProcess.png }} | + | {{:software:tim:deployment_bpmn.png?400 |}} |
| - | A confirmation message will be shown after the deployment procedure has been executed successfully (without any problems). | + | ---- |
| - | {{ :software:tim:deployProcess2.png }} | + | A confirmation message will be shown after the deployment procedure has been executed successfully (without any problems). |
| - | A message will also be shown if an error occurs. | + | {{:software:tim:deployment_sccess.png?600 |}} |
| - | {{ :software:tim:deployProcess3.png }} | + | ---- |
| + | ==== Automatically Deploying the Process ==== | ||
| + | Should the process still require configuring within the [[en:software:tim:processrepository|ProcessRepository]] before being deployed, then the check-box marked **Publish process automatically** can be deactivated. | ||
| + | <note tip> If the option is deactivated, it will appear only in the final deployment.</note> | ||
| + | ----- | ||
| + | ==== Direct deployment from the model ==== | ||
| + | If the process is to be deployed without being exported beforehand, this can be accomplished using the following URLs | ||
| + | <code>http://<server><:port>/loom-portal/Deploy.iGrafx</code> | ||
| + | or | ||
| + | <code>http://<server><:port>/loom-portal/Deploy.signavio</code> | ||
| + | If the process should not be directly activated here, this may be designated by adding the suffix **?publish=false**. | ||
| + | <code>http://<server><:port>/loom-portal/Deploy.iGrafx?publish=false</code> | ||
| + | ---- | ||
| + | ==== Error and Error Removal ==== | ||
| + | If an error occurs and the process definition is not deployed thereafter, the following points should be addressed before contacting support for help: | ||
| + | * Is the user correctly entered or is the [[en:software:tim:tim.properties#default-client|Mandant]] missing? | ||
| + | * Is the password entered correctly of is the [[en:software:tim:userprofil_profile|LDAP Authentifcation]] on/off? | ||
| + | * Is the correct user/group used entered as the deployer? | ||
| + | * Does the user have **deployer** [[roles| rights]]? | ||
| + | * Are all of the groups correctly entered into the characteristics of the process model? | ||
| + | |||
| + | {{ :software:tim:process_properties.png?600 |}} | ||
| + | A message will also be shown if an error occurs.\\ | ||
| - | If the process definition could not be properly deployed due to an error, please consult the following checklist before contacting support: | ||
| - | * Has the name of the user been correctly entered into the form? | ||
| - | * Has the password been correctly entered? | ||
| - | * Has the user or group been granted the status of a deployer? | ||
| - | * Has the process been correctly modeled (**Check for deployment**)? | ||
| - | * Have all roles been correctly assigned within the properties of the current process model? | ||
| - | * Has the user been granted full **deployer** [[roles| rights]]? | ||
| - | <note tip>If problems are still experienced, please contact TIM via e-mail at support@tim-solutions.de. Please send the file **server.log** as an attachment .</note> | + | <note tip>If problems are still experienced, please contact TIM via e-mail at support@tim-solutions.de. Please send the file **server.log** as an attachment.</note> |
en/software/tim/deploy_processdefinition.1461241524.txt.gz · Last modified: 2021/07/01 09:54 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: 2013 T!M Solutions GmbH
