[19.0][MIG] document_page_mgmtsystem: Migration to 19.0 - #854
Conversation
|
@etobella I created various manuals (other than quality) and they don't show up in the Manuals menu. |
max3903
left a comment
There was a problem hiding this comment.
The Quality Manual category shows up in the Manuals menu.
|
@etobella Both issues remain:
|
|
@max3903 I think both problems are solved |
|
@etobella Still some issues: #854 (comment) |
|
Can you give the steps that you did in runboat to have the issues? A video might work too |
The new issue is related to the category being set by default when creating a new manual and the fact that the content is not updated when the category is changed (missing onchange). |
|
@etobella The Manuals menu opens all the manuals. Search panel allows to filter based on the Quality, Environment, etc. Having separate menu items for each does not make sense. Most organizations would have only one record in each menu. |
|
In this case, we should think about if we really nead enviromental Manuals category at all. |
|
If we want them to be shown as Quality manuals, we just need to remove environment_manual and use |
|
@etobella We need it to provide the structure of the environment manual from ISO 14001. Categories are templates and hold the default content for the pages. |
|
Yes, but with the new change, you can do it yourself without using a module to configure it. For this reason I am saying that I would recommend to remove it in 20. Obviously, I will not recommend that approach in 19. |
… it can be handled with quality_manual
|
@etobella I am not sure users will prefer entering all the content. I think they will appreciate having the template being provided. |
|
Well, that is something that we can decide from a PSC perspective on the migration. IMO, it would be better to have templates to upload on the system and not depend on unnecessary modules. At the end, we are just pushing data and in my experience, we are just adding a few categories and every company might have their own way for doing that. |



Applies changes from #756 to 19.0
I added a smart detection of migration to allow migration from 18 to 19 without executing the scripts.
@FernandoRomera @max3903