Differences

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

--- faq [2024/02/13 15:04] – [STARTUP ERROR: "Couldn’t retrieve trigger: ..."] emr
+++ faq [2024/02/15 00:00] – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 To analyze or reproduce a problem the Stages Support team often asks to send the Stages runtime information to [[http://stages-support@ul.com|stages-support@ul.com]]. This is an archived set of Stages configuration and logfiles that provides detailed information on the Stages environment and can only be opened by the Stages Support team.
-If the .pks/.pks2 file created is too big for email transfer please use our upload form: [[https://upload.methodpark.de|https://upload.methodpark.de]]\\
+If the .pks/.pks2 file created is too big for email transfer please use our upload form: [[https://upload.methodpark.de|https://upload.methodpark.de]]\\  The requested **Ticket ID** to upload data is visible in the mail subject of the respective Stages Support mail:** [SupportID#1234567812345678]**
-The requested **
- <font inherit/inherit;;#c0392b;;inherit>Ticket ID</font>  **  to upload data is visible in the mail subject of the respective Stages Support mail:** [SupportID#
- <font inherit/inherit;;#c0392b;;inherit>1234567812345678</font>  ]**
 **Inside the Stages WebGUI**
@@ Line 18: / Line 15: @@
 **Manually on the Stages server**
-If login to the Stages WebGUI is not possible please proceed as follows:\\
+If login to the Stages WebGUI is not possible please proceed as follows:\\  \\  __Windows:__
-\\
-__Windows:__
-   - Connect to your Stages Server e.g. via Remote Desktop Connection or login to your Stages Server directly
+  - Connect to your Stages Server e.g. via Remote Desktop Connection or login to your Stages Server directly
   - On your Stages Server please open a command shell with administrative permissions
   - Navigate to folder: //<stages-installation-directory>\stages//\bin
@@ Line 29: / Line 24: @@
 __Linux:__
   - Connect to your Stages Server with a linux shell or login to your Stages Server directly
   - Navigate to folder: //<stages-installation-directory>/stages//  /bin
@@ Line 132: / Line 128: @@
 The stable URL always contains the “Version number” embedded in link:
-''stages.example.com/stages/#/workspace/100/for% <font inherit/inherit;;#e74c3c;;inherit>2025.01</font>  /(process/activity/_LT2BcM7j89iq0vSy_p5cRA)''
+''stages.example.com/stages/#/workspace/100/**for%2025.01**/(process/activity/_LT2BcM7j89iq0vSy_p5cRA)''
-The link is stable in regard to__ releases of new process versions__. It is **not **stable in regard to __renaming process versions__.\\
+The link is stable in regard to__ releases of new process versions__. It is **not **stable in regard to __renaming process versions__.\\  We would generally advise against renaming process versions that have already been released or reviewed, as the corresponding version can then no longer be found under the released names. (So not only via link, but also from any review protocols in which the name is written).
-We would generally advise against renaming process versions that have already been released or reviewed, as the corresponding version can then no longer be found under the released names. (So not only via link, but also from any review protocols in which the name is written).