You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
OSCM 17.4.
Provisioning Service based on APP (Powershell)
When using user "cmgt-business" and subcribing to a service (HyperV), the UI change from "Get it Now" to the configuration dialog takes 2 seconds which is very good.
When using the user "cmgt-it" (who is in the supplier organization) and subcribing to the same service (HyperV) the change from "Get it Now" to the configuration dialog takes about 180 seconds which is too long.
Please investigate
The text was updated successfully, but these errors were encountered:
Checking the data from both users the cause gets clear.
In opposite to "cmgt-business" the user “ctmg-it” has defined a Create Subscription trigger. This trigger is not correctly configured, respectively the URL points to a location where either no notification service is deployed or this service is not functional.
There are about 130 trigger processes and it takes time to read them from DB. This is a rather special case than a general performance bug.
Solution is to remove the failed trigger processes.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
OSCM 17.4.
Provisioning Service based on APP (Powershell)
When using user "cmgt-business" and subcribing to a service (HyperV), the UI change from "Get it Now" to the configuration dialog takes 2 seconds which is very good.
When using the user "cmgt-it" (who is in the supplier organization) and subcribing to the same service (HyperV) the change from "Get it Now" to the configuration dialog takes about 180 seconds which is too long.
Please investigate
The text was updated successfully, but these errors were encountered: