Validation for the generic create component works the same way as the web form component (emxForm.jsp). See Validating Form Field Data for more information. Validation files can be specified in the emxAPPNAME.properties file, where APPNAME is the ENOVIA product name (for example, emxEngineeringCentral.properties). Use this property to specify the name of the validation file: emxAPPNAME.UIForm.Create.ValidationFile=filename where filename is the js or jsp file that executes the validation. The validation file must be stored in the corresponding application directory, such as ematrix\engineeringcentral. If a jsp file is defined, it cannot contain any <script> tags. In addition, enter the method name as the value for the Validate setting on the webform field. The system looks in the properties file for the application defined by the Registered Suite setting on the command that calls emxCreate.jsp to determine which validation file to use. For example, if the Registered Suite=Components setting was set on the command that calls emxCreate.jsp, you could have this property set in emxComponents.properties: emxComponents.UIForm.Create.ValidationFile=createValidate.jsp and the createValidate.jsp must be stored in the ematrix\components directory. If validation methods from more than one ENOVIA product need to be used on a single create form, all methods/files must be stored in the same directory (the one defined by the Registered Suite setting). If validation fails, a message is displayed to the user. If validation passes, the create component makes any required connections. After the object has been created, the value of the submitAction URL parameter determines if:
| |||||||