PLEASE NOTE: THIS RELEASE REPLACES 15/5/2007 RELEASE. THE 15/5/2007 RELEASE DID NOT CONTAIN THE LATEST QAF TEMPLATE VERSION - WHOOPS!
NEW FEATURE: FIELD PUSH alpha
This feature automatically pushes fields to response documents when the value(s) change in the parent. The operation is triggered Post-Save and is executed on the server. Each field is pushed only if it's value has changed AND an item with the same name already exists in the response.
This tool only works for Notes response hierarchies. The obvious extension is to support the definition of relationships between the source document and documents that should inherit data. (eg based on formulas and view lookups) - this should appear in a future release. Field Push configuration is available at the workflow level (new link on QAF Desigher "Field Push").
CHANGES TO SCRIPT LIBRARY: QAF WF API
wfGetAllStates() function - new parameter optActualNextStatesOnly. When true, only the states actually in use by workflow actions (Next State) are retrieved, as opposed to all defined States for the workflow + Global States.
wfConsistencyCheck() function - logic improved (see Help/About in QAF template for details). This function is used to repair erroneous Waiting On information and to otherwise 'contrive' Waiting On information based on the document's Status.
AGENT: APPCOORD TOOLS \ WORKFLOW CHANGE STATUS
This agent now only displays statuses that are actually used by Workflow Actions relevant to the selected documents. Previously all defined States were shown (of the related workflow) + Global States.
VERSIONING
Beyond version 1.1 Alpha, version numbers are changed from an incremental numbering scheme to a date (design last modified date). The terms Alpha and Beta now appear in forms/ dialogs of new features that are in progress.
Alpha and Beta are defined as follows:
Alpha: Experimental new feature in early stages. Probably buggy; untested.
Beta: New feature that is settled in terms of function, and reaching maturity in terms of reliability.