![](/images/new-backgrounds/1214202/214202389x1.webp)
|
|
| Chapter 3 Working with an XML model | |
| Option |
| Description | |
|
| |||
|
|
|
|
|
| Save generation |
| When selected, PowerDesigner keeps track of the identity of | |
| dependencies |
| each generated object. It is useful when merging two XML | |
|
|
| models which have been generated from the same PDM. | |
|
|
| Objects can be compared and recognized as the same object, | |
|
|
| even if the object has been modified in the merged XML | |
|
|
| model | |
| Convert names |
| When selected, object codes are generated from names using | |
| into codes |
| the corresponding conversion script. This is useful when | |
|
|
| generating models with very different naming conventions. | |
|
|
| With this option selected, both objects will have their codes | |
|
|
| generated from their names. If you do not select this option, | |
|
|
| generated object codes will be copied from original object | |
|
|
| codes | |
| Generate |
| When selected, allows to define the current PDM as the data | |
| mapping |
| source of the generated XML model and to create object | |
|
|
| correspondence between PDM and XML model | |
| Enable |
| This button is used to activate transformations during | |
| transformations |
| generation. When you click this button, the | |
|
|
| appears if the source model contains transformations. You can | |
|
|
| select the transformations to execute before generation. The | |
|
|
| Extended Model Definitions tab also appears for you to select | |
|
|
| extended model definition files to attach to the generated | |
|
|
| model. These files may contain | |
|
|
| transformations, in this case, the | |
|
|
| to let you select the transformations you want to be executed | |
|
|
| in the generated model. If the generation is an update, and the | |
|
|
| generated model contains extended model definitions with | |
|
|
| ||
|
|
| automatically appears as soon as you click the Enable | |
|
|
| Transformations button | |
| Generate |
| When selected, columns in the PDM tables are generated as | |
| columns as |
| child elements (instead of attributes) in the XML model. You | |
| elements |
| can then set attributes to these child elements | |
|
|
|
|
|
For more information on conversion scripts, see chapter Managing Models in the General Features Guide.
Check model before generation
If you select the Check model option, the procedure to generate an XML model starts by checking the validity of the PDM. An XML model results when no errors are found. You can set check options by selecting Tools→Check Model.
XSM User's Guide | 183 |