• Hello, I add new topic.

    Rules are great to define some specific data. In sales, logistics, we have a few data to watch and work. Standard rules are not sufficient.

    What rules schould have in my opinion.

    A rule that works based on character count.
    If ‘product description’ has XX or more (or fewer) characters, replace it with ‘product name’ or insert an attribute + another attribute + another attribute.

    This is a powerful option.

    Another powerful option.

    A rule that allows you to edit fields. Character limit (related to what I mentioned above). If a field has more than XX characters, truncate the characters to ZZ + add 3 periods (…).

    Another very interesting option is the rule that allows you to combine individual data using and then without selecting the field to change (this option allows you to work on the same field, e.g., combining variables, numbers, and words, e.g., [unclear text]).

    Combined rules:

    If the ‘short description’ field is more than 300 characters, shorten it to 240 characters and add … and add the value ‘read more below’.

    or

    If the ‘short description’ field is more than 300 characters, insert the ‘color’ attribute, insert the ‘size’ attribute, insert the ‘material’ attribute, and add the value ‘read more below’.

    We generally need other rules, but implementing these makes things much easier. They’re helpful in development. Of course, nested XML feeds would be great (nesting could be bypassed if the system allowed adding prefixes and suffixes that kill the <><>/ characters—this is a threat to the file, but this can be bypassed with a button that allows these type characters (allow adding <>/ etc. characters, I understand the risk)).

You must be logged in to reply to this topic.