Implement validation for custom field Names/IDs to ensure A4J rule compatibility between lower and production environments.

XMLWordPrintable

      Currently, after testing new A4J rules in a lower environment, if you export the rule from that lower environment and import it into production, those rules might fail to enable if there are differences in the custom field IDs between the environments.

      It would be good to have some extra validation related to the custom field Names/IDs between the lower/production environments.

              Assignee:
              Unassigned
              Reporter:
              Diogo Wunsch
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: