Changes in the system

Changes come in deliberately

Opero's configuration does not change by accident. The administrator works on a draft version no one but them sees, and a change becomes visible only at the moment of publication. Thanks to this, it does not happen that a field disappears while you are filling in a form because someone is just moving it.

A practical consequence: between requesting a change and its appearing in the system there is a moment when the change already exists but does not yet work. This is a normal stage of the work, not a forgotten request.

What to do after a change is deployed

If you had the system open at the moment of publication, refresh the page. A screen built before the change still shows the previous version of the layout.

A configuration change does not touch data. Moving a field on a form, adding a section, or changing a name does not change the records' contents.

Problems after a version change

Report it to the administrator as specifically as possible: what you did, what you expected, and what happened. Previous versions of the layouts are kept, so returning to the state before the change is usually quick.

Example. After a change to the ticket form, two fields swapped places and the team started getting confused. A report and the publication of a corrected version the same day were enough, without waiting for a system update.

What publication does not cover

• Permissions. A new layout does not grant access to data that was not visible before.
• Records' history. Saved values and history entries stay untouched.
• Numbering. Assigned numbers remain as they were.