Updating Configurations
It is usually necessary to restart components that enaio® webclient accesses after making changes to configurations. Users must also reload enaio® webclient in the browser.
enaio® applications |
Changes |
Necessary actions |
---|---|---|
enaio® editor |
Change to the object definition:
|
Restart the 'dms' microservice. |
enaio® editor / enaio® administrator |
Add new object types and grant access rights. |
Restart the 'dms' microservice. Reload enaio® webclient with F5. If the technical user is still in use, then the 'osweb' microservice must also be restarted. |
enaio® administrator |
Change of access rights to existing object types. |
Reload enaio® webclient with F5. If the technical user is still in use, then the 'osweb' microservice must also be restarted. |
enaio® administrator |
Change/add clauses for access rights. |
Changes apply immediately after saving them in enaio® administrator. |
enaio® administrator |
Change of users' system roles. |
Restart enaio® appconnector. |
enaio® administrator |
Change to the user management:
|
Restart enaio® appconnector. |
enaio® editor-for-workflow |
Change to the workflow organization:
|
Restart enaio® appconnector. |
AD synchronizations |
Update to the user administration and workflow organization. |
Restart enaio® appconnector. |
enaio® editor-for-events / enaio® editor-for-workflow |
Change/add client-side Java Script events. |
Reload enaio® webclient with Shift+F5 |
enaio® webclient Service Release |
Import Service Release of enaio® webclient. |
Restart the 'osweb' microservice. Reload enaio® webclient with Shift+F5. |