Would like more direct access to all field mappings, sources and update frequencies for the Customer data. For example, we can have several different rules populating the customer info fields but need to access that via each rules.
I've used a naming convention to separate Load to Customer rules from CTA triggering rules but it's still difficult to track or we can potentially have rules that overwrite values. In most cases, these are universal mappings and do not require specific filtering and scheduling configurations like we do with CTAs.
Userlevel 6
Would a filter on rules that load to Customers or similar action be useful in this scenario?
Rules engine is a loose coupling over the objects in SFDC, so a direct access to field mappings may not be possible.
Rules engine is a loose coupling over the objects in SFDC, so a direct access to field mappings may not be possible.
Userlevel 3
It would be useful but I have that covered with the naming convention.
Reply
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.