Hi HomerJ,
The following code is provided as is and is use and test at your own discretion and usage is not supported further:
1) Enter the Customization module section for you project
2) Add your desired user field to the Module Section within the User Fields section of the Project Entities (take note of the user field for example TC_USER_01 and not the displayed name that you used)
3) Save that addition (this can be done for basically any module needing the customization)
4) Enter the Workflow editor section on the left of the Customization Section.
5) Navigate to the Module Section and expand it
6) Add the following code (adjusting for your module, in this example I used the Test Lab module and the TestSetTest_MoveTo actions for adding to the Test Instances Details displayed from the Test Lab):
TestSetTest_Fields.Field(''TC_USER_01'').PageNo = 1 (substitute your user field noted above and add the number for the page/tab you would like to be displayed on Page 0 is the Details page so use 0 only if you want it displayed on the details page which is unnecessary as it displays there by default)
7) If the GetDetailsPageName routine already exists within that sections details, then select it and proceed to add the code, otherwise if it doesn't exists then select the Module Script header by clicking on it.
8) Scroll to the bottom of the routines list on the right side screen and add the following code:
Function GetDetailsPageName(PageName, PageNum)
Select Case PageNum
Case 2
GetDetailsPageName = ''Custom Tab1'' (substitute your desired page/tab name here)
End Select
End Function
Any tab you would like to rename can be added here within the case statement as well (say you wanted to rename the Details tab, not recommended, it would be:
Case 1
GetDetailsPageName = ''New Tab Name''
and any other tab would be such:
Case (page number)
GetDetailsPageName = ''Desired tab name''
(you can also accomplish this by adding code to the CommonScripts GetDetailsPageNumber detailed here: http://eyeontesting.com/questions/10183/tab-names-in-the-test-instance-details-window.html )
9) Save the workflow code and the syntax checker will check and determine if the code is correctly syntax formatted.
10) Exit out of Customization and test your changes.
This same code procedure can be used for basically any of the modules to create and display the modules information as desired.
The above has been tested and works as desired, but it is use and support at your own risks so make sure to test and insure it does what you are desiring and I would make sure you have current saved backups prior to making and changes in the workflow.
I hope you find this helpful,
Dan