Some customers ask for the recycling notice on everything they receive. The starter rule Show the recycling notice for a customer adds one rule that shows the notice your layout already holds on every label for one customer, wherever the order is going.
Use the starter rule
You need the Author role. The rule is added to a draft: production keeps using its active release until a Reviewer publishes a new one.
- Open Rules. The page opens on Starter rules.
- Find Show the recycling notice for a customer. It is in Label content; choose All or Label content to see it; you can also type a word such as "recycling" in Search starter rules and Help.
- Fill in the blanks in the card's sentence, "Show the recycling notice on every label for customer ….":
- Customer code: the customer's code exactly as it arrives in your job data, for example ELLAND. It is matched exactly as typed, including capitals, so a code with a space before or after it is refused.
- Choose Use this rule. The button waits until every blank has a value, and a value the card cannot accept is refused on the card with what the blank accepts.
LabelRules opens an ordinary rule draft, named with the sentence you completed. Its page says Began from a starter rule, names the rule that was added (for example recycling-notice-elland) and names the rule of yours the draft is anchored on, which is unchanged. No model is asked and nothing is approved.
What the rule does
The rule belongs to the decision what the label says. It matches when the job's customer code equals the code you entered, and it sets the recycling notice to shown. It is given a priority one step above every other rule that sets the notice, so it wins wherever it matches. Other customers keep what your destination rules decide.
The notice's wording and position come from the layout, which is changed and reviewed separately. To show the notice by country for every customer, use Show the recycling notice by destination.
Check the examples
Open Review the examples for this rule. The starter rule prepares five examples for the values you chose, one in each category, and the page says so under Examples prepared by the starter rule. They are not saved until you save them.
- Positive: a line for your customer prints the recycling notice.
- No match / default: another customer's line keeps what its own rules decide.
- Missing data: a line for your customer that is already held for missing data stays held.
- Boundary: a line for your customer going to a country with no notice rule prints the notice anyway.
- Unrelated: an export line for another customer is unchanged.
Check each example before you save it:
- Example input holds the values the example runs with. Change any that do not suit your data.
- Independently expected result is what you expect to happen. The starter rule fills in the part its own rule decides. The rest is LabelRules' ordinary synthetic example, so correct anything your own rules decide differently.
- Expected matched rule identities, in execution order lists every rule you expect to match. The starter rule states only its own rule. Add the others from the list of available rules, in order.
Tick the review box, write a note saying where the expected results come from and choose Save reviewed examples. Then choose Verify saved examples and inspect the proofs and refusals. A failed check tells you which expectation and which result disagree: decide which of the two is wrong before changing either.
Release it
When the saved examples pass, freeze the draft with Freeze rule candidate and hand the candidate to a Reviewer. Examples and releases describes the review and publication. Where the site requires a second approver, a rule from a starter rule needs one like any other.
If the card is refused
- This starter rule changed. LabelRules has a newer version of the starter rule than the page you have open. Reload the page and fill the card in again.
- The active release changed. A release was published while the page was open. Reload the page: the cards are built for the release in use.
- Remove the spaces around the customer code. The code is matched exactly as typed.
- A site holds up to 100 rule drafts and a ruleset up to 50 rules. At either limit, finish or publish existing work first.