Hi,
I was not aware of this addition. It is clear that having these UIDs it
will be simpler to check if the archetype has changed, as you say. But is
it also the intention of these UIDs to be used to fill the archetype_id
attributes in the RM instances? Or the link between the instance and an
On 18/11/2014 12:50, David Moner wrote:
Hi,
I was not aware of this addition. It is clear that having these UIDs
it will be simpler to check if the archetype has changed, as you say.
But is it also the intention of these UIDs to be used to fill the
archetype_id attributes in the RM
I can see the point now. I couldn't understand the benefits of the new UID
attributes.
It is OK if they become mandatory in 2.0. We just have to have clear rules
to know when a new instance_id has to be created.
2014-11-18 14:31 GMT+01:00 Thomas Beale thomas.beale at oceaninformatics.com:
On
On 18/11/2014 12:50, David Moner wrote:
Hi,
I was not aware of this addition. It is clear that having these UIDs
it will be simpler to check if the archetype has changed, as you say.
But is it also the intention of these UIDs to be used to fill the
archetype_id attributes in the RM
4 matches
Mail list logo
