Basically, I noticed that the ‘Save’ button remains disabled when changing a field of type ng-model. However, if I add a typical cam-variable-name field into the same embedded form, the Save button is enabled on change with this field (cam-variable-name). And, once the save button enable/disable begins working, the ng-model field also begins sending events to enable save on field change.
Here’s the div section for the ng-model field - and, this binds and displays data perfectly… just doesn’t enable the save button if contents change:
<div class="control-group"> <label class="control-label">ng-model: customer.value.firstname</label> <div class="controls"> <input type="text" ng-model="customer.value.firstname" class="form-control" /> </div> </div>
Didn’t see any errors in the console…
My workaround is to use some temporary process variables - using cam-variable-name. And, these fields work simply as temporary place-holders to help workaround the save button enabling issue.
But… is there a patch (if this is a bug) or alternate work-around? I noted a similar issue in JIRA. Initially assumed a code-error on my side. However, I’m following the examples closely (if you notice I even use the ‘customer’ json var).