Module : Actions

Issue	Type	TrialGrid Version	Description
3910	Feature	69	The list of Actions defined for a URL can be filtered by object type, including custom object definitions.
3857	Feature	68	Actions can now be defined for custom objects.
3782	Feature	66	It is now possible to run Actions from object editors.
3703	Bug	63	When an auto-action precondition references a custom property that an object did not have set, the action would fail with an error result on object save. This was corrected.
3668	Bug	63	When saving an object with many auto actions defined there were many repeated database queries which could affect performance. The number of queries was reduced.
3284	Bug	48.2	When saving an edit check with no changes, auto-actions would run. This was corrected.
3149	Bug	47	Performing an action was triggering many database calls. Performance was improved.
3165	Bug	46.2	Actions which collect custom property values did not recalculate object fingerprints. This caused inconsistencies in draft comparisons. This was fixed.
3116	Feature	46	It is now possible to reference custom properties of objects in Actions via
3102	Bug	45	Actions no longer allow a Add Label or Remove Label action for a object type which cannot have that label associated. An error is shown on saving the action.
2984	Feature	43	When Custom Functions have their Source Code changed (ignoring changes to comments), the Auto-actions for Edit Checks and Derivations are run. A new function related_custom_function_changed() can be used in Edit Check and derivation auto actions to determine if a related custom function was changed.
2988	Feature	43	When Matrices have a Folder/Form combination added or removed, the Auto-actions for Edit Checks which have a CheckAction using MergeMatrix, AddMatrix and OldMergeMatrix action types which reference this Matrix will run. The function related_matrix_folders_changed() can be used in Edit Check auto actions to determine if a related matrix was changed.
2931	Bug	41	When saving a data dictionary, auto actions did not run correctly, this was corrected.
2909	Bug	41	When custom properties were set for Draft Objects by Actions, the draft subsequently could not be cloned due to a database error. This was corrected.
2846	Feature	40	In Action preconditions the function compliance_status_is(ALLOWED_CHANGES) returns True if the object has only allowed changes or passed rules. The new function only_allowed_changes() returns True if state is ALLOWED_CHANGES and the count of allowed changes is greater than 0 and the count of rules passed is 0. That is, there are ONLY allowed changes type changes.
2847	Feature	40	In Action preconditions the function compliance_status_is(ALLOWED_CHANGES) returns True if the object has only allowed changes or passed rules. The new function only_rules_passed() returns True if state is ALLOWED_CHANGES and the count of rules passed > 0 and the count of allowed changes is 0. That is, there are ONLY standard rules passed type changes.
2852	Feature	40	In Action preconditions the new function matches_copy_source() returns True if the object is in a draft linked to a library and has been copied from some other object (e.g. another draft) and matches that object precisely (by fingerprint). Otherwise it returns False.
2692	Bug	35	When creating a URL and using settings from another URL Action Operations, associated Roles and Data collection properties were not copied. This was corrected.
2636	Bug	34	When auto-actions were triggered by user actions, the auto-action did not see new labels applied to the object which could then affect its logic. This was corrected.
2635	Feature	34	Action preconditions do not recognize “Smart quotes”. The system now warns if a precondition contains smart quotes. In addition, examples containing smart quotes were removed from the online help.
2598	Feature	34	Actions can now be set as auto-run. This means the action runs automatically on all objects of this type when they are saved, labelled or otherwise changed.
2612	Feature	34	Actions now have an ordinal which affects their display order and the order in which auto-actions run.
2633	Feature	34	Actions cannot be created with duplicated or conflicting add/remove label operations.
2582	Feature	34	The compliance status of objects (e.g. Matched, Different, Not Found etc) can now be checked in Action preconditions.
2571	Feature	34	To make it easier to understand why an object did not meet Action preconditions the Action dialog now displays the parts of the precondition logic with either a check (tick) or a cross to show whether that part of the precondition was evaluated and what its return value was (check=True, cross=False).
2585	Bug	34	When actions are used to collect custom property values the values are not initially set (i.e. only updates were working). This was corrected.
2543	Feature	34	Before actions are executed the action dialog now shows how many objects out of the selected will actually be affected (e.g. 10 selected / 5 applicable)
2544	Feature	34	The action dialog now shows the pre-condition for the action to help users understand why an object cannot have the action applied.
2536	Bug	34	Actions on object listings will sometimes temporarily remove custom property values already shown in the object list. This was corrected.
2517	Feature	33	The Action definition list may now be filtered by related object type.
2491	Feature	32	Actions for Forms are now available in the Form listing.
2492	Feature	32	Actions for Edit Checks are now available in the Edit Check listing.
2493	Feature	32	Actions for Derivations are now available in the Derivation listing.
2494	Feature	32	Actions for Folders are now available in the Folder listing.
2495	Feature	32	Actions for Custom Functions are now available in the Custom Function listing.
2496	Feature	32	Actions for Data Dictionaries are now available in the Data Dictionary listing.
2497	Feature	32	Actions for Unit Dictionaries are now available in the Unit Dictionary listing.
2498	Feature	32	Actions for Matrices are now available in the Matrix listing.
2499	Feature	32	Actions for Test Cases are now available in the Test Case listing.
2452	Feature	32	When entering preconditions for Actions, the preconditions are validated to
2453	Feature	32	When editing an Action if I make a change and try to leave the page I see a warning that I will lose my work if I do not save.
2459	Feature	32	Actions are assigned to Project Roles. This means a user with that Role is able to execute the Action on an object if the pre-conditions are met.
2467	Feature	32	Actions have associated Operations which define the result of applying the Action. This feature defined "AddLabel" and "RemoveLabel" actions.
2469	Feature	32	Actions may now be applied to Projects from the Project listing.
2476	Feature	32	Actions now have related custom properties so that when executing an action data can be collected about that action. For example, marking an Edit Check as Tested can also collect the test date, test subject reference etc.
2478	Feature	32	Actions have an Active/Inactive setting. When Actions are Inactive they are not shown to users in listings.
2480	Feature	32	It is now possible to apply actions to a selection of Drafts from the project Draft List.
2483	Feature	32	Actions cannot be applied to Drafts which are locked.
2485	Feature	32	Actions can now have a precondition which determines whether an object has been approved by a certain Project Role.
2432	Feature	31	There is now a URL permission to manage Actions.
2434	Feature	31	A count of Actions defined appears on the URL home page.
2435	Feature	31	A listing of Actions for the URL is now available from the URL count of Actions navigation link and in the URL-level breadcrumbs.
2437	Feature	31	Users with Manage Actions permission can create and modify Action definitions for a URL.
2443	Feature	31	Labels can now be reserved for Actions. This means users cannot add or remove these Labels, they can only be added or removed through Actions.
2444	Feature	31	When copying settings from a URL Actions are included in the copied settings.