15 May
2015
15 May
'15
2:39 p.m.
On 14/05/2015 19:27, denis wrote:
To prevent this situation getting any worse is, I believe, a one line fix in the software. Adding this MNTNER name to a list of MNTNERs kept in the software that users cannot directly reference will: -prevent any new direct reference being made in user's objects -force users to replace it with their own MNTNER if they want to update an object that has a reference to this MNTNER -have no impact on the intended use for hierarchical authorisaton
I can't imagine anyone not agreeing with this, so if we get a few +1s the NCC can implement this in the next software release.
sounds good to me. Nick