| Outage handler should retain all processed outage IDs | Once an outage has been processed, the outage handler removes it from its databases. However, because of the intricacies of IPC through the cloud and other things that can go wrong (e.g. the drive filling and killing off the pipes collector), sometimes the fact that the outage has been processed doesn’t make it back to other processes that care about it (i.e. TagController and Pi Pipes Collector) and they can be left with the impression that an outage hasn’t been sent or processed |
| Fusion Pi Data Accuracy | Fusion now handles Refresh, Delete and Update messages from PI |
| Search function ResultSearchLimit | Fusion ADX Search function could take a long time to return results if the search term is only a few characters long. Reducing the ResultSearchLimit improves performance of the function |
| TagController returns 400 Bad Request | A 400 Bad Request is returned on any HTTP request that requires authentication. TagController now returns an appropriate code and json |
| ModelReader | This occurs specifically if model reader is asked to read a PI AF model with an element one of whose attributes: references a malformed tag such that accessing the tag’s name through PI AF SDK throws an exception OR the tag the attribute references exists on a server that has not been configured in model reader |
| Azure Identity Security Vulnerability | Possibly exploit of elevated privliges against the file system. See here for more info |
| Fusion UI SSRF Security Vulnerability | An Open Source package (axios) used in the Fusion UI allows SSRF via unexpected behavior where requests for path relative URLs get processed as protocol relative URLs. See here for more info |