Placeholders for every fields

[Nicolas Micoud]

Hi,

Placeholders were recently added for range process parameters.
I think that could be useful for every field, process param, info window criteria, ...

Idea would be to add a 'Placeholder' column in :
 AD_Element
 AD_Element_Trl
 AD_Field
 AD_Field_Trl
 AD_InfoColumn
 AD_InfoColumn_Trl
 AD_Process_Para
 AD_Process_Para_Trl

And then adapt components classes (WStringEditor, WTableDirEditor ...) to set the placeholder (if defined) (at the end of the init() method).
The SynchronizeTerminology process should also be updated to take care of those columns.

We also need to add specific message for some panels (eg. location panel with Address1Placeholder, Address2Placeholder, ... PostalPlaceholder, ...)

WDYT ?

Regards,

Nicolas

[Carlos Antonio Ruiz Gómez]

Hi Nicolas, that sounds like a good idea.

two comments:

- when we add to AD_Field we need to think if is worthy also to add it to AD_UserDef_Field - in this case I think it can be good to add such possibility

- message for Address1Placeholder ... PostalPlaceholder ... I think it won't work as the message can be different per country, maybe adding those placeholders to country and country_trl would solve that case

Regards,

Carlos Ruiz

[Nicolas Micoud]

I'm starting to work on the subject.
I will add field to AD_UserDef_Field table.

For the specific message, adding fields to C_Country won't work for SaaS environnment.
So, i would suggest to use SysConfig instead. Name of the key would be something like PC_LOC_<CountryID>_Add1, PC_LOC_<CountryID>_Add2, PC_LOC_<CountryID>_Postal, ...

WDYT ?

Nicolas

[Carlos Antonio Ruiz Gomez]

Hi Nicolas,

> For the specific message, adding fields to C_Country won't work for SaaS environnment.

I think country definition is on top of tenant.
In principle I would say a tenant cannot override what is defined on a country level.

But anyways, if you think this is a strong need - I think you could change the WLocation* class to search for a field name change in field tenant customization (AD_UserDef_Field) for the Location window, if not defined, then use the country defined.

Regards,

Carlos Ruiz

--

[Nicolas Micoud]

Yes, using AD_UserDef_Field for location window will do the trick !

Another question... for Range process parameter ; should we allow to override "standard" placeholder (means adding a AD_Process_Para_PlaceholderTo column).
Or unique message is enough ?

[Carlos Antonio Ruiz Gomez]

AD_Process_Para_PlaceholderTo sounds fine

[Nicolas Micoud]

ok thanks

[Nicolas Micoud]

Is almost done !

Just struggling with the list of region on the Location Dialog. It doesn't support placeholder.
(note that Country also doesn't support but as it is mandatory, it would be never shown).

So i would propose to let a TODO in the WLocationDialog so maybe one day the Listbox could be updated to a WTableDirEditor and then, the placeholder could be set.

WDYT?

Nicolas

[Carlos Antonio Ruiz Gomez]

Yes, it sounds fine

[Nicolas Micoud]

Jira created : https://idempiere.atlassian.net/browse/IDEMPIERE-3639

[Satish Vijayan]

I got an error on pack-in - it said something along the lines of 'ad_process_para.placeholder' not found.

I guess we need to run migration scripts on the DB to rectify?