Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

New Control Typology rules in ACS

AKP3
Level 2
Level 2

How to create New Control Typology rules in ACS? 

 

Use Case I:  Need to fail the Delivery executed on an adhoc basis by the user in preparation stage if some mandatory URLs are accidentally deleted before sending or missed to get reviewed while proofing the content. For example Opt Out link, Mirror Page link, subscribe link or any other links. Something similar to what we have for Check subject line control rule. Note* - Check unsubscription link (urlOptout) OOB control rule is not failing the delivery when an opt out link is not present. It just writes the warning in the log.

 

Use Case - II: Need to fail the Delivery executed on an adhoc basis by the user in preparation stage if the user has not named the Delivery Label using proper naming convention.

1 Accepted Solution
craigthonis
Correct answer by
Employee
Employee

Hi AKP3,

 

Due to design, there isn't a simple way to modify or create Control Typology rules in ACS. This is to protect the product from misconfigurations that could significantly harm the environment.

 

That said, the steps below can be leveraged to by an advanced user to create a control typology.

 

1/ Export in a package a typology rule of type "control"
2/ Update the exported xml file to adapt with your needs (name, <code>)
3/ Import the changed xml file

 

Please note, any changes should be performed in Test and validated prior to moving to production.

 

Regards,

Craig

View solution in original post

1 Reply
craigthonis
Correct answer by
Employee
Employee

Hi AKP3,

 

Due to design, there isn't a simple way to modify or create Control Typology rules in ACS. This is to protect the product from misconfigurations that could significantly harm the environment.

 

That said, the steps below can be leveraged to by an advanced user to create a control typology.

 

1/ Export in a package a typology rule of type "control"
2/ Update the exported xml file to adapt with your needs (name, <code>)
3/ Import the changed xml file

 

Please note, any changes should be performed in Test and validated prior to moving to production.

 

Regards,

Craig

View solution in original post