Modeling Studio should block removing of TQL if is in use from some integration

Idea ID 1765392

Modeling Studio should block removing of TQL if is in use from some integration

Verified in 2018.08

If integration  had TQL, and this TQL is  removed from modelling studio, UCMDB server fail to restart.

After  a restart of uCMDB doesn't start with  error in the error.log / wrapper.log:
ERROR [Starter for "data-acquisition" (during Writer server startup). (customer 1, id name: Default Client)] (CustomerController.java:531) - Failed to start component [data-acquisition]
appilog.framework.shared.manage.impl.MamResponseException: [ErrorCode [-2147483648] undefined error code]

UI should return error and block removing of TQL

4 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

Micro Focus Expert
Micro Focus Expert
Status changed to: Under Consideration

We are looking into this as a future product enhancement. Check the notifications box to be emailed if the status changes.

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

I hope this idea will be implemented soon.

Micro Focus Expert
Micro Focus Expert
Status changed to: Accepted

Great news, this idea has been accepted on our product roadmap. Subscribe to receive updates. (This is not a formal commitment, and subject to change)

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.