View Issue Details

IDProjectCategoryView StatusLast Update
000550810000-014: PubSubSpecpublic2023-06-22 18:12
ReporterMatthias Damm Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status acknowledgedResolutionopen 
Summary0005508: AccessLevel (writer capability) undefined for TargetVariables
Description

If a Variable is selected as FieldTargetDataType.targetNodeId it is currently undefined if this changes the access level of this variable or what should happen if the variable is used for more than once as target variable or if a client writes to the Variable

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008339 acknowledged 10000-003: Address Space Features needed for locking functionality 

Activities

Georg Biehler

2020-03-10 14:12

reporter   ~0011740

FLC's expectation isd:

  • if a variable is selected as target variable, and if the SubscribedDataSet the target variable is assigned to is referenced by a enabled DataSetReader, the variable is set to read-only for any access, excluding the DataSetReader.
  • If a variable is selected as target variable by multiple SubscribedDataSets, only one of them may be referenced by an enabled DataSetReader.

Matthias Damm

2020-12-10 14:54

developer   ~0013444

Last edited: 2021-03-05 12:29

Writing the requirement to the spec is easy. But we need to come up with some generic functionality that can be implemented in base libraries to avoid that every implementer of a Write needs to have special logic.

Option for indicating "locked" state would be

  • Use reserverd AccessLevel bit 7 for 'Locked'
  • Introduce new attribute like AccessLevel for Methods or a general solution for all node classes

[Edit based on discussion on January 19, 2021]
It would be much easier to use the AccessRestrictions for a new 'Locked' flag. This attribute is available for all NodeClasses.
We can still reflect the locked state in the UserAccessLevel.
Discuss in next meeting
[Edit end]

Indication of who is locking is necessesary - reference to the locking object (DataSetReader, Lock) may be a good solution.

Matthias Damm

2021-03-05 13:48

developer   ~0013987

Discussion in UA WG Meeting:
There is an agreement that adding a IsLocked flag to the AccessRestrictions is the right way to indicate the locking state on a node.
For Methods the flag would influence the UserExecutable Attribute.
For Variables the flag would influence the UserAccessLevel Attribute.

Open Issue:
How is the information provided about the owner of a lock.

Matthias Damm

2021-06-11 08:15

developer   ~0014549

We need the locked state also for the PubSub configuration objects managed by a FX connection. These objects cannot be modified through the PubSub API

Paul Hunkar

2022-09-21 20:49

developer   ~0017777

discussed in UA meeting - see new related issue for results.

Issue History

Date Modified Username Field Change
2020-03-06 15:36 Matthias Damm New Issue
2020-03-10 14:12 Georg Biehler Note Added: 0011740
2020-05-19 16:59 Jim Luth Assigned To => Matthias Damm
2020-05-19 16:59 Jim Luth Status new => assigned
2020-12-10 14:54 Matthias Damm Note Added: 0013444
2021-01-19 18:10 Matthias Damm Note Edited: 0013444
2021-01-19 18:11 Matthias Damm Note Edited: 0013444
2021-03-05 12:29 Matthias Damm Note Edited: 0013444
2021-03-05 13:48 Matthias Damm Note Added: 0013987
2021-06-11 08:15 Matthias Damm Note Added: 0014549
2021-10-26 16:30 Jim Luth Target Version => 1.05.02
2022-07-05 14:17 Jim Luth Target Version 1.05.02 => 1.05.03 RC1
2022-09-20 21:49 Matthias Damm Relationship added related to 0008339
2022-09-21 20:49 Paul Hunkar Note Added: 0017777
2023-06-22 18:11 Matthias Damm Target Version 1.05.03 RC1 =>
2023-06-22 18:12 Matthias Damm Assigned To Matthias Damm =>
2023-06-22 18:12 Matthias Damm Status assigned => acknowledged