In discussion with serverwiz users two key issues were identified:
(1) Finding specific entries/attributes in the tree view of the System MRW was not possible. Users would often have to grep the resulting XML for entries. This also led to users editing the XMLs directly - which was error-prone.
(2) Produced System MRW XML files provided no information about the version of the common-mrw that parts were pulled from. For example, if a consumer of a System MRW identified an error in a part, they would have no idea if that part came from the current common-mrw or if it was outdated. Since a System MRW could have used multiple versions of the common-mrw it becomes almost impossible to track what is happening.
Changes:
(1) A search tab is added to the top of the GUI which allows the user to search inside the tree view for specific part names, part attributes, attribute values. For example, one could search for a part name and then update an attribute value immediately.
(2) When a part is created from the common-mrw, serverwiz will query the git repository for the current commit hash (of the entire repo). This hash is added as metadata to the part and is displayed in the serverwiz GUI.
Parts from MRWs created prior to this change will NOT have a hash in their metadata and serverwiz will not add one. Only new parts add after this change will have a hash.
Because parts can be dependent on multiple files in common-mrw, the decision was made to use the overarching repository hash.
mtvaught-ibm
commented
4 years ago
In discussion with serverwiz users two key issues were identified:
(1) Finding specific entries/attributes in the tree view of the System MRW was not possible. Users would often have to grep the resulting XML for entries. This also led to users editing the XMLs directly - which was error-prone.
(2) Produced System MRW XML files provided no information about the version of the common-mrw that parts were pulled from. For example, if a consumer of a System MRW identified an error in a part, they would have no idea if that part came from the current common-mrw or if it was outdated. Since a System MRW could have used multiple versions of the common-mrw it becomes almost impossible to track what is happening.
Changes: (1) A search tab is added to the top of the GUI which allows the user to search inside the tree view for specific part names, part attributes, attribute values. For example, one could search for a part name and then update an attribute value immediately.
(2) When a part is created from the common-mrw, serverwiz will query the git repository for the current commit hash (of the entire repo). This hash is added as metadata to the part and is displayed in the serverwiz GUI. Parts from MRWs created prior to this change will NOT have a hash in their metadata and serverwiz will not add one. Only new parts add after this change will have a hash. Because parts can be dependent on multiple files in common-mrw, the decision was made to use the overarching repository hash.