Releases: MxUpdate/Update
Releases · MxUpdate/Update
V0.07.0: A new version of the MxUpdate Update Deployment Tool is released.
New Features: - With this release workspace objects are support for groups, roles and persons. Workspace objects are cues, filter, tables, tips and views which are individual defined for a user. - Sites are supported from groups and roles. Major Improvements: - MQL programs are handled with the parameters --mqlprogram, --mqlprog or --mql. - All programs (JPO's, MQL programs or pages) could be handled now with the parameters --program or --prog. - Pages are handled also from the --admin or --all parameters. Solved Issues: - issue #38: Suport of workspace objects for roles / groups / persons - issue #65: Persons as Employee from a Company with spaces in the name are exported not correctly - issue #66: Support of sites for roles / groups - issue #67: Update of an hidden role / group / person without defining hidden flag in CI file does not remove hidden flag - issue #69: Pages are not exported if --admin * is exported
V0.06.3: A new version of the MxUpdate Update Deployment Tool is released.
The new version is a bug-fix release for the installation of trigger groups and multiple parent interfaces of an interfaces. Also now page objects are supported. Solved Isses: - issue #24: Support of configuration item "page" - issue #62: The trigger group type is not assigned to the trigger group policy within first installation - issue #63: Update for an interface with multiple parent interfaces failed - issue #64: The description for the trigger group data model must be fetched from the property file
V0.06.2: A new version of the MxUpdate Update Deployment Tool is released.
The new version is a bug-fix release that the update for MQL programs without file extension works. Bug-Fixes: - issue #60: MQL program without extension could not be updated - issue #61: Typo in the logging text for JPOs
V0.06.1: A new version of the MxUpdate Update Deployment Tool is released.
The new version includes some bug-fixes belonging inquiry updates on windows and the new directory structure for JPO and MQL programs (now in program/jpo and program/mql). Bug-Fixes: - issue #45: Compile the installed MxUpdate JPOs with force update - issue #55: If no code for an inquiry is defined the embedded inquiry code must be also a zero length text - issue #56: Update of an inquiry failed under Windows - issue #57: JPO and MQL programs must be located in directory program with sub directory JPO and MQL
V0.06.0: A new version of the MxUpdate Update Deployment Tool is released.
The new version includes some minor bug-fixes belonging special character handling and installation of the downloaded version. Improved: - issue #51: Possibility to reference Wiki pages in the parameter definition needed Bug-Fixes: - issue #47: Installation of downloaded MxUpdate failed - issue #52: Special characters must be removed from calculated symbolic names - issue #53: Configuration Items with double quotes gets wrong file names - issue #54: Use escaped MQL commands within TCL update file
V0.05.2: A new version of the MxUpdate Update Deployment Tool is released.
This is only a minor change belonging the installation of MxUpdate Update: - issue #46: Simplify the JPO installation routine
V0.05.1: A new version of the MxUpdate Update Deployment Tool is released.
Improved support for MX V6: - issue #14: Interfaces must support relationships Bug-Fixes: - issue #33: Symbolic names of states must be exported only as symbolicName within policyUpdate definition - issue #34: Support of multiple symbolic names for states of policies - issue #36: Export and Update of methods for types is supported - issue #39: Interfaces are not exported for type definition groups admin and data model
V0.05.0: A new version of the MxUpdate Update Deployment Tool is released.
Improved support for MX V6: - issue #5: Dimension must be supported to export / update - issue #27: Assigned default applications of Persons will not be exported and not removed if updated Bug-Fixes: - issue #22: Programs and JPOs are not registered with symbolic names - issue #26: JPOs with Packages are not exported correctly - issue #28: Policies with properties without name could not be updated - issue #29: Policy Definitions with states without symbolic names gets empty properties - issue #30: Policy with all types assigned are not exported correct - issue #32: MxUpdate Update Programs must be registered with a symbolic name
V0.04.0: A new version of the MxUpdate Update deployment tool is released.
Improvements: - issue #18: Post-Update Script for Programs could be also defined within Source Code - issue #21: New parameter added to compile JPOs automatically