Reply posted on August 14, 2019 by VSSPRUDHVIKRISHNS
This comment/reply has been branched into a new post
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 Kannan Raveendran Nair for achieving the title of Participant of the Week! Kannan believes in sharing knowledge. He proved to be an amazing participant by writing a knowledge share article on a topic that will be informative to the diverse audience in the community. Read his article here. Keep up the great work!
We recently experienced this same issue when creating a custom Nexus component. There is an additional activity that unfortunately needs to be implemented to support the devops merge wizard with custom repositories. We have a bug internally to address...
Hi Sunil, Release dates are considered as insider information and will not be shared on our community. Please reach out to your Pega Account Executive who can keep you informed on the latest releases. Thank you.
This issue has been fixed as part of DM-4.5 and a RAP was supplied to customer for 3.3.1 version. So Closing this thread
The Issue has been fixed. How? You need to keep branch rule set version unlocked but lock the ruleset which you have mentioned in the product file. Also, uncheck the option- "Allow checked out rules...." in the product rule.
I found the required details in the document about Deployment manager. Thanks for your effort and time. https://community.pega.com/knowledgebase/articles/using-deployment-manager-41x#startbuild
Hi Sowmya, Below is the link for the article. https://community.pega.com/knowledgebase/installing-upgrading-and-configuring-deployment-manager-44x Thanks, Lokanath
Please wait while we search for PDN content that suits your question.