Question

Pega Marketing: Artifacts Ruleset does it support Versioning of RS?

Hello - On Pega Version 8.1 and higher, does Pega Marketing Application that contains the "Artifacts" Ruleset, support versioning of that Ruleset?

Artifacts Ruleset is supposed to be always Unlocked so that MKTG engine can use it for creating and managing all the rules that are part of MKTG runtime processing. There are specific rule types that should be placed in this Ruleset as per the MKTG Guides.

Question is: can we create versions of this Artifacts RS such that all older versions are Locked and the most recent highest version is Unlocked?

Comments

Keep up to date on this post and subscribe to comments

April 11, 2019 - 9:10pm

Definitely you can have versions of Artifacts... here is a screenshot:

April 25, 2019 - 7:12am
Response to KevinZheng_GCS

hi Kevin -- I don't see the screenshot attached to this thread.

Also, can you check internally especially with the MKTG product team on this question? Lower versions of Pega MKTG had problems with versioning of "Artifacts" Ruleset which is used by MKTG engine to perform bunch of Marketing operations creating/ modifying/updating those rules on the fly.

I raised this question to check if anything has changed for 8.1 or higher versions particularly for the MKTG Artifacts RS.

August 1, 2019 - 1:42pm

I think the question is not 'can' you version artifacts, but 'should' you version it ... 

Artifacts is the sandbox for outbound Marketing, and developers should not put their own rules in there, so why do you want to lock a version and open a new ruleset version?

I can see possibly a need to clean up artifacts, but not version it.

it will get cluttered with test segments, and campaigns, and all the batchout Classes that are generated for you ... but since there is no code to deliver and push (other than things like the offer flows) you generally don't want to promote it to other environments instead just use a product rule and include just the items that need to be delivered (like the offer flows) in your product package.

if you do lock it and push to a higher environment you will push all the development test artifacts that are not meaningful to test/preProd/Prod ... and you will just clutter things up in the higher environments as well.

just my 2p worth, but ...