I don’t understand this Info modeler requirement as I’ve changed the the number of characters in my system for WTDocument and I don’t have it, maybe this requirement refers for PDMLink types such EPM and WTPart…
See the modules I have installed:
See the procedure I’ve used as reference:
Customizing Column Lengths
A column length for a modeled attribute can be customized. These column lengths
are obtained through the wt.introspection package. The value of this
property can be overridden by placing entries in the customizations property file
for modeled packages.
To change the column length for a modeled attribute, perform the following steps:
1. Determine which customization property entry must be added.
2. Add the customization entry to the appropriate customizations property file.
3. Generate the class info objects and SQL scripts.
4. Verify the customization.
5. Create the database tables.
6. Restart the method servers if they were running during the procedure.
The following example sets the column length for the name attribute of the wt.
doc.WTDocumentMaster class to 350. The following steps describe how to
determine which customizations property file entry will contain the new column
length, and how to set the value. The customization will be made in a location
parallel with the originally modeled attribute.
The default location for these customizations is $(wt.home)\wtCustom, as
defined by the wt.generation.custom.dir entry in the tools properties.
Create this directory if it does not already exist.
Note
See the descriptions for the tools.properties and user.properties files in
Property Files on page 35 .
1. Determine which customization property entry must be added:
a. Obtain an info report for the class by executing the following command:
infoReport wt.doc.WTDocumentMaster
b. Inspect the value of the WTIntrospector.UPPER_LIMIT property (the value being customized) of the number PropertyDescriptor:
getValue( WTIntrospector.UPPER_LIMIT ) : 60
c. Inspect the value of the WTIntrospector.DEFINED_AS property of
the number PropertyDescriptor:
getValue( WTIntrospector.DEFINED_AS ) :
wt.doc.WTDocumentMaster.number
Customizing Modeled Elements 1691
d. Based on this information, use the following values:
• The customization property file is <windchill>\wtCustom\wt\
doc\docModel.properties.
• The customization property entry is
"WTDocumentMaster.name.UpperLimit".
2. Add the customization property entry to the appropriate customizations property file. In this example, add the following entry to <windchill>\wtCustom\wt\doc\docModel.properties (create this file if it does not exist):
WTDocumentMaster.number.UpperLimit=64
# ignore multi-byte database character sets when setting value
3. Generate the class info objects and the SQL scripts. Update the serialized info object and the SQL script for the customized class by entering the following command (on one line):
ant -f <windchill>\bin\tools.xml custom_column -Dgen.input=wt.doc
4. Verify the customization:
a. Obtain an info report for the class and inspect the UPPER_LIMIT value asdescribed in the preceding steps. The value should reflect the customization.
b. If the info report value is unchanged, verify that the generate step actually
updated the following serialized info file:
<windchill>\codebase\wt\doc\WTDocumentMaster.ClassInfo.ser
5. Create the database tables, if they don’t already exist, by executing the relevant SQL scripts generated above. If the tables already exist, adjust the length of the customized column by taking the following steps:
a. Execute the Windchill Upgrade Manager to run the Compare Schema step
only.
Start the Windchill Upgrade Manager within a Windchill shell as follows:
• Windows : UpgradeManager
• UNIX : UpgradeManager.sh
• Linux : UpgradeManager.sh
To perform only the Compare Database Schema step, the following commands can be appended to the upgrade manager command for the following purposes: -compareschema|-cs
1692 PTC Windchill ® Customization Guide
For further information about the Windchill Upgrade Manager command options and upgrading data base schema see the following topics in the PTC Windchill Upgrade Guide :
• “Additional Upgrade Manager Commands”
• “Upgrade Database Schema”
b. Inspect the generated output to find the SQL script(s) related to this customization.
Caution
Review the output carefully to ensure the results are what you expect.
You should never execute any SQL that you do not understand, or that does not seem related to your intended customizations
c. Execute the relevant SQL scripts.
In this example, WTDocumentMaster.name is also the source for the derived attribute WTDocument.name. This derived attribute, WTDocument.name, gets its UpperLimit from the source attribute, WTDocumentMaster.name.
A derived attribute cannot set the UpperLimit property in the annotation.
Therefore, the derived attribute cannot be customized in this manner.
Update the value in database:
alter table wtdocumentmaster modify (WTDOCUMENTNUMBER varchar2(64));
SQL> alter table wtdocumentmaster modify (WTDOCUMENTNUMBER varchar2(64));
SQL> commit;
