.

NET & VB Symbols co-existing in the same part class

Contents
Introduction .................................................................................................................................................. 2
Check error messages and the behavior of .NET symbols first................................................................. 2
Add .NET Parts to a part class already having VB parts. ........................................................................... 3
Results Summary........................................................................................................................................... 4
Miscellaneous Test Cases.......................................................................................................................... 6
Conclusion ..................................................................................................................................................... 6
Troubleshooting Tips .................................................................................................................................... 6
 Introduction
The scope of this document is to test if VB Symbols and .NET Symbols can co-exist in the same part class
or not. Testing includes both when the user has given the correct inputs and when the user doesn’t give
the correct inputs for the parts. However, testing does not include modifying the existing parts from VB
to .NET symbols or vice-versa as we do not support modifying existing parts in an on-going project.
Apart from this, the existing behavior cases of how a Symbol handles the input arguments is also tested.

Check error messages and the behavior of .NET symbols first.

Before proceeding to add .NET symbols to the part classes that are having the VB parts, we need to first
understand the errors with the .NET symbols. So, we will test the errors with .NET symbols and if they
are expected and fine, then we will proceed further. The below are the two test cases:

Case1) Test modifying the Symbol at the part class level.

NET Symbols had Symbol def by default defined both at the part class level and at the part level.

AMD Bulkload: Modify Symbol Def at the part class level and make it NULL.

Case2) Error messages when the attributes are set to NULL values for .NET symbols.

AMD Bulkload: Modify the .NET required attributes at the part level and make them NULL.

Workflow common to the 2 cases listed above: Place few objects, Bulkload with the needed
modifications specified in the test case. Place new objects again and modify the existing objects.

Results for these two cases: The results are expected and are behaving in the same way as VB symbols.
Surface
S.N Blind Reduc Weldole Stock Valve Mount
Test Case Valve Elbow Flange
o Flange er t Instruments Operators Compone
nts
1 Check error messages and the behavior of .NET symbols first.
Remove Symbol
Definition on the Part
1.1 Pass Pass Pass Pass Pass Pass Pass Pass Pass
class and place the
object
 Failed to
place
No Placed
Error but no Error Placed with Placed
Remove the values Error mandator with Error
Updatin error updatin random with
1.2 for required attributes Updating y random Updating
g messag g values. Bad random
and place the object Symbol dimensio dimensi symbol
Symbol e is symbol graphics values
nal value ons
displaye
d

Add .NET Parts to a part class already having VB parts.

Once we get to know the errors that occur in the .NET symbols, then we will proceed to adding the .NET
symbols to the VB symbols.

The input arguments between VB and .NET are not changed for some of the part classes. For example,
most of valves (Check valve, Gate valve, Globe valve etc) are having FaceToFace dimension in both VB
and .NET symbols. However, in some cases, the input arguments have changed, for example in reducing
tee, the Face2ToCenter is changed to Face3ToCenter in OOTB .NET version of the symbols. In such cases,
we need to test if there is any dependency between the VB and the .NET symbol input arguments.
Ideally, the software should take its required/optional attributes and ignore the other attributes (if they
are NULL or even these other attributes have some values). These test cases are listed below.

Test Cases:

Case1) When input arguments are NOT changed between the VB and .NET symbol (Check valve – Face
to Face attribute for example as explained above).
 Workflow: Place such objects with VB symbols (Symbol Def to be at the Part level, not at the part class
level). Modify Ref data and add few .NET parts. Test both the VB and .NET parts placement. Here we
have 3 cases:

Using such parts, test the below cases:

Sym Required Attributes (VB New extra attributes in Pass/Fail Comments

Type & .NET is same) .NET
VB Giving correct values NULL Should work
VB Giving correct values Giving some values Should work as it should
ignore the new extra
attributes.
.NET Giving correct values NULL Just check for any errors

Case2) When the input arguments are changed between the VB and .NET symbol (Reducing Tee for
example as discussed above).

a. Give the correct and required Symbol attribute values for .NET and VB parts and NULL values for
the optional attributes. In our “Reducing flange” example discussed above,
 .NET part: Give correct Face3toCenter dimension and a NULL value for Face2toCenter.
 VB Part: Give correct Face2toCenter dimension and a NULL value for Face3toCenter

Similarly we have other cases where we give some correct/incorrect values for Required attributes and
NULL or giving some values for the other/optional attributes. The below are the cases.

Sym Required Attributes Required Attributes New extra Pass/Fail Comments

Type for .NET for VB symbol attributes
.NET Giving correct NULL Giving correct Should ignore the VB
values values symbol attributes.
.NET Giving correct Giving some values Giving correct Should ignore the VB
values values symbol attributes.
VB Giving some values Giving correct Giving some Should ignore the .NET
values values symbol attributes.

Test all the above cases with different object types like Valve, Elbow, Flange, BlindFlange, Reducers,
Olets (Weldolet), Stock Instruments, Valve operators, Surface Mount Components etc.

Test dataset used: Madison Plant.

V2016 Build: 11.00.82.2203.

Results Summary
Surface
S.N Blind Reduc Weldole Stock Valve Mount
Test Case Valve Elbow Flange
o Flange er t Instruments Operators Compone
nts
1 Check error messages and the behavior of .NET symbols first.
 Remove Symbol
Definition on the Part
1.1 Pass Pass Pass Pass Pass Pass Pass Pass Pass
class and place the
object
Failed to
place
No Placed
Error but no Error Placed with Placed
Remove the values Error mandator with Error
Updatin error updatin random with
1.2 for required attributes Updating y random Updating
g messag g values. Bad random
and place the object Symbol dimensio dimensi symbol
Symbol e is symbol graphics values
nal value ons
displaye
d
2 VB & .NET Symbol attributes are same and .NET symbols have some new extra attributes.
No
No extra
No extra No extra extra
attribute
attributes attributes attribut
s
es

Symbol Type: VB
Required Attributes:
2.1 Giving correct Pass Pass Pass Pass Pass Pass Pass Pass Pass
values
New extra attributes
in .NET: NULL
Symbol Type: VB
Required Attributes:
Giving correct
2.2 values Pass Pass Pass Pass Pass Pass Pass Pass Pass
New extra attributes
in .NET: Giving
some values.
Symbol Type: .NET
Required Attributes:
Giving correct
2.3 Pass Pass Pass Pass Pass Pass Pass Pass Pass
values
New extra attributes
in .NET: NULL.

Reducin Instrume
Union
g Tee nt
3 VB & .NET Symbol attributes are different and .NET symbols have some new extra attributes.

Symbol Type: .NET

Required Attributes:
3.1 Giving correct Pass Pass Pass
values
New extra attributes
in .NET: NULL
Symbol Type: .NET
Required Attributes:
Giving correct
3.2 values Pass Pass Pass
New extra attributes
in .NET: Giving
some values.
Symbol Type: VB
3.3 Required Attributes: Pass Pass Pass
Giving some values
New extra attributes
in .NET: Giving
correct values.

Miscellaneous Test Cases

1) Placement of a .NET Symbol when Generic data missing – Working fine. The errors shown in the log
are same for both VB and the .NET symbols.

2) For the same commodity code if the Schedule is varying and user defined one part with a VB symbol
and the other with a .NET symbol – Working fine

Conclusion
We can use the VB and .NET parts with in the same part class even if the Symbol attributes are different
for VB and .NET.

Troubleshooting Tips
If adding the new parts doesn’t work for you, then the below troubleshooting tip may help you to check
if there are any issues with your Catalog data preparation for the new .NET symbols as described above:

1) Add “M” before part class to create the new .Net attributes under the part class.
2) Verify that all the Occurrence attributes are added in the catalog sheets (including the
dependent sheets like Valve operator sheets in case of Valves).
3) Verify that the generic data for the new parts is added correctly.
4) Check for the catalog data of new parts that are added in the new .Net symbols (specifically Part
data basis).
5) Verify that the new attributes are added in the custom interfaces sheet with the correct
interfaces.
6) Remove the symbol definition at part class level.
7) Symbols with incorrect inputs: If the values (required or optional) are either defined incorrectly
at the Symbol level, then the Symbol placement will fail in some cases. In some cases
unexpected results occur and these will not be detected by the software. These have to be
detected manually. Examples are given below:
The below CR exists to report the missing values for such similar issues.

CR-CP-160798 Check valve symbol can be placed using the symbol inputs.