View Issue Details

IDProjectCategoryView StatusLast Update
0009659Part 81: UAFX Connecting Devices and Information ModelSpecpublic2024-09-10 13:51
ReporterJan Murzyn Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityN/A
Status closedResolutionno change required 
Product Version1.00.02 
Summary0009659: Additional check needed for VerifyAssetCmd
Description

By doing asset verification as part of EstablishConnection, it’s implied that the AssetToVerify shall be related to that AutomationComponent on which the EstablishConnection is called. However, this is not explicitly required by the specification. In theory, an id of any asset existing in the Server, even from outside of the AC can be passed.

Proposal:
Add in Table 10, in the description of Bad_InvalidArgument the same phrase as already exists for FunctionalEntity in Table 11: “[...], or not related to the AutomationComponent on which EstablishConnections was called.”

TagsNo tags attached.

Activities

Paul Hunkar

2024-08-27 04:41

manager   ~0021623

Checking the existence of the Asset in the AC is not needed and potentially a very expensive operation. The Asset could be owned by more then one AC, if there are multiple AC in a server. It is only important that it is an Asset (has the correct required interfaces - and thus the correct required variables)

Paul Hunkar

2024-08-29 03:27

manager   ~0021639

The text does not imply and the error code states in the server - so no change is required (it can be any asset)

Paul Hunkar

2024-09-10 13:51

manager   ~0021690

discussed in call agreed no change required

Issue History

Date Modified Username Field Change
2024-07-12 06:36 Jan Murzyn New Issue
2024-07-12 06:36 Jan Murzyn File Added: image.png
2024-07-12 06:36 Jan Murzyn File Added: image-2.png
2024-07-20 06:05 Paul Hunkar Assigned To => Paul Hunkar
2024-07-20 06:05 Paul Hunkar Status new => assigned
2024-08-27 03:48 Paul Hunkar File Deleted: image.png
2024-08-27 03:49 Paul Hunkar File Deleted: image-2.png
2024-08-27 04:41 Paul Hunkar Note Added: 0021623
2024-08-29 03:27 Paul Hunkar Status assigned => resolved
2024-08-29 03:27 Paul Hunkar Resolution open => no change required
2024-08-29 03:27 Paul Hunkar Note Added: 0021639
2024-09-10 13:51 Paul Hunkar Status resolved => closed
2024-09-10 13:51 Paul Hunkar Note Added: 0021690