Allow fields to be marked as read-only (no edits)

[GoogleCodeExporter]

When creating a document that is both used standalone as well as in a package, 
we find we have to create two flavors.  First, we create the document to be 
fully filled out (standalone).  Then we create another version in which some of 
the fields are no longer editable by a party because values are set from prior 
documents in the package.

This is a common need, such as the I-9, where the employee name, SSN and 
address, for example, are filled out by the employee when it's standalone, but 
inside an onboarding application, those values come from the job application 
itself -- or some other "info sheet" where common fields are entered and then 
pre-filled on subsequent forms.

Original issue reported on code.google.com by yoz...@gmail.com on 13 Apr 2013 at 10:44

[GoogleCodeExporter]

Allow a field to be marked as non-updatable by subsequent parties on the SET 
VALUE action. This allows a document to have some fields set from other fields 
(or transaction initial data from a POST) and then converted into non-editable 
fields.

This way, the document can be marked as having editable fields for standalone 
purposes, but when in a package, those fields can be pre-filled and then locked 
from further changes.

Original comment by yoz...@gmail.com on 16 Apr 2013 at 6:35

• Changed state: Started
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Fixed in release 13.5.5 as part of the SET FIELD VALUE action for custom logic 
in a document or package (mostly this would be used in a package, which is the 
component that knows that a given document can be pre-filled from other docs in 
the package.

Original comment by yoz...@gmail.com on 16 Apr 2013 at 9:53

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****