Module : Custom Properties
Issue |
Type |
TrialGrid Version |
Description |
---|---|---|---|
3977 |
Feature |
72 |
Custom properties can now be made inactive to retire them from future entry and display. |
3982 |
Feature |
72 |
When custom properties are excluded from draft compares, custom objects are now also excluded. |
3976 |
Bug |
72 |
When updating a custom object definition the external name could be left blank which would result in a blank worksheet name in ALS exports for that object type. This would make the spreadsheet unreadable. This was corrected. |
3953 |
Feature |
71 |
Custom properties set for HTML editing cannot contain javascript script tags. |
3952 |
Feature |
71 |
Custom properties set for HTML editing now have an HTML editor in editor views. |
3900 |
Feature |
69 |
Custom properties with a type of Text can now be set as having HTML content. If set the html content is rendered in listings and spreadsheet views. Some html tags are not supported for rendering, see help on custom properties for details. |
3911 |
Feature |
69 |
The list of Custom Properties defined for a URL can be filtered by object type, including custom object definitions. |
3795 |
Feature |
67 |
Custom object definitions are now included in the spreadsheet export of URL settings. |
3797 |
Feature |
67 |
When creating a url, custom object definitions are now included in settings copied from another url. |
3750 |
Feature |
66 |
When creating a custom object it is now possible to choose from the available icons. |
3752 |
Feature |
66 |
When creating or updating a custom object it is now possible to choose the separator for the parts of the custom object identifier. |
3757 |
Feature |
66 |
It is now possible to choose which custom properties are concatenated to create the identifier for an instance of a custom object. These identifiers are used in standards compliance matching to library objects. |
3720 |
Feature |
65 |
Custom properties can now be defined for Test Cases. |
3721 |
Feature |
65 |
The Test Case list will display custom properties. |
3722 |
Feature |
65 |
It is now possible to edit custom properties for a Test Case in the Test Case editor, on the metadata tab. |
3723 |
Feature |
65 |
Custom properties are available for data collection in Actions for Test Cases. |
3724 |
Feature |
65 |
Custom properties will be copied when Test Cases are copied from one Draft to another. |
3606 |
Feature |
61 |
Custom Objects can now be copied between drafts using the Import button from the custom objects list. |
3585 |
Feature |
61 |
Custom Objects can now be copied between drafts from the draft compare page. |
3574 |
Bug |
60 |
Drafts with custom properties could not be cloned and showed an error when cloning was attempted. This was corrected. |
3572 |
Bug |
60 |
When editing a custom property definition for a custom object, the changes could not be saved if another custom object had a custom property of the same name. This was corrected. |
3548 |
Feature |
59 |
When downloading an ALS there is now an option to include custom objects in the download if any have been defined for the URL. |
3549 |
Feature |
59 |
Custom objects will now be imported from ALS files if present and the custom object definitions appear in the URL. |
3550 |
Bug |
59 |
Invalid values for custom properties are now ignored on import with a warning given that the value is not being imported. |
3533 |
Feature |
58 |
The custom property definition listing page was loading slowly in some cases due to calculating in-use counts. Usage counts are now shown on the custom property edit page and when requesting to delete a custom property. |
3427 |
Bug |
55 |
When creating a draft from a library, custom properties which were set not to copy were being copied. This was corrected. |
3377 |
Feature |
52 |
Custom property definitions can now be set so that copied or cloned objects will not inherit that custom property from the source object. |
3345 |
Feature |
51 |
The Fields list will now only display the Custom Properties column if there are Custom Properties to display. |
3251 |
Feature |
49 |
It is now possible to define custom objects which appear as child objects of Drafts. A custom object can have custom properties defined for it and spreadsheet views. Custom objects can be a convenient way to model simple data that is related to Drafts (IVRS specifications, Report formats etc). |
3143 |
Feature |
47 |
Data dictionary entries can now have custom properties related to them. |
3168 |
Bug |
46.2 |
Some custom properties preserved whitespace at the end of the value. This whitespace is now removed. |
3132 |
Bug |
45.1 |
When cloning a draft, draft custom properties can be left associated with the original draft. This was corrected. |
2970 |
Bug |
43 |
When a custom property was applied to a large number of objects, it could not be deleted from the Custom Property list. This was corrected. |
2971 |
Bug |
43 |
When a Label was applied to a large number of objects it could not be deleted deleted from the Label list without error. This was corrected. |
2773 |
Feature |
39 |
In object comparisons custom properties now appear as additional attributes of objects that they belong to rather than as a separate collection. This makes the compare dialog results much easier to read. |
2475 |
Feature |
32 |
Custom Properties may now be reserved for Actions. This means the custom property values can only be changed via data entry fields related to Actions. |
2481 |
Feature |
32 |
Custom properties defined for Drafts and set to show in lists now appear in their own columns in Draft listings. |
2426 |
Feature |
30 |
Project Custom properties with "show in lists" set to True now appear in their own columns in the Project List View. |
2390 |
Feature |
28 |
When a choice value is removed from a custom property for form fields, any default value in a property sheet that uses that value is removed. |
2391 |
Feature |
28 |
When a custom property for fields is deleted, its input column is removed from all form/field property sheets. |
2343 |
Feature |
27 |
When a custom property is added or removed from Field objects, existing property sheets are updated to add the new property (but not automatically show it) or removed as appropriate. |
2323 |
Bug |
26 |
When Matrices had associated custom properties, copying a Draft failed with an error, this was corrected. |
2241 |
Feature |
23 |
The Custom Properties list can now be filtered by Object type. |
2236 |
Feature |
23 |
It is now possible to copy Project level metadata from one Project to another Project in the same URL. |
2189 |
Bug |
22 |
Tabs can be cut and pasted into Metadata (Custom property) values. This was changed so that tab characters saved in Custom property values are turned into single spaces. |
2193 |
Feature |
22 |
Importing large numbers of custom properties from an ALS was slow. Performance was improved. |
2160 |
Bug |
22 |
When creating a Draft from the Library custom property were compared with case-sensitivity, this caused matches not to be found ("Value" not equal to "VALUE"). This was corrected. |
2119 |
Bug |
21 |
Custom Property Choice values could be uploaded which had different case to their definitions ("TRUE" vs "True"). These custom property values would not display in the object editors and the system would not allow the definitions of these custom properties to be changed. This was corrected. |
2012 |
Feature |
19 |
When creating a new Custom Property, the "Show in Lists" checkbox is no longer checked by default. |
2028 |
Feature |
19 |
If an object editor has a single editor tab (i.e. no Metadata) then then tab navigation for different pages of the Object Editor should not show. |
1858 |
Bug |
16 |
The Form list showed custom property values even when "show in lists" was not set for a custom property. This was corrected. |
1821 |
Feature |
16 |
Custom Properties on objects are now copied as part of the create Draft from Library process. |
1753 |
Bug |
16 |
Custom properties on forms could not be saved without error when Form is matched to a Standard Library (compare fails). This was corrected. |
1608 |
Bug |
16 |
When changing a custom property from a text field to a choice field and there are empty values in the choices list, the system will throw an error. This was corrected. |
1596 |
Feature |
16 |
In the list of custom properties, blank values are not be counted toward the "in use" total. |
1597 |
Feature |
16 |
When editing a Custom Property definition the system now warns if you make a change and try to leave the page without saving. |
1604 |
Feature |
16 |
Custom Properties now have a display order attribute which controls the order in which they are displayed in editors and listings. |
1490 |
Feature |
16 |
Custom Properties can now be defined for Project and Draft objects. |
1525 |
Feature |
16 |
Custom Draft Properties are exported into ALS files and imported from ALS files via the TG_DraftProperties tab. Rave Architect will ignore this tab in the spreadsheet. |
895 |
Feature |
9 |
Users can now Define Custom Properties for Forms and Fields at the URL level. See Help on Properties for more information on this feature. |
2913 |
Feature |
9 |
Custom properties may be deleted from the URL, deleting a custom property definition will remove that custom property from all objects along with any value set. |
896 |
Feature |
9 |
A count of Custom Properties appears on the URL home page. |
897 |
Feature |
9 |
The "Properties" tab for Forms and Fields shows all custom properties defined at the URL level. Values entered for these properties are exported into the ALS and can be re-imported into TrialGrid. Note that Rave ignores these custom properties. |
899 |
Feature |
9 |
Creation of Custom Property Definitions is controlled by a permission at the URL level. |
900 |
Feature |
9 |
Custom property names and values are shown in the listing for the Object to which they are assigned (i.e. the Form or Field listings in the Draft area) |
901 |
Feature |
9 |
Whether a Custom Property is shown in the Object Lists can be controlled by the "Show in Lists" checkbox on the Custom Property Definition at URL level. |
902 |
Feature |
9 |
To avoid confusion with Custom Properties the "Properties" column of the Field and Form lists was renamed to "Summary" since it summarizes key properties of the Form or Field such as Log Direction or whether a field is Log. |