in employee interface table with "tblProperties" id should be presented in any part of detail_* form, hidden or not,
in analyst interface properties loads into div with id "propertyDiv".
So I think that you can simply remove original properties inputs,
then create <table id="tblProperties"> for employee and <div id="propertyDiv"> for analyst and place them anywhere on form.
This should work otherwise you need to modify js to prevent property generating.
Using the employee interface, I hadn't thought of that! (shame on me...) I will do some tests here and post the results here. Thanks!
Did that work for you?
From that time I had implemented something like this in our env,
here is 2 screenshots how it looks in Read Mode and Edit Mode.
To achieve this I used xx_prop_include.htmpl which is includable version of xx_prop_tab,
form is universal and could be included in chg/iss/cr forms,
also I modified load_properties form, all above were attached to this post.
Notice: this is not ready solution because it may include customized methods like:
- lookup properties;
- date properties;
- russian traslation;
- other custom functions;
if you want use this method works, you should remove them.
Code to include tab:
<PDM_INCLUDE FILE=xx_prop_include.htmpl z_cols=0 z_factory=$args.producer_id>
If someone interested in this, I'll try to make normal instruction how to implement this.
Thank you. Yes, this is a common request for customization when having the Properties displayed 'at first glance' is more important than trying to limit the vertical scroll on the detail form through the use of nested tabs.