Known Issues (3.3.5)
- Jenni Wallin
In Usage Engine 3.3.5, there are the following known issues:
- 1 Encrypted Workflows Cannot be Viewed in MZOnline
- 2 mzcli Commands Do Not Provide Return Codes
- 3 Removing Dynamic Fields May Cause Problems in the Web Interface
- 4 OpenAPI Validation Error for Type enum
- 5 AWS Terraform Template does not Support M1 Mac with darwin_arm64 Architecture
- 6 Datahub Profiles not shown in Workflow Properties Profile Selection Window
- 7 SAP CC Notification Agent TLS Feature Not Working
Encrypted Workflows Cannot be Viewed in MZOnline
In MZOnline, any encrypted workflows cannot be viewed.
mzcli Commands Do Not Provide Return Codes
If you are using scripted solutions requiring return codes, you must use the mzsh commands, since the mzcli commands do not provide return codes.
Removing Dynamic Fields May Cause Problems in the Web Interface
When having changed fields in the Workflow Properties from being dynamic per workflow to being final, you may have problems running the workflow in the Web Interface.
OpenAPI Validation Error for Type enum
There is a bug when performing OpenAPI validation for parameters of the enum type. The bug is based on: https://bitbucket.org/atlassian/swagger-request-validator/issues/161/mockmvc-openapi-30-type-of-enum-parameter
The error is recorded as:
[Path ‘/requesterPlmn’] Instance type (string) does not match any allowed primitive type (allowed: [“object”])This occurs when you send a request to an NRF server that is configured using our HTTP2 Server agent with OpenAPI validation enabled. You will be meet with a Bad Request error (Error 400) and the validation fails. There was an issue with the specifications for the type enum within the 'anyOf' section as seen from the example below.
Example: NFType found in TS29510_Nnrf_NFManagement.yaml
NFType:
description: NF types known to NRF
anyOf:
- type: string
enum:
- NRF
- UDM
- AMF
- SMF
- AUSF
- NEF
- PCF
- SMSF
- NSSF