Custom Properties are custom fields which can hold up to 8,000 characters of text. They can be associated with:
Custom Properties can be used to capture metadata associated with these Objects.
When a Custom Property is defined in a URL for an Object, that Custom Property becomes available to all objects of that type in that URL. For example, if a Custom Property of “Version” is added for Fields in the URL then all Field objects will have a Version Custom Property which can be edited in the Form editor.
The Show in Lists attribute controls whether the Custom Property is shown in object lists. This allows Form and Field Custom Properties to be displayed alongside other attributes of those objects such as Name and OID.
Custom Property values related to Forms, Fields and Drafts are exported from TrialGrid in the Architect Loader Spreadsheet in an TG_<objectname>Properties sheet (e.g. TG_FieldProperties) and can also be imported into Drafts in TrialGrid where the Architect Loader Spreadsheet has those worksheets.
The TrialGrid Architect Loader Spreadsheet upload process will not import properties for Draft Objects where the URL does not have a property of that name defined. For example, if the Architect Loader Spreadsheet contains a PropertyName of “DOMAIN” for Fields then these properties will only be imported if “DOMAIN” is defined as a property in the TrialGrid URL. If there is no property of that name the property value will be ignored with a warning during the Architect Loader Spreadsheet upload.
Medidata Rave cannot import Custom Property sheets, it ignores these worksheets in any Architect Loader Spreadsheet uploaded into Architect.