Migrating from Earlier Versions : Clean and Validate the Project, and Correct Validation Errors

Clean and Validate the Project, and Correct Validation Errors
Clean and Validate the Project
After you import the 3.x project into BusinessEvents Studio Explorer, do the following:
1.
Highlight the project name in BusinessEvents Studio and select Project > Clean. At the Clean dialog, click Clean projects selected below, and then select the imported project. Click OK.
All build problems and built states are discarded. The project is rebuilt from scratch.
2.
You may see some common validation errors that are addressed in the following sections. If you see additional errors that you can’t resolve, contact your TIBCO representative for assistance.
After you clean and validate the project, and correct any errors, see Other Post Import Actions for the next step.
Ambiguous Reference Errors (Unqualified References)
During migration, duplicate name references can cause issues. If the project contains unqualified references to rules, rule functions, or ontology types, and any of the rules, rule functions, or ontology types have the same simple name, duplicate name validation errors will result.
Error
In the BusinessEvents Studio Problems tab, you see listings for these issues, such as the following:
Ambiguous reference. Reference must be qualified, as multiple elements exist with the same name [/sharedResources/Element, Rules/Element, Concepts/Element]
One source of this issue is that in the 4.x product, rules are separate resources and in the 3.x product, they exist within ruleset resources.
To Resolve the Issue
To resolve the situation fully qualify all such ambiguous references.
XSLT Mapper Errors
If you have used the XPath (XSLT) mapper in TIBCO Designer, there could be errors that prevent a clean validation of the project after it is imported.
In 3.x, XSLT Mapper errors were not reported during project validation. This validation has been added to 4.0. Therefore, any mapper errors must be fixed before project validation can be successful. These errors existed in the 3.x product, though they may not have caused any runtime problems.
To Resolve the Issue
To fix the problem, In BusinessEvents Studio double-click those items in the Problems view. The rule editor displays the corresponding rule or rule function. In the editor. Check for red error indicators on lines containing function mapping. Where you see an error indicator on a line containing Mapper code, Ctrl-click the underlined argument text to open the Function Argument Mapper dialog. Click the Mapper Check and Repair (check-mark icon) button.
Some errors can be auto-fixed: Click the validate option (the check mark) in the mapper. You see the Mapper Check and Repair dialog. Select the items you want to fix and click OK. (Using auto-fix is harmless even if the errors can’t be auto-fixed.) Then manually fix any errors that can’t be autofixed. For example, errors such as undefined variable errors can’t be fixed automatically.
Use of Words Now in Reserved Word List
As BusinessEvents develops, the number of reserved words increases. Validation shows errors for use of keywords as identifiers.
For the current list of reserved words, check the section Keywords and Other Reserved Words in Chapter 17, Rule Language Grammar, of TIBCO BusinessEvents Developer’s Guide.
Error
Reserved keyword, cannot be used as an identifier
Action
If you use any of the listed words as identifiers, resource names, or folder names, change them in your 4.x project