joesinger12 / TestTicketTransfer

0 stars 0 forks source link

IfValidAnd() and potentially LocalCompAssigned() enhancements #18

Open joesinger12 opened 9 years ago

joesinger12 commented 9 years ago

Originally created by: da...@360-analytics.com Originally owned by: scriswel...@gmail.com

IfValidAnd() function, has an issue when encountering undefined data at more than one indirection.  An example rule where the function is used in this context is:

RULE TrmlUnit:InducedAirZnRef   ...   CHECKSIM   ...   if( IfValidAnd( InducedAirZnRef:Name = ZnServedRef:RetPlenumZnRef:Name ) )   then ...

if RetPlenumZnRef is UNDEFINED, the function returns an error indicating the arguments on both sides are not the same datatype.

Also, this may already be the case, but it would be ideal if the LocalCompAssigned() function could be used ensure a component is assigned for any of the object ref properties if multiple indirections are used.  For example it would be ideal if:

LocalCompAssigned( ZnServedRef:RetPlenumZnRef:... )

returns FALSE if no object is assigned to ZnServedRef, RetPlenumZnRef, etc. This may already be the case, but I have not tested.

What version of CBECC-NRes are you using? On what operating system? [r3014]+.

Please provide any additional information below.

Reported by: joesinger12

Original Ticket: cbecc-com/tickets/926

joesinger12 commented 9 years ago

Originally posted by: nka...@archenergy.com

Was this resolved in v3b if not please tag it for Milestone-v3c

Cc: rhedr...@archenergy.com nka...@archenergy.com

Original comment by: joesinger12

joesinger12 commented 8 years ago

Diff:

Original comment by: joesinger12

joesinger12 commented 8 years ago

Issue is now listed on Ticket 1758 with link to this ticket for details.

Original comment by: joesinger12

joesinger12 commented 7 years ago

Original comment by: joesinger12

joesinger12 commented 7 years ago

Original comment by: joesinger12

joesinger12 commented 7 years ago

Original comment by: joesinger12

joesinger12 commented 7 years ago

Moving to next release as per team discussion on2/28/2017

Original comment by: joesinger12

joesinger12 commented 6 years ago

Original comment by: joesinger12

joesinger12 commented 1 year ago

Original comment by: joesinger12