Reply posted on March 8, 2019 by RaghavendraT9414
Thanks, it is working now.
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
Congratulations to Anthony Tham for achieving the title of Participant of the Week! Anthony proactively assisted several users with their queries, which helped them progress with the troubleshooting and arrive at successful solutions. We appreciate your efforts to share knowledge in the community. Hope to see you around and keep up the great work!
OK, I got the response frome the PO:-) More than 4 canditate systems in the pipeline is currently not supported by PDM. So 2 pipelines are required to achieve it. Regards, Rodolphe
Go to the Diagnostic Cloud Menu, System Administration, Manage System Access From there you can restrict an operator to see only specific systems
I figured out the issue. The name that was being passed to the Test Suite ID was incorrect. It should be the pxInsname and not just pyID. Thanks!
These features are not available for 7.3.1 compatible version of Deployment Manager and there are no plans to support them there. Upgrading to the latest version of the platform will allow you to get the newest Deployment Manager versions and its...
New AESRemote versions are available for 722, 73, 731 and 74 The latest versions shipped are below; we will be releasing new enhancements in February Pega Version SR Item SE Item HotFix DL BUG Pega 7.2.2 SR-C62499 SE-47522 HFix-47522 DL-92871 BUG...
Yes you can configure orchestrator and Dev systems in single system. If Orchestrator environment is also used as QA or any other candidate in pipeline, then please be careful when you perform rollback action. Currently Deployment manager uses OOTB...
Please wait while we search for PDN content that suits your question.