Clarity

Hi guys,

Clarity 13.1

1- Create a static lookup (code) with these values:
Id = one / Value: 1
Id = two / Value: 2
Id = three / Value: 3

2- go to project object / attributes tab
3 - create new attribute calling the above lookup with default value 1
4 - add custom attribute to create / edit view
5 - enable audit trail for custom attribute
6 - create new project and remain the default value (1)
7 - in edit view change value from 1 to 2 / save
8 - check audit trail old value in the first time appears as NULL

What do you think?
Thanks

Screenshot


.

Thanks Martti.

In the first record old value = null / new value = 1

I thought that first record would be
Old value = 1 / new value = 1

Because in the attribute definition value by default = 1

Martti

What do you think?
Normal behavior?

I don't know.
I'll try to have a look at it on v13.0.
It may depend on when exactly the default value get populated.


Martti K.

My test environment is 13.1

In this moment I dont access to another environment therefore I dont know if this behavior occurs also in previous versions
Thanks

Well if you are that picky. v13.0 would have been just starting another VMWare guest, but for v13.1 I have to start another host first. ;-)

Martti K.

I think that on Monday I'll can test using 13.0.1 / 12.1.2
My finding will be posted

Thanks

...and the answer is no.

Clarity 13.1

1- Create a static lookup (code) with these values:
Id = one / Value: 1
Id = two / Value: 2
Id = three / Value: 3

2- go to project object / attributes tab
3 - create new attribute calling the above lookup with default value 1 - The attibute name = Test_juan
4 - add custom attribute to create / edit view
5 - enable audit trail for custom attribute
6 - create new project and remain the default value (1) - The project name = Test_juan

odf_ca_project custom attribute gets populated
Audit trail show new value for test attribute

7 - in edit view change value from 1 to 2 / save
8 - check audit trail old value in the first time appears as NULL

[color=#fc0000]The old values does not appear as NULL but 1 as it should[color]

Martti K.


.

Thanks Martti

Reviewing your screenshot (audit trail), the first record old value appears as NULL (at least in UI).

The second screenshot the second record ID = 500009 in RAW_VALUE_BEFORE = NULL

So, do you think that this is a bug?

Regards,
Juan

No because I was watching also odf_ca_project and as soon as the project is created the value of the attribute get populated.
My audit trial was set to catch insert as well.
When the new project is created the attribute is populated and it did not exist before that so there should not be any old value.


Martti K.

Thanks Martti, so when you assigned 1 as default value in the attribute definition, the assigned value (1) is not reflected in odf_ca_project table?

The above sentence anyway sounds strange, because if you assigned a default value I would expect that in odf_ca_project was with my default value (1).

Regards

I think that this sentence is not true, when you assigns a default value in the attribute, the value is populated in odf_ca_project table

I perfomed the following

1 - create custom attribute nicolas (data type = string) / default value = hello
2 - add the attribute in both views (create / edit)
3 - enable audit trail with the above attribute
4 - go to Project / create new Project / save

I checked odf_ca_project according my new Project id = 5****** and the value in my custom attribute (by default) appears in the column,

Now, I changed the value from 'hello' to 'how' and audit trail change new value (hello) by new value (how), a correct a pattern because before there was nothing

Best Regards,
Nico!

Thanks for your time!

I think that this sentence is not true, when you assigns a default value in the attribute, the value is populated in odf_ca_project table

Yes, at least when you do not have checked Populate Null values with defaults that does not happen.
Only for the project where the value is set in the GUI it appears also in ODF_CA_PROJECT while the others have NULL.



Martti K.


.