Classification Sets - How do I create rule?

[ericnguyen021]

Hi Community,

Do we know what will happen when classification rule build gets deprecated? our team is looking to get some insights on what we should do to prepare for this as most of our classification is being populated using rule builders.

Thank you in advance!

[MandyGeorge · Accepted solution]

The legacy classification rule builder is being sunset Aug 31, 2026. So there is still plenty of time.

Ideally, the best thing to do is to start migrating your classifications over to classification sets. Rather than having separate places for the classification importer and the rule builder, they will both now be in the same place. Any classifications that you have that are using the importer you can migrate now. There are also some new options for automating the imports to make it easier to maintain.

However, if you're using the rule builder (for stuff such as regexing values), it doesn't seem that the rule builder portion has been released into the classification sets yet. I would suggest reaching out to customer care to see if they can provide any information on when it will be updated, especially if you're looking to start migrating your classifications. 

So while we do want to migrate rule builder classifications, we can't do it quite yet, although hopefully Adobe will make that available soon!

[Jennifer_Dungan]

@MandyGeorge is correct, the "new" rule builder for classification sets is not yet built/released... so classifications requiring regex rules must still be done in the legacy system.

Depending on how many rules you have to migrate, When you start the process will have to take effort into account, but there is lots of time so far, again, as mentioned you have until Aug 2026.

That said, I have seen a lot of bugs reported with the classification sets, and encountered some myself.

Your existing classifications should all have been "auto" made into Classifications Sets by Adobe... for better or worse... All my legacy classifications are set to a minimum of 2 suites (QA and Prod), and in some cases 3 (QA, second isolated QA, and Prod), all with a specific naming convention for proper identification of the purpose / dimension....  all of the auto created classifications were created as one per suite, with horrible naming. When I attempt to consolidate them, it failed.

This means I will have to delete everything and re-build.. and since 99.9% of my rules are Regex based (so I will still have to do work in the legacy rule builder), I am not doing this until there the new rule builder is released, because I am concerned that I will have to do all that work again once Classification Sets are fully released. And even when it does, I will test in my QA suite only, and confirm functionality, then start the migration on the least critical rules first, making sure they are doing what they should. Then, and only then, after I have confirmed viability, will I start the migration in earnest. 

However, this is a choice I make for myself, and only you know how much work and effort is required to migrate your rules.

[Meghan_Powers]

Like the other responses, I'd start building what you can now in your dev report suite and compare and contrast what data returns for each set.  Hopefully you get identical data sets with old method and new method.  If different, I'd try to not "are all of them a consistent % off?"