Reply posted on November 15, 2018 by RanganathK6165
JESUSG89, were you able to resolve the issue. i'm also facing similar issue.
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 Al Wells from Monster Pixel on being this week's Participant of the Week! Last week Al posted a few questions and not only did he find the answers, he updated the thread as such to help others in the PSC! Congrats again!
Please consider an upgrade to higher version where Deployment Manager built by Pega is provided to support DevOps approach like CD/CI. More details you can find at: https://community1.pega.com/exchange/components/deployment-manager
Hi, Please check below link, These may help you: https://community.pega.com/knowledgebase/articles/installing-and-configuring-deployment-manager-33x
We are also looking at upgarding the DB to SQL Server 2016. Our app is on Pega v7.2.2. We are not using any Pega frameworks. As per the above trail, Pega v7.2.2 is not certified for SQL Server 2016. What if we enable 'run in 2014 compatibility...
I am assuming you are referring to https://community1.pega.com/exchange/components/release-management-framework-rmf. I think when creating / configuring the environments in the RMF the type has to be selected as Repository or SOR. If this wasn'...
My Primary concern is no DSS should be exported fromDEV. either the product rule should throw error or should all DSS even if it is included as individual instances or it is exported with ruleset. (when the exclude non versioned rules is unchecked)...
Yes, for PegaRULES-ALERT.log, PegaRULES-ALERTSECURITY.log, and PegaRULES-SecurityEvent.log, the date and time are hardcoded in the messages.
Please wait while we search for PDN content that suits your question.