Updating / Saving
A Knowledge Base's changes are in progress until the Save action is undertaken via the button in the top-right of the screen.
General Behavior
On Save, several actions will occur:
1. Connection is Retested
As a failsafe, the connection is retested in case the form has changed between saves and tests or to flag an intermittence issue. If the connection fails, the user will be asked to confirm if they want to progress forward with a faulty connection.
2. Validations are Checked
Items like Tables and Fields have validations — the system checks if they exist and can be evaluated. In case of failed validations (e.g., a Field no longer maps correctly to its source) then the UI will similarly flag to the user if they are comfortable proceeding.
Knowledge Base "Locks"
To prevent multiple Contributors in a Knowledge Base from overwriting one another's changes, "locks" are applied to manage edit state.
When a Knowledge Base is not being actively editted by any individual, the first Contributor to select Edit will place a "lock" on the Knowledge Base. This "lock" is effective until the Contributor cancels, saves, closes the window, or times out (~ 2 hours). While the "lock" is in place, the Edit button is grayed-out for all other Contributors.
You can check the user who has placed the "lock" by hovering over the grayed-out Edit button, which will indicate their name. Once the lock is removed, the Edit button will turn blue once again.
Last updated
Was this helpful?