Änderungen von Dokument 07 Variablen verwenden

Zuletzt geändert von Carina Enke am 25.07.2024

Von 405.1 nach 406.1 Von 411.1 nach 412.1

Von Version 406.1

bearbeitet von Carina Enke
am 07.06.2019

Änderungskommentar: Mittels Scroll Versions veröffentlicht aus dem Bereich ONYXintern und Version 8.7.

Auf Version 411.1

bearbeitet von Carina Enke
am 08.05.2019

Änderungskommentar: Mittels Scroll Versions veröffentlicht aus dem Bereich ONYXintern und Version 8.7.

Rohform
Im Layout

Zusammenfassung

Seiteneigenschaften (1 geändert, 0 hinzugefügt, 0 gelöscht)
Objekte (1 geändert, 0 hinzugefügt, 0 gelöscht)
- Confluence.Code.ConfluencePageClass[0]

Details

Seiteneigenschaften

Inhalt

@@ -169,8 +169,8 @@
  The use of variables allows the creation of dynamic task text. Task content can be generated randomly or adapted to the user, previously given answers, or assessments. For implementation, two different types of variables are provided in the tab of the same name:
  * **Pre-processed variables**
--Pre-variables are assigned before the task is displayed and therefore make it possible to adapt the task text as well as the predefined and correct answers dynamically. In this way, task templates can be defined with the help of placeholders. These are replaced by specific random values per test run on the basis of defined intervals, value drop-down lists, or calculation rules. As a result, test tasks will be different but similar for each participant and test run.
--* **{{id name="PostVariablen_en"/}}Post-processed variables**
++Pre-variables are assigned before the task is displayed and therefore make it possible to adapt the task text as well as the predefined and correct answers dynamically. In this way, task templates can be defined with the help of placeholders. These are replaced by specific random values per test run on the basis of defined intervals, value drop-down lists, or calculation rules. As a result, test tasks will be different but similar for each participant and test run.
++* **Post-processed variables**
  Post-variables are only assigned after the task has been answered, submitted, and automatically assessed, thus allowing access to response-specific values such as the learner's response or the points for correct answers. In this way, adaptive feedback content, follow-up tests, and task series can be enabled. The use of conditions and MAXIMA statements allows responses from learners to be analysed and typical errors identified. Based on these insights, teachers will then be able to provide appropriate feedback or customised exercises.
  [[image:attach:Editor - Tab Variablen_de.png]]
@@ -190,7 +190,7 @@
  {{/panel}}
  {{panel borderColor="#ddd" bgColor="#f0f0f0" borderStyle="solid" title="Further information"}}
--* [[MAXIMA manual>>url:http://maxima.sourceforge.net/docs/manual/de/maxima.html||shape="rect"]]
++* [[MAXIMA manual>>url:http://maxima.sourceforge.net/docs/manual/maxima.html||shape="rect"]]
  * [[MAXIMA good practice examples>>url:https://bildungsportal.sachsen.de/opal/auth/RepositoryEntry/5499682817/CourseNode/93229879750473/wiki/Index||shape="rect"]]
  * [[MAXIMA system information>>url:http://maxima.sourceforge.net/||rel="nofollow" shape="rect" class="external-link"]]
  {{/panel}}
@@ -208,10 +208,45 @@
  (% class="confluence-embedded-file-wrapper image-center-wrapper confluence-embedded-manual-size" %)[[image:attach:Testrun - Beispielaufgaben_de.png]]
--{{info}}
--For a typical application example for the use of variables as random parameters, see [[Example "Transport" - Use of random parameters>>url:https://www.bps-system.de/help/display/ONYXintern/.Beispiele+zum+Einsatz+von+Variablen+v8.7||shape="rect"]].
--{{/info}}
++
++{{id name="Example ~"transport~" - Use of random parameters"/}}
++
++=== Example "transport" - Use of random parameters ===
++
++As an example, a typical application task is created. The goal is to calculate the distance travelled by a vehicle based on speed and time. The speed is dependent on the vehicle type.
++
++
++
++|(% colspan="1" %)(% colspan="1" %)
++(((
++[[image:attach:Editor - Tab Variablen zur Beispielaufgabe_de.png]]
++)))|(% colspan="1" %)(% colspan="1" %)
++(((
++In the example, the [[text variable>>url:https://www.bps-system.de/help/display/ONYXintern/.Textvariablen+v1.11||shape="rect"]] {transport} will be randomly initialised with one of the following values: "bike", "bus", or "train". The [[numeric variable>>doc:Numerische Variablen]] {speed} is randomly selected from a value range. Thus, the value range for the speed {speed} should be set in dependence of the selected vehicle {transport}, since a "bike" is generally slower than a "train".
++)))
++|(((
++[[image:attach:Editor - Beispiel einer Bedingung_de.png]][[image:attach:Editor - weiteres Beispiel einer Bedingung_de.png]]
++)))|(((
++For dependent value setting, we use the variable condition. In the condition, we can define the value range for the variable {speed} depending on the selected value of the variable {transport}. For the bike ({transport}="bike"), for example, a value range of 10 to 30 (km/h) was set.
++)))
++|(((
++[[image:attach:Editor - Nutzung von Variablen in der Aufgabenstellung_de.png]]
++)))|(((
++The given values of the task are integrated into the task text by specifying the variable name ({transport}, {speed}, and {hours}). In the example, the variable is included in a task of the type [[calculation interaction>>url:https://www.bps-system.de/help/display/ONYXintern/.Berechnungsaufgabe+v1.6||shape="rect"]].
++
++The variable with the correct solution {distance} is bound to the gap.
++)))
++|(((
++[[image:attach:Testrun - Beispielaufgabe im Testrun_de.png]]
++)))|(((
++One of the defined values will be randomly chosen for each participant and each test attempt. In the example, the value "bike" was randomly inserted, which is why a speed in the value range of 10 to 30 (km/h) was selected.
++)))
++
++
++
++{{id name="Post-processed variables"/}}\\
++
  == (% style="background-color: rgb(220,231,239);font-size: 20.0px;" %)Post-processed variables(%%) ==
  Define variables that are determined after the submission of the task in order to create adaptive task and test scenarios. Post-processed variables (in short: post-variables) allow you to access the learners' answers and points achieved. You can use this information to enhance following content such as feedback or task descriptions of follow-up attempts. In addition, it is possible to intervene in the assessment and make subsequent changes to it.
@@ -218,31 +218,181 @@
  (% class="confluence-embedded-file-wrapper image-center-wrapper confluence-embedded-manual-size" %)[[image:attach:Testrun - Nutzerlösung einer Beispielaufgabe_de.png]][[image:attach:Testrun - Post-Variable im Feedback_de.png]][[image:attach:Testrun - Post-Variable Lösungshinweis_de.png]]
--\\
--{{info}}
--The following examples for the use of post-processed variables show possible application scenarios:
--* [[Example "Transport" - Adaptive task feedback>>url:https://www.bps-system.de/help/display/ONYXintern/.Beispiele+zum+Einsatz+von+Variablen+v8.7||shape="rect"]]
--* [[Example "Transport" - Points deduction per attempt>>url:https://www.bps-system.de/help/display/ONYXintern/.Beispiele+zum+Einsatz+von+Variablen+v8.7||shape="rect"]]
--* [[Example "Transport" - Assessment of the maximum score>>url:https://www.bps-system.de/help/display/ONYXintern/.Beispiele+zum+Einsatz+von+Variablen+v8.7||shape="rect"]]
--{{/info}}
++{{id name="Example ~"transport~" - Adaptive task feedback"/}}
++=== Example "transport" - Adaptive task feedback ===
++
++Adaptive feedback allows for individual feedback based on the learners' answers. The participant can, for example, be provided with concrete hints or error messages. Post-variables (post-processed variables) allow access to the learners' responses, e.g. to each gap. Attempts at solutions or even previous answers can also be included in the feedback.
++
++In the following, the example "transport" will be extended by simple adaptive feedback. Feedback should give the user an indication of whether their answer was less than or greater than the correct solution or hint at how the correct solution can be calculated.
++
++{{panel titleColor="black" titleBGColor="#FFB266" title="Example ~"transport~" - Adaptive task feedback"}}
++{{expand title="Show example ..."}}
++|(((
++[[image:attach:Editor - Angabe von POST-Variablen_de.png]]
++)))|(((
++In the first step, the __[[text variable>>url:https://www.bps-system.de/help/display/ONYXintern/.Textvariablen+v1.11||shape="rect"]] __{div} in a condition is set to the value "less than" or "greater than" in the tab **//Variables// **, depending on whether the answer given by the learner was less than or greater than the correct answer.
++
++In addition, the learner's answer will be stored in a __[[numeric variable >>url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]]__{answer} so that it can be easily accessed from within the feedback.
++)))
++|(((
++[[image:attach:Editor - Post-Variablen im Feedback_de.png]]
++)))|(((
++In the second step, concrete task feedback is stored. The participant should see the feedback only if they have submitted an incorrect answer. Therefore, the general feedback **//Answer was wrong// **needs to be selected from the tab **//Feedback// **. For more information about task feedback, refer to the help page __[[Set>>url:https://www.bps-system.de/help/display/ONYXintern/.Feedback+festlegen+v1.11||shape="rect"]] [[feedback>>url:https://www.bps-system.de/help/display/ONYXintern/.Feedback+festlegen+v1.11||shape="rect"]] __.
++
++Individual feedback and values stored in the variables can be included in other feedback by entering the variable name ({div}, {answer}).
++
++Additional feedback blocks can also be added as individual feedback. In the example, a hint was added to the feedback, which is permanently displayed regardless of the learner's answer. Feedback can also contain detailed sample solutions and calculations. For tasks with random parameters, pre-processed variables can be added to the feedback.
++)))
++|(((
++[[image:attach:Testrun - Feedback mit Post-Variablen_de.png]]
++)))|(((
++Since the task contains random parameters, different values will be displayed for each test attempt and participant. According to the defined content, the participant will now additionally be shown individual feedback based on their answer.
++
++You can decide whether you want to retain the random parameters of a task or have them redefined for future attempts. For more information, see the section **//Reset variables// **on the help page __[[Set test options__.__>>url:https://www.bps-system.de/help/display/ONYXintern/.Test-Optionen+festlegen+v1.11||shape="rect"]]__
++)))
++{{/expand}}
++{{/panel}}
++
++
++
++{{id name="Example ~"transport~" - Points deduction per attempt"/}}\\
++
++=== Example "transport" - Points deduction per attempt ===
++
++If the participant has several attempts at a solution, individual and successive hints can be provided to help them answer the question. In such scenarios, it may be especially desirable to have points deducted from the participant's total score for each additional attempt. A participant who answers the task correctly at the first attempt receives the full score. The more hints or attempts they need, the fewer points they will obtain.
++
++For the __[[example "transport">>url:https://www.bps-system.de/help/display/ONYXintern/.Variablen+verwenden+v1.12#id-.Variablenverwendenv1.12-Variablenverwenden-Beispiel&quot;Transport&quot;-EinsatzvonZufallsparametern||shape="rect"]] __, a points deduction for each attempt should be realised using variables. Therefore, the maximum possible score for the task has been increased to 10 points. For each additional attempt, the score should be reduced by one point. In other words, if a task is attempted multiple times within one test run, points will be deducted for each additional attempt. The number of **test attempts** is not considered. It is strongly recommended to make the points deduction visible to the participant. This can be achieved by embedding appropriate text elements into the task and feedback.
++
++|(((
++[[image:attach:Editor - Variablen zur Beispielaufgabe_de.png]]
++)))|(((
++(% class="WordSection1" %)
++(((
++To perform the points deduction, the following variables need to be defined:
++
++* (((
++**The [[numeric variable>>url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]] [[url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]]{deduction_attempt} stores the points deduction for each attempt.**
++
++In this example, the total score should be reduced by one point. Therefore, {deduction_attempt) is set to a static value of 1. Since the value is static, it can be created as a pre-variable (pre-processed variable).
++)))
++
++* (((
++**The [[numeric variable>>url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]] [[url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]]{deduction} stores the current points deduction depending on the attempt.**
++
++The points deduction {deduction} is calculated as the product of the number of attempts (system variable NUMATTEMPTS) and the deduction of points per attempt {deduction_attempt}. Since this value is computed per attempt, it must be calculated as a post-variable (post-processed variable).
++)))
++
++In addition, the score of the task must be recalculated according to the points deducted by **setting the system variable SCORE** and verified by the author. This includes the definition of a new condition: If the points deduction is greater than 0, the score of the task is reduced by the respective value.
++
++//Note: For the sake of simplicity, all of the variables for generating general task and feedback content have been hidden in the screenshot.//
++)))
++)))
++|(% colspan="1" %)(% colspan="1" %)
++(((
++Note within the task:
++
++ [[image:attach:Editor - Hinweis in der Aufgabenstellung_de.png]]
++
++Note as individual feedback:
++
++[[image:attach:Editor - Hinweis als individuelles Feedback_de.png]]
++)))|(% colspan="1" %)(% colspan="1" %)
++(((
++A general note will be included in the task to make the learner aware of the fact that points may be deducted, and an individual note will be displayed as a feedback message immediately after the deduction.
++
++{{note}}
++//Please note that if there has been a points deduction, the follow-up attempt can no longer be considered as completely correct because the maximum score can no longer be achieved. This also affects the presentation of the points achieved (colour marking), the correct/incorrect marking, and the general task feedback, which depends on the condition whether or not the participant has reached the maximum score. By using individual feedback, the logic for displaying feedback content can be individually adapted to the task.//
++{{/note}}
++)))
++|(((
++[[image:attach:Testrun - Beispielaufgabe in unterschiedlichen Versuchen_de.png]]
++)))|(((
++Points will now be negated according to the number of attempts needed.
++
++* Participants who enter the correct answer at the first attempt receive the full score.
++* Participants who enter the correct answer in a follow-up attempt receive partial points. Through appropriate feedback, these participants can be given individual hints at the solution to encourage them to continue processing the task on their own.
++)))
++
++
++
++{{id name="Example ~"transport~" - Assessment of the maximum score"/}}\\
++
++=== Example "transport" - Assessment of the maximum score ===
++
++If several attempts are possible per task, it might be the case that a participant will not score as many points in a follow-up attempt as was already scored before. If desired, the highest score achieved can be remembered and eventually used for the assessment. The participant should be informed accordingly through notes and be shown the scoring of the current attempt as well as the maximum score achieved for all attempts.
++
++In the following, the __[[example "transport">>url:https://www.bps-system.de/help/display/ONYXintern/.Variablen+verwenden+v1.12#id-.Variablenverwendenv1.12-Variablenverwenden-Beispiel&quot;Transport&quot;-EinsatzvonZufallsparametern||shape="rect"]] __will help to explain how the assessment of the maximum score can be enabled.
++
++|(((
++[[image:attach:Editor - Beispiel mehrere Versuche_de.png]]
++)))|(((
++To do this, the following variables need to be defined.
++
++The entire implementation is done using post-variables ( [[post-processed variables>>url:https://www.bps-system.de/help/display/ONYXintern/.Variablen+verwenden+v1.12#id-.Variablenverwendenv1.12-Variablenverwenden-NachAbgabeverarbeiteteVariablen||shape="rect"]] ), since, among other things, the score of the current attempt will be accessed.
++
++(% style="font-size: 10.5pt;line-height: 107.0%;" %)Note: For the sake of simplicity, all of other variables for generating task and feedback content have been hidden in the screenshot.
++
++* **The [[numeric variable >>url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]]{best_score} stores the highest score achieved in multiple attempts. **
++The variable {best_score} is initialised without a value and later controlled by a condition:
++** At the **first attempt** (% style="text-indent: -18.0pt;" %),(%%) {best_score} is not yet initialised (NULL) and will be set to the current score {current_score}. Condition: IF best_score = (% style="font-size: 10.5pt;" %)//NULL THEN best_score = value: current_score//
++** Each **successive attempt** is checked to see whether the score achieved {current_score} is greater than the present maximum score {best_score}, in which case the latter will be adjusted accordingly. Condition: IF current_score > best_score THEN best_score = value: current_score
++* **The [[numeric variable >>url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]]{current_score} stores the current score for the current attempt.** **
++**The current score can be read out using the system variable SCORE. As this value is changed manually by the author, it should be temporarily stored in a variable. This guarantees access to the current score and, for example, the output of this value in notes and feedback.
++** With each attempt, the variable** **{current_score} is set to the value of the system variable SCORE. Condition: IF best_score = NULL THEN best_score = value: current_score**
++**
++* **The [[numeric variable>>url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]] {best_score_is_used} stores whether the task assessment was changed manually.**
++In the example, the participant should be shown an additional note if the best score is used for assessment instead of the current score. Therefore, the auxiliary variable {best_score_is_used} is applied, which will be set to the value 1 if the task assessment was changed manually.**
++**
++** The variable {best_score_is_used} is set to the value 1 if the current score is less than the highest score, which has been achieved so far. Otherwise, the variable is given the value 0. Condition: IF best_score > current_score THEN best_score_is_used = value: 1 ELSE best_score_is_used = value: 0
++)))
++|(((
++Note within the task:
++
++[[image:attach:Editor - Hinweis zur Wertung in Aufgabenstellung_de.png]]
++)))|(((
++In order to let the learners know which assessment procedure will be applied, a general note is included with the task. This note will be accompanied by some individual feedback information if the task assessment has been changed manually and the best score option has been configured.
++)))
++|(% colspan="1" %)(% colspan="1" %)
++(((
++Note as individual feedback:
++
++[[image:attach:Editor - Hinweis zur Wertung als individuelles Feedback_de.png]]
++)))|(% colspan="1" %)(% colspan="1" %)
++(((
++Feedback can be controlled using the auxiliary variable {best_score_is_used}, which displays individual feedback to the participant depending on whether its value is 0 or 1. It includes a reference to the current score {current_score} as well as to the maximum score {max_score} achieved so far. In addition, the system variable MAXSCORE is used to embed the maximum possible score in the note.
++)))
++|(((
++[[image:attach:Testrun - Beispielaufgabe Wertung in unterschiedlichen Versuchen_de.png]]
++
++
++)))|(((
++If the participant receives a lower score in a test attempt than in a previous attempt, the best score will be the one counted. In the example given, the exercise is configured in such a way that different values will be displayed for each test attempt. The participant has already solved the task at the second attempt and received the full score. Therefore, the participant obtains the full score for the task despite giving an incorrect answer. The feedback displayed to the participant also indicates that they have received 0 points for the current attempt, but that their best score of 10 points will be assessed.
++
++This example can be combined with the application scenarios described above:
++
++* Example "transport" – Use of random parameters
++* Example "transport" – Adaptive task feedback
++* Example "transport" – Points deduction per attempt
++)))
++
  == Definition of a variable ==
--Click on **//Add new variable// **in the tab// **Variables** //to define a new variable. The new variable is immediately added and displayed in the overview table. Below the table, an edit window opens for the new variable. The order of the variables and conditions within the variables table can be easily changed using drag-and-drop.
++Click on **//Add new variable// **in the tab// **Variables** //to define a new variable. The new variable is immediately added and displayed in the overview table. Below the table, an edit window opens for the new variable.
  [[image:attach:Editor - Definition einer Variable_de.png]]
  Assign a **unique variable name **for your variable. The variable name serves as an identifier and allows you to **use the variable in the task text**. Please make sure that the variable name does not contain any umlauts, special characters, and spaces. The input is case sensitive. If a variable is defined with the name "a", it can be accessed via the placeholder {a}.
--Select the **variable type**. The following variable types are available:
++Select the **Variable type**. The following variable types are available:
--* [[Numerical variables>>url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]]:
++* [[Numeric variables>>url:https://www.bps-system.de/help/display/ONYXintern/.Numerische+Variablen+v1.11||shape="rect"]]:
  ** Integer
  ** Floating-point number
  * [[Text variables>>url:https://www.bps-system.de/help/display/ONYXintern/.Textvariablen+v1.11||shape="rect"]]
--* [[Image variables>>url:https://www.bps-system.de/help/display/ONYXintern/.Bild+Variablen+v1.11||shape="rect"]]
++* [[Image Variables>>url:https://www.bps-system.de/help/display/ONYXintern/.Bild+Variablen+v1.11||shape="rect"]]
  Depending on the selected variable type, you have various options for the **determination of the value**:
@@ -251,7 +251,7 @@
  * Random selection
  * Calculation (MAXIMA)
--Variables can also be created** without immediately setting a value**. If the value is set at a later point in time, it can for example be set in dependence of other variables (cf. conditions).
++Variables can also be created without immediately setting a value. If the value is set at a later point in time, it can for example be set in dependence of other variables (cf. conditions).
  == Use of variables   ==
@@ -263,9 +263,9 @@
  == Definition of a condition ==
--In the tab// **Variables**//, you can also use conditions. A condition allows you **to set the value of a variable, depending on other variable values**.
++In the tab// **Variables** //, you can also use conditions. A condition allows you **to set the value of a variable, depending on other variable values**.
--Click on **//Add new condition// **to define a new condition. The new condition is immediately added and displayed in the overview table. Below the table, an edit window opens for the new condition. The order of the variables and conditions within the variables table can be easily changed using drag-and-drop.
++Click on **//Add new condition// **to define a new condition. The new condition is immediately added and displayed in the overview table. Below the table, an edit window opens for the new condition.
  [[image:attach:Editor - Neue Bedinung anlegen_de.png]]
@@ -275,12 +275,8 @@
  Please note: A variable that is used within a condition must be initialised before the condition. The variable which is used in the condition or statement must be added as a single variable before the condition can be added. If the value of a variable is set within one or more conditions, it will be unnecessary to set a value for the variable itself. Select the empty entry from the value selection list.
--**Link conditions:** If you have created several conditions for an IF section, you can configure how these entries will be linked. Determine whether all conditions (AND) or at least one condition (OR) must be met for the condition to be executed.
++You can add any number of alternative conditions (ELSE IF - branches). Different variables can be set in the conditions. In the simple mode, only one variable can be set per condition. For more complex rules, you can switch to the **expert mode**. A more detailed description can be found in the help pages for the expert mode.
--(% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" style="color: rgb(255,102,0);" %)[[image:attach:Editor - Verknüpfung von Bedingungen_de.png]]
--
--(% style="color: rgb(51,51,51);" %)**Alternative conditions (ELSE IF): **(%%)You can add any number of alternative conditions (ELSE IF branches). Different variables can be set in the conditions. In the simple mode, only one variable can be set per condition. For more complex rules, you can switch to the **expert mode**. A more detailed description can be found in the help pages for the expert mode.
--
  == Expert mode (IMS QTI) ==
  The variable representation in the test and task content is based on the principle of template declaration and the template processing of the [[IMS QTI 2.1 specification>>url:http://www.imsglobal.org/question/||shape="rect"]]. The template processing of IMS QTI 2.1 offers far more possibilities for setting variables, in particular by the nesting of logical expressions and conditions. The description entered in the expert mode is directly transferred into the XML of the task as a single template processing expression.
@@ -293,7 +293,7 @@
  == View variable assignment ==
--When testing your test content, you can view the variable assignment in the [[preview>>url:https://www.bps-system.de/help/display/ONYXintern/.Inhalte+ansehen+v1.11||shape="rect"]] at any time. These details are also available to the supervisor or assessor in the [[results views>>url:https://www.bps-system.de/help/display/ONYXintern/.Ergebniseinsicht+v1.11||shape="rect"]]. In addition to the variable assignment, information on the MAXIMA tasks as well as possible system errors are displayed.
++When testing your test content, you can view the variable assignment in the [[preview>>url:https://www.bps-system.de/help/display/ONYXintern/.Inhalte+ansehen+v1.11||shape="rect"]] at any time. These details are also available to the supervisor or assessor in the [[Results views>>url:https://www.bps-system.de/help/display/ONYXintern/.Ergebniseinsicht+v1.11||shape="rect"]]. In addition to the variable assignment, information on the MAXIMA tasks as well as possible system errors are displayed.
  For more detailed information, please refer to the following help sections:

Confluence.Code.ConfluencePageClass[0]

id

@@ -1,1 +1,1 @@
--301072837
++226231057

url

@@ -1,1 +1,1 @@
--https://www.bps-system.de/help/display/SOV/wiki/spaces/ONYX/pages/301072837/Variablen verwenden
++https://www.bps-system.de/help/display/SOV/wiki/spaces/ONYX/pages/226231057/Variablen verwenden

Änderungen von Dokument 07 Variablen verwenden

Zusammenfassung

Details

Suchen

ONYXGlobal

ONYXMenü

Zuletzt besucht