Read-Only Field Behavior

enabling and disabling read only fields is a flexible feature within swimlane turbine you set up read only fields from within application builder or within workflow within application builder, you set up a read only field by clicking a checkbox in the field properties in workflow, you can either enable a read only field, or disable an existing read only field when you add playbook actions, or use python driver, and api, the read only fields can continue to be manipulated here are some scenarios that show you how read only fields behave scenario 1 in this scenario, the read only field is built into the application in application builder the application has a field that is set to read only, for example, a date & time field the table below describes how that field behaves when encountered by a user or through workflow, and also when updated via apis, or playbooks user (within a record) workflow python driver restful api task api unable to edit the field field is editable not editable (you receive a read only error message ) editable editable scenario 2 in the second scenario, the read only field is created by workflow in this example, a condition is set up that if a record's severity field is set to critical, then the reported by field is set to read only (the field is not originally) once the workflow executes, the field is editable or not editable as seen in this table user (within a record) workflow python driver restful api task api unable to edit the field editable (if workflow is also set up to set the field value) editable editable editable