Updating / Saving

In beta: Save controls will be updated with "Locks" preventing multiple contributors from concurrently saving and overwriting each others' changes.

A Knowledge Base's changes are in progress until the Save action is undertaken via the button in the top-right of the screen.

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.

If the connection is faulty, the Knowledge Base will not function as intended. You can choose to accept the connection failure if you plan to solve for it later or aware of a pending solve at source. The Knowledge Base will not be restricted from use in the meantime, though users will receive a warning in Chat if the connection is not detected as healthy.

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.

Validation checks should only be ignored similar to the connection if a solve is imminent or known. If there are widespread validation failures the Knowledge Base will not function correctly. The system leaves the decision to the user's discretion to not block saving and to allow waiting for a solve elsewhere.