RMFW - Data-Tag-RelevantRecord Class Missing
For the Release Management Framework, I imported into 7.1.9 (one version below 7.1.10 the RMFW was created in) and ran into an error where the class "Data-Tag-RelevantRecord" was not present. Do you know if that is something that was introduced in 7.1.10 or is something that was missing from the import?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
GB
Thank you for your question. Someone will contact you with an answer presently.
Regards,
Andrew Fontenelle
PDN and Pega Academy Support Team
Paypal Inc
IN
Hi Ammor,
RMF for Pega 7 has been built on 7.2 and has not been tested in any of the before releases.
We will update the documentation to reflect this
Thank you
Sudharsan
UNISYS CORP
IN
while importing from 7.2 version to 7.1.9 , we ran into an error saying the class "Data-Tag-RelevantRecord" was not present. Do you know if that is something that was introduced in 7.2 or is something that was missing from the import?
screenshot of the error attached.
Paypal Inc
IN
Hi,
That is a data instance introduced in 7.2. Can you try creating a RAP excluding the Data-Tag-RelevantRecord and try to import in 7.1.9 ?
GE
IN
We are facing the same issue. ( V7.1.8 )
Apart from this, we are unable to launch the RMF portal from the admin layout. Unsure whether the Data-tags are the reason for this?
Any help will be appreciated
Scotiabank
CA
There is no documentatin anywhere on the purpose of this Data Instance. The data instance doesn't have a form either. Cannot be opened. It's auto created and auto associated with a Ruleset. To have one's Product Rule excempt these Data Instances requires the Developers and the release team to keep track of the all the other Data instances and to include them sepereately. Which is NOT Feasible.
So why not publish something on the the purpose of this class and it's instances. And if it's internal, prevent the Auto Association with a Ruleset so that they don't get migrated to other environments.
Pegasystems Inc.
IN
Because of this new data instances, now unnecessarily the count of Data Instances are getting almost doubled.
Can we have a way to exclude them in the product rule form (in Global Exclusion List). And also can some one explain if there is any implication if we dont ship them to the higher environments like (production).