UI Action does not save record

[George P]

I am attempting to create a UI Action to extend the Valid To date on a published Knowledge Article without going through the checkout/approval process.  The intent is to use a UI Action button to prompt the user for a new date, update the value, and save the record.  I have created the button and when I use it as myself it works as expected.  However, the published articles are read-only for the users who need to make the change and the action does not complete for them.  It prompts as expected, updates the form with the new value so it looked correct, but it does not save the change.

I cannot copy the code as it is on a system with no internet access.  But the basic functionality is that I used GlideModal renderWithContent to display a prompt with date input, pass the date to a takeAction function to update the forma nd save the record.

My thought on how to get past this is to pass the new date value to a server side function within the UI Action, but is that doable?  Any other suggestions?  I would like to keep this simple as I am only updating a single value.

[bammar]

This is probably a security issue or there is a conflicting Business rule.  If these articles are read only then it is security- fundamentally what these users are mimicing is them actually just going to date field and editing it without a UI action- if they dont have access to write on that field then that explains it.  You may have to create a role that is allowed to extend the date field only and grant that role access to take that action.

[George P · Accepted solution]

This was the right direction.  Turns out there is a property called allow minor edits that must be set to true.  Another property allows setting which fields are minor.  Then finally I needed to follow the ACL down through the script includes until I got to the canWrite function of the kbVersioningSNC script and override that function to determine who was allowed to perform the minor edits.