6 Let's consider a YACS schema containing Block, FOR loop and inline script nodes with data ports.
8 The first step is to import the schema from YACS XML file. One of the ways for the user to do it is to click on the **Import schema** button on the :ref:`schema` and choose **YACS XML** item from the pull-down list. Let's open legendre7.xml from YACS_SRC/src/gui directory.
10 After import operation, arrangement of the schema nodes and **Fit All** operation we have the following state of Salome 4.1 application.
14 .. image:: images/functionality_list_98.jpg
19 **The result of legendre7.xml import**
22 For more convenient view of a schema representation in 2D Viewer the user can rebuild schemas' links with help of **Rebuild links** command from :ref:`visualization`. The result will be the following.
26 .. image:: images/functionality_list_99.jpg
31 **Representation of a schema after rebuild links operation**
34 To change input value of the schemas' node it is needed to select this node either in schema 2D Viewer or in the Tree View of a schema. And after that change input ports values with help of corresponding controls on the property page of the selected node. But in our case, if we want to execute a body of the **loopiter** node 5 times we have to change the **nsteps** output port value of **init**
35 node from 3 to 5 with help of its property page, and press "Apply" button on the Input Panel schema 2D Viewer.
38 .. image:: images/functionality_list_100.jpg
44 **Property page of init node**
47 In order to execute this schema the user should to create a run of the schema with help of **New execution** button on the :ref:`execution_toolbar`. After a new schema run has been created, schema run Tree View is constructed and schema run object is published in the Object Browser.
50 .. image:: images/functionality_list_101.jpg
56 **Object Browser content and schema run Tree View**
59 If the user selects schema object in the Tree View, Input Panel with schema property page will occur. Errors raised during create execution process is shown in the 'Error Log' list box of schema property page in the run mode. In our case there are no errors occured during creation of execution.
62 .. image:: images/functionality_list_102.jpg
68 **Schema property page in the run mode**
71 To use :ref:`breakpoints run mode <breakpoints_mode>` it is sufficient for the user to set breakpoints on nodes using check boxes in the run Tree View. Let's set one breakpoint - on **iter2** node inside **deuxIter** block.
74 .. image:: images/functionality_list_103.jpg
80 **Set breakpoint in run Tree View**
83 Start execution with help of **Start/Resume** button on :ref:`execution_toolbar` in run mode. Execution is paused on the **iter2** node inside **deuxIter** block. The run Tree View displays states of nodes.
86 .. image:: images/functionality_list_104.jpg
92 **Run Tree View of paused schema**
95 Now try to save execution state of the schema by clicking :ref:`save_restore_execution_state` button on :ref:`execution_toolbar`. Save the current state of execution into /tmp/legendre7_exec_state.xml file.
99 .. image:: images/functionality_list_105.jpg
104 **Save the current execution state of legendre7.xml schema**
107 Now execute the schema using **Start/Resume** button until the execution of the schema is finished, making sure that **loopiter** node had been executed 5 times.
110 .. image:: images/functionality_list_106.jpg
116 **Execution of legendre7.xml schema is finished**
119 The user can check values of output ports with help of 'Output ports' table on the propertty page of a node.
122 .. image:: images/functionality_list_107.jpg
128 **Output port values of iter_1 node**
131 Let's try to load saved execution state of legendre7.xml schema. After this operation run Tree View should be in the same state as at the moment of saving execution state.
134 .. image:: images/functionality_list_108.jpg
140 **Run Tree View after load execution state**
143 Continue execution of the schema from the saved state and check values of output ports when execution is finished. They should be the same as obtained earlier during the first execution.