Original Publishing Date: 2023-04-13 Symptoms If you click on Terms & Conditions on the last screen of purchase project, new windows is opened with the details of Terms & Conditions. If you click a link that redirects you to an external page it shows you the message "Can't open file": Cause There is no link set on the html template of the Terms and Conditions. The url is placed between tags but no url is specified in the href part: Resolution There is different solutions on the approach you prefer. Edit the template following the steps: Billing > System > Setting > Terms > Terms and Conditions > select terms to modify > Edit  Then apply the preferred solution:  Add link to external url on the html Template on the following way: Delete tags and let the url as plain text so the customer can copy url and search on the navigator: Delete link as explained in solution 2 and add new paraph with information in plain text you want to show from the external url.

Original Publishing Date: 2023-04-14 Symptoms Customer place Sales Order by API, the subscription takes too long to generate so it retry the API request. After some time two subscriptions are generated in CloudBlue Commerce. Cause Each time Sales Order request is received generates new uispan in the system, then the request is handled as a different request. It can be seen in billing logs.  Example for first order (uispan:9031c019-9640-4056-b035-aac98845c286): [23-04-12 09:03:01.340 billing RQ2673323 TH05881 TRC] [uispan:9031c019-9640-4056-b035-aac98845c286] TRACE START PlaceSalesOrder_API [23-04-12 09:03:01.343 BM_Object RQ2673323 TH05881 NTE] Entering method BM.PlaceSalesOrder_API(user = 2368960, SID = 0, lang = en, request = 2673323, localObject = 0, transaction = 5923575 (HP)) [23-04-12 09:03:01.343 BM_Object RQ2673323 TH05881 NTE] 1 input arguments : [23-04-12 09:03:01.343 BM_Object RQ2673323 TH05881 TRC] +++[0] ItemResult* BM::PlaceSalesOrder_API(Str)(inParams: Example for the second order (uispan:7abd520a-7b9c-4a3d-b4a7-6e531009f33b): [23-04-12 11:03:15.042 billing RQ2681746 TH07625 TRC] [uispan:7abd520a-7b9c-4a3d-b4a7-6e531009f33b] TRACE START PlaceSalesOrder_API [23-04-12 11:03:15.042 BM_Object RQ2681746 TH07625 NTE] Entering method BM.PlaceSalesOrder_API(user = 2368960, SID = 0, lang = en, request = 2681746, localObject = 0, transaction = 5934011 (HP)) [23-04-12 11:03:15.042 BM_Object RQ2681746 TH07625 NTE] 1 input arguments : [23-04-12 11:03:15.043 BM_Object RQ2681746 TH07625 TRC] +++[0] ItemResult* BM::PlaceSalesOrder_API(Str)(inParams: Resolution Do not resubmit API request in case you have not received a failure answer, even if the Order is not created on CloudBlue Commerce. If the request takes too long, please, contact support for further information about its status. In case the "extra" subscription is created it should be cancelled immediately or customer will be charged for two subscriptions. 

Original Publishing Date: 2023-04-18 Symptoms After a microservice has been successfully upgraded, its apsinstance 'Component status' changed to status  'APS Instance upgrade failed' and 'Deployment status' to 'Deployment failures'. In a8n-operator log it shows that the corresponding instance on APS is in APS_INSTANCE_UPGRADE_ERROR: Instance with error on APS, state APS_INSTANCE_UPGRADE_ERROR, you need to apply a manual fix. The corresponding task with name 'Upgrading resources of application 'name of app/microservice''on Task Manager level failed with error: ... '500 Internal Server Error' received from 'POST https://appstore:8081/rest/application/8be9e554-93f9-4a3c-bd24-b94621960cd0/upgrade?version=': I/O error on GET request for "https://jira.int.zone/rest/api/2/search": Connect to jira.int.zone:443 [jira.int.zone/137.117.182.241] failed: Connection timed out; nested exception is org.apache.http.conn.ConnectTimeoutException: Connect to jira.int.zone:443 [jira.int.zone/137.117.182.241] failed: Connection timed out ... Cause The https://jira.int.zone is not whitelisted in the aks cluster. Resolution Add https://jira.int.zone in the aks cluster whitelist.

Original Publishing Date: 2023-03-28 Symptoms In an attempt to do an immediate plan upgrade for subscription to a better SKU, the following message appears in UX1: There are no plans available for an immediate switch, but you can schedule a plan change on subscription auto-renewal. Cause Immediate switch not allowed: Resolution The possibility of doing an immediate plan upgrade to a higher SKU was implemented in the new feature request PFR-5454 and a new version of PLM 1.9.589. Before that, it was not possible due to platform limitations and was allowed during 7 days after renewal only (despite the fact that Microsoft allowed to do it in the middle of the subscription lifecycle). Check you current PLM version and if PPR is uploaded with the correctly filled out PlanSwitchPaths sheet (ImmediateSwitchAllowed should be set as TRUE):

Original Publishing Date: 2023-04-19 Question Due to cybersecurity critical vulnerabilities, customer is asking on how to disable https:\\/auth/ URL Keycloak access for certain brand. Answer Based in the apache configuration documentation Apache Docs,  can be used  to disable any specific URL path pattern. Therefore, tag will need to be used inside the apache configuration file of the requested brands. Resolution 1st: We will need to ssh into the branding-ui pod branding-ui-cluster-ui container container   kubectl exec -ti branding-ui-cluster-ui- -c branding-ui-cluster-ui -- /bin/bash 2nd:  Edit /etc/httpd/brand.conf.d/ https VirtualHost as follow:         ServerName         DocumentRoot /var/www/brands/                         Require all denied                                 ProxyTimeout 300                                 ProxyTimeout ${DEFAULT_PROXY_TIMEOUT}                 SSLEngine on         SSLProxyEngine on 3rd: Restarting the branding-ui pod in branding-ui-cluster-httpd container will also be required: kubectl exec -ti branding-ui-cluster-ui- -c branding-ui-cluster-httpd -- /bin/bash 4rd: To permanently apply these changes customer could export/import the config files so after every pod restart changes could again be applied: kubectl cp branding-ui-cluster-ui-:/etc/httpd/brand.conf.d/   kubectl cp   branding-ui-cluster-ui-:/etc/httpd/brand.conf.d/

Original Publishing Date: 2023-04-18 Symptoms From Usage Reports (Operations > Services > Usage Reports) a customer is trying to upload a usage file to their panel, but it is getting rejected for the following error:  RequestError: Unable to load /aps/2/resources/5b630a03-a278-4cc8-b593-fb4e57227d94/usageReports status: 500 Unsupported Usage Schema value: {QT}. Cause The customer is using VRDM, which is an old implementation it does not support QT schema. Resolution Usage Collector (UC) is the replacement for this implementation and as it is indicated in the documentation shared in the description it does support it but in order to update it from Vendor-rated Data Manager (VRDM) to UC a migration process has to be executed according to the documentation: Migrating from a Vendor-rated Data Manager Based Solution to a Rating Engine Based Solution.

Original Publishing Date: 2023-04-20 Symptoms Based on the current deployment guide for Monitoring and Alerting solution, inside the infra.yaml metric_server_enable setting value can be set to either true or false. In addition it is not mandatory. However, if this setting is set to true, the monitoring deployment will fail with error as below:     metrics_server_enabled: true specified state file infra/monitoring/helmfile.yaml is not found Cause The deployment container image does not have the yaml file for the deployment of the Kubernetes metric server kube-state-metric. Resolution Remove setting metrics_server_enabled from your infra.yaml. Internal

Original Publishing Date: 2023-04-21 Symptoms PPR import has no response at all. No error, notification or summary  is shown at all. At the same time, in the inhouse-product log it is indicated that the import actually failed with exception(s). Cause The issue is caused by software-related issue, OA-31988 "Error message are not displaying in UX1 new experience". Resolution Please contact your Technical Account Manager to clarify the status of the software-related issue. Workaround: Turn off "New Experience" featur on UX1 as below:

Original Publishing Date: 2023-04-28 This article is a container for the migrate_connect_to_pdi.py that is required for the instructions in this section: https://docs.cloudblue.com/cbc/21.0/Product-Lifecycle-Management/Switching-Product-Management.htm.

Original Publishing Date: 2023-05-04 Symptoms There is a difference in the NCE Azure usage file from CB Connect and Azure Usage Management tool on Microsoft Partner Center. Cause The discrepancy in the usage report in the Azure/Microsoft Portal and Connect usage report is due to the fact that Azure Usage Management is an informative tool that does not include discounts or credits that Microsoft applies to the partner. This is mentioned in their documentation - https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/get-started-partners. Therefore, it is expected to have some difference between the Microsoft portal vs Connect Usage. Resolution The connector uses the following formula: cost rated = BillingPreTaxTotal / (1 - RateOfPartnerEarnedCredit) Where BillingPreTaxTotal is partner cost (CR) and RateOfPartnerEarnedCredit (PEC) is going to be 0.15 if the partner has earned credit or 0 otherwise. Use this formula if you want to check the exact amount which should be in the usage file.