Properties/Configuration page

[Yvan1]

I'm trying to create a sort of properties/configuration page for admins, I understand how to create a Module page containing all the properties of a particular Property Category type using the URL (from Arguments) Link Type; but what I'm really looking for is a mix of fields types so I can populate those properties, some choice fields, a few reference fields, and of course string fields; but without having to create a whole custom table, ha anyone had any luck with that approach?

[Bert_c1]

You need to provide more details on your goal so you may get some useful responses. I'm having trouble understanding what you're looking for.

10-tips-for-writing-a-quality-community-question

[Yvan1]

Take for example the Email Properties (email_properties.do), it contains properties for configuring email.

I'm looking to try doing that, but with reference fields as well. Since you can't make a record reference type Property, I'm looking to make module page that can display the Properties that I need a user to reference/edit as well as reference fields that will populate other properties that are hidden.

[Bert_c1]

From what I see, 'email_properties' are showing records from the sys_properties table applicable to email functionality. Names that start with 'glide.email, glide.pop3, glide.smtp, ...  I can not see any value in providing another means to create/update those records.

I suspect I don't understand your goal. If you have your own "properties" to use, create a table for those and develop modules to provide users to 'reference/edit' those. You can create Reference fields on other tables that reference your "properties" table.

If you create record in the sys_properties table, I suppose you can build a module and UI components for those. Like the one with title: Email Properties in the sys_app_module table that uses email_properties.do (proprietary code).  

[Yvan1]

I'm really only using the email_properties.do as an example that is present across all instances of ServiceNow.

Since I can't create properties that act the same as reference fields, my thought was to create a UI page similar to email_properties.do, have a reference field on there that when changed would update a corresponding property via business rule or an on submit rule.

Most of what I had seen in the community suggested I would need to create a table and use its record type that store/reflect the information in my properties. It seems you're confirming it's not possible without creating a table to store that information.