How to define a default value for a custom Property in DCO ?

[aashraf]

Hi,

In DCO / Configure Custom Properties, We configured some custom properties and defined them as a List with the possible values for the drop-down list, Also some of these custom properties are defined to be mandatory.

But when we add these custom properties to a data center item, It 's possible to leave them as a blank (without choosing any value from the drop-down list) which may be occurred as a human error.

So, the question is

Is it possible to define a default value for these custom properties? And How?

Thanks,

Ahmed Ashraf

[Jef]

Hi Ahmed,

A default value cannot be set beforehand, user may need to define/set it. As illustrated when using the configured mandatory custom properties, if you do not set the value the notification may say "Mandatory custom property xxx should be set":

However, if you have many devices that need to modelled and you need to set some sort of default properties settings, then you might want to set it in Genomes.

Kind regards,

Jef

[aashraf]

Hi Jef,

Yes, I got this notification, But if you click OK without setting the value it will proceed without any issue.

 And actually I have a lot of data center modeled items (more than 2000), and I added the custom property to a template which is already deployed for these data center items, But it's deployed without any value (As a blank field).

So it's not applicable now to add it to a genome.

The conclusion is,

There is no way to set a default value for the custom property and the custom property value (as per the above setup) should be set manually for each individual data center item, Is this right?

Thanks,

Ahmed Ashraf

[Jef · Accepted solution]

Hi Ahmed,

That's correct, there is no way to set a default value for the customer property and the custom property value - it should be manually set for each data center item.
However, I think it might make sense that for the mandatory custom preproteins software should force you to select a value otherwise the "OK" button should not be enabled. I will capture this as a useful product feedback (for our future plans), thanks.

Kind regards