modeling_2.0
Differences
This shows you the differences between two versions of the page.
|
modeling_2.0 [2024/11/06 10:49] montse [Usability from Modeling] |
modeling_2.0 [2025/06/19 11:58] (current) ale [Renaming variables in the diagram] |
||
|---|---|---|---|
| Line 49: | Line 49: | ||
| * **Delete elements**: allows you to delete the selected diagram object(s) using the 'trash can' icon. | * **Delete elements**: allows you to delete the selected diagram object(s) using the 'trash can' icon. | ||
| * **Diagram actions**: groups a series of actions that can be performed at the diagram level:\\ \\ {{ :acciones_de_diagramaen.png?direct&300 |}}\\ | * **Diagram actions**: groups a series of actions that can be performed at the diagram level:\\ \\ {{ :acciones_de_diagramaen.png?direct&300 |}}\\ | ||
| - | * **Assistants**: displays a list of available assistants:\\ \\ {{ :asistentesen.png?direct&300 |}}\\ \\ | + | * **Assistants**: displays a list of available assistants:\\ \\ {{ :en:edit_diagram:newassistants.png?direct&300 |}}\\ \\ |
| * **View diagram map**: by clicking this button, a thumbnail of the current diagram (at a scale of 4:1) is displayed in a box at the top right of the Canvas. | * **View diagram map**: by clicking this button, a thumbnail of the current diagram (at a scale of 4:1) is displayed in a box at the top right of the Canvas. | ||
| * **Magnifying glass**: allows you to perform free text searches on all diagram elements, and also allows you to narrow the searches on those elements that interest you at a given moment. | * **Magnifying glass**: allows you to perform free text searches on all diagram elements, and also allows you to narrow the searches on those elements that interest you at a given moment. | ||
| Line 69: | Line 69: | ||
| - **Optional step:** The result of this step will not impact the test result.\\ | - **Optional step:** The result of this step will not impact the test result.\\ | ||
| - **Comment out:** If this check is marked, the message will not be executed. | - **Comment out:** If this check is marked, the message will not be executed. | ||
| - | - **Breakpoint:** The breakpoint check is used to stop the execution of the test in this step. It is helpfull during the creation of the diagram.\\ \\ | + | - **Breakpoint:** The breakpoint check is used to stop the execution of the test in this step. It is helpfull during the creation of the diagram.\\ \\ |
| + | |||
| + | ==== Renaming variables in the diagram ==== | ||
| + | |||
| + | This new functionality is accessed through a new context menu option with the right mouse button, by clicking on a certain element of the diagram. To do this, the diagram must be unlocked. This option appears by clicking on: a message, a gate or a fragment of the diagram. | ||
| + | \\ \\ {{ :en:edit_diagram:picture1renamingvariables.png?nolink&500 |}}\\ | ||
| + | If no variable is declared in the element on which this action is executed, then the following message will appear: | ||
| + | |||
| + | \\ \\ {{ :en:edit_diagram:picture2renamingvariables.png?nolink&500 |}}\\ | ||
| + | On the other hand, if there are variables declared in the element, the following modal dialog for renaming variables appears: | ||
| + | |||
| + | Renaming variables dialog. | ||
| + | \\ \\ {{ :en:edit_diagram:picture3renamingvariables.png?nolink&500 |}}\\ | ||
| + | In this modal there are different **items**:\\ | ||
| + | * **Variable list**: This combo shows the list with all the variables declared in the selected item. This list does not contain neither global variables nor repository variables. | ||
| + | * **“Variable name” field**: Not editable field. This shows the variable selected in the list. | ||
| + | * **New variable name**: Here we will enter the new name for the selected variable. | ||
| + | * **“Rename” button**: Once the new variable name has been entered in its field, pressing this button automatically replaces all occurrences of that variable in the diagram. Once the variables have been renamed in the diagram, a message will appear for information purposes indicating the number of elements in which the variable has been renamed. | ||
| + | |||
| + | \\ \\ {{ :en:edit_diagram:picture4renamingvariables.png?nolink&500 |}}\\ | ||
| + | * **Revert the changes**: After renaming a variable, if for some reason you want to revert the changes and leave the diagram in its previous state, just press the **“Undo”** option from the context menu, or use the **CTRL+Z** key combination. | ||
| + | |||
| ==== Guards ==== | ==== Guards ==== | ||
| Line 882: | Line 904: | ||
| ====Introduction==== | ====Introduction==== | ||
| - | Library Management provides TAST, and specifically the diagram modeling part, with a library management tool to store, organize and query javascript functions or Sql queries that the user considers useful, for example to be reused in the messages of other diagrams.\\ \\ Predefined functions such **executeJavascript** or **dbGetQueryData**, are examples of messages that include a //javascript code// or a //sql query//:\\ \\ {{ :en:librarymanagement1.png?direct&400 |}}\\ \\ {{ :en:librarymanagement2.png?direct&400 |}}\\ \\ | + | Library Management provides TAST, and specifically the diagram modeling part, with a library management tool to store, organize and query javascript functions or Sql queries that the user considers useful, for example to be reused in the messages of other diagrams.\\ \\ Predefined functions such **executeJavascript** or **dbGetQueryData**, are examples of messages that include a //javascript code// or a //sql query//:\\ \\ {{ :en:librarymanagement1.png?direct&500 |}}\\ \\ {{ :en:librarymanagement2.png?direct&500 |}}\\ \\ |
| ====Library Management Page==== | ====Library Management Page==== | ||
| Line 895: | Line 917: | ||
| In this screen we can create, catalogue, edit and browse library elements:\\ \\ {{ :en:librarymanagement4.png?direct&600 |}}\\ \\ | In this screen we can create, catalogue, edit and browse library elements:\\ \\ {{ :en:librarymanagement4.png?direct&600 |}}\\ \\ | ||
| + | In the following we will see each of the different functionalities of the screen. | ||
| Line 917: | Line 939: | ||
| {{:en:librarymanagementicono_limpar_filtros.png?direct&20|}} Click on the "Clear filters" button when you want to clear the fields and reset them to their initial state.\\ \\ | {{:en:librarymanagementicono_limpar_filtros.png?direct&20|}} Click on the "Clear filters" button when you want to clear the fields and reset them to their initial state.\\ \\ | ||
| + | |||
| ==Table or Results list== | ==Table or Results list== | ||
| Line 925: | Line 948: | ||
| {{:en:librarymagementicono_content_preview.png?direct&40|}} By clicking on the "eye" icon, it expands a preview of the item's content, as well as the last user who edited it:\\ \\ | {{:en:librarymagementicono_content_preview.png?direct&40|}} By clicking on the "eye" icon, it expands a preview of the item's content, as well as the last user who edited it:\\ \\ | ||
| {{ :en:librarymanagement10.png?direct&400 |}}\\ \\ | {{ :en:librarymanagement10.png?direct&400 |}}\\ \\ | ||
| - | {{:en:librarymanagementicono_content_preview2.png?direct&50|}} Click on the icon again to collapse the preview.\\ \\ 3. **Actions** column:\\ \\ | + | {{:en:librarymanagementicono_content_preview2.png?direct&40|}} Click on the icon again to collapse the preview.\\ \\ 3. **Actions** column:\\ \\ |
| {{ :en:librarymanagement11.png?direct&100 |}}\\ \\ | {{ :en:librarymanagement11.png?direct&100 |}}\\ \\ | ||
| Line 936: | Line 959: | ||
| ==Edit the content of a library item== | ==Edit the content of a library item== | ||
| - | {{:en:librarymanagement14.png?direct&40|}} Clicking on the **Edit content** button in the Actions column takes you directly to the code editor, where the user can modify the javascript or sql code of the item and save it again. This action also checks that no other user is editing the content of the item at the same time.\\ \\ {{ :en:librarymanagement15.png?direct&400 |}}\\ \\ | + | {{:en:librarymanagement14.png?direct&40|}} Clicking on the **Edit content** button in the Actions column takes you directly to the code editor, where the user can modify the javascript or sql code of the item and save it again. This action also checks that no other user is editing the content of the item at the same time.\\ \\ {{ :en:librarymanagement15.png?direct&600 |}}\\ \\ |
| Line 952: | Line 975: | ||
| ===Accessing Library Management from Modeling=== | ===Accessing Library Management from Modeling=== | ||
| - | If you are modeling a diagram and need to browse the Javascript/Sql code in the libraries, you can do it in two ways: | + | If you are modeling a diagram and need to browse the Javascript/Sql code in the libraries, you can do it in two ways:\\ |
| - | Manually | + | |
| - | By opening a new TAST tab in your browser, where you will open the Library Management screen. | + | |
| - | Automatically | + | |
| - | + | ||
| - | Clicking the Open Library Management button from the Modeling Javascript/Sql code editing window will automatically launch the Library Management page in a new tab of your browser. | + | |
| - | + | ||
| - | + | ==Manually== | |
| - | + | By opening a new TAST tab in your browser, where you will open the **Library Management** screen.\\ | |
| + | |||
| + | ==Automatically== | ||
| + | {{:en:librarymanagement20.png?direct&100|}} Clicking the **Open Library Management** button from the //Modeling Javascript/Sql code editing window// will automatically launch the Library Management page in a new tab of your browser.\\ \\ {{ :en:librarymanagement21.png?direct&500 |}}{{ :en:librarymanagementflecha.png?direct&40 |}} {{ :en:librarymanagement22.png?direct&500 |}}\\ \\ Note: Remember that the Javascript/Sql code editing window appears in Modeling when editing code in messages such as **executeJavascript**, or **dbGetQueryData**, for example.\\ \\ | ||
| - | Note: Remember that the Javascript/Sql code editing window appears in Modeling when editing code in messages such as executeJavascript, or dbGetQueryData, for example. | ||
| ===Saving Javascript/ Sql code from Modeling in a library=== | ===Saving Javascript/ Sql code from Modeling in a library=== | ||
| - | If you are modeling a diagram and want to save in a library the javascript/query sql code used in a given message, you can do it in two ways: | + | If you are modeling a diagram and want to save in a library the javascript/query sql code used in a given message, you can do it in two ways:\\ |
| ==Manually== | ==Manually== | ||
| - | In the //Library Management// screen the user will create a new item, then copy the Modeling code and finally **paste** it into the Contents field of the new library item. | + | In the //Library Management// screen the user will create a new item, then copy the Modeling code and finally **paste** it into the Contents field of the new library item.\\ |
| ==Automatically== | ==Automatically== | ||
| - | {{:en:librarymanagement23.png?direct&100|}} Clicking the **Create new library item** button from the //Modeling Javascript/Sql code editing// window, which will automatically launch the Library Management page in a new tab of your browser, with the **Create new library item** form open and with the Domain, Project, Type and Content fields already filled in.\\ \\ {{ :en:librarymanagement24.png?direct&600 |}}\\ {{ :en:librarymanagementflecha.png?direct&40 |}}\\ {{ :en:librarymanagement24.png?direct&600 |}} | + | {{:en:librarymanagement23.png?direct&100|}} Clicking the **Create new library item** button from the //Modeling Javascript/Sql code editing window//, which will automatically launch the Library Management page in a new tab of your browser, with the **Create new library item** form open and with the Domain, Project, Type and Content fields already filled in.\\ \\ {{ :en:librarymanagement24.png?direct&500 |}}\\ {{ :en:librarymanagementflecha.png?direct&40 |}}\\ {{ :en:librarymanagement25.png?direct&500 |}}\\ \\ |
| - | |||
| - | |||
| - | |||
| - | |||
| ===Retrieve Javascript/Sql code from a library for use in Modeling=== | ===Retrieve Javascript/Sql code from a library for use in Modeling=== | ||
| Line 983: | Line 998: | ||
| When a user is modeling a diagram and editing the javascript or sql code of a message, and would like to bring the code from one of the libraries, this is the way:\\ | When a user is modeling a diagram and editing the javascript or sql code of a message, and would like to bring the code from one of the libraries, this is the way:\\ | ||
| | | ||
| - | 1. Open the //Library Management// screen in a new tab of your browser and locate the desired code, then **copy** the code,\\ \\ 2. and simply **paste** the code into the //Modeling Javascript/Sql// code editing window. | + | 1. Open the //Library Management// screen in a new tab of your browser and locate the desired code, then **copy** the code,\\ \\ 2. and simply **paste** the code into the //Modeling Javascript/Sql// code editing window.\\ \\ {{ :en:librarymanagement26.png?direct&500 |}}\\ {{ :en:librarymanagementflecha.png?direct&40 |}}\\ {{ :en:librarymanagement27.png?direct&500 |}} |
| - | + | ||
| - | {{ :en:librarymanagement26.png?direct&500 |}}\\ {{ :en:librarymanagementflecha.png?direct&40 |}}\\ {{ :en:librarymanagement27.png?direct&500 |}} | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
modeling_2.0.1730890144.txt.gz · Last modified: 2024/11/06 10:49 by montse
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
