Skip to main content
hamburger menu Created with Sketch.
Veeva Support EU Holiday: Aug 20th - 21st - Limited staff, please plan accordingly

Search the Knowledge Base

When is Veeva Align Feedback Data Ignored in the Targeting Feedback Process?

  • Updated

Question:

When can Veeva Align Feedback data be ignored in the Targeting Feedback Process? What happens when this happens?

Answer:

Feedback data can be lost in the following scenarios:

 

1. Assume that the Automated Feedback Handling Align Setting is set to Yes (True). Feedback data roll-back may occur in the case of challenges remaining in the Challenged Status.  The Challenge Status value Challenged is referred to as a Pending or Non-Approved Challenge.

Any Feedback challenges of any Feedback challenge types whose Challenge Status remains  Challenged (challenged__aln) is ignored once the (Territory) Feedback Complete Lifecycle state is set. 

This applies to all of the following Challenge Types:

  • Add Account (Model Account Territory record)
  • Remove Account (Model Account Territory record)
  • Keep Account (Model Account Territory record)
  • Add Target (MC Cycle Plan Target record)
  • Remove Target (MC Cycle Plan Target record)
  • Edit Goal (MC Cycle Plan Channel and/or MC Cycle Plan Product record)

What is meant by Ignoring? What happens to the Challenge data of each Challenge Type when the Lifecycle state of the related Model Territories or MC Cycle is changed? What are the main considerations?

Assume In the event the Challenge Status is Challenged of MC Cycle Plan Channel and/or MC Cycle Plan Product records and the lifecycle state is set to (Territory) Feedback Complete. The values of the respective (Team) Activity Edit Goal fields of the MC Cycle Plan Channel and/or MC Cycle Plan Product records are not stamped with the values of the respective Feedback Activity Goal fields of the MC Cycle Plan Channel and/or MC Cycle Plan Product records.

The (Team) Activity Edit Goal fields are not related to Challenges directly.

The values of the Challenge-related fields of any records having these Challenge Types still remain in the (Territory) Feedback Complete Lifecycle state. This also applies to Feedback Activity Goals of MC Cycle Plan Channel and/or MC Cycle Plan  Product records. 

However, after publishing the Modeling Project:

  • MC Cycle Plan Target records having the Add Target Challenge Type are completely deleted.
  • MC Cycle Plan Target records having the Remove Target Challenge Type are null.
    The Null-Out action, in the case of Remove Target, gets applied to the related Challenge Fields and data which are the values of the Challenge Type, Challenge Reason, Challenge Status, Feedback Provider, Challenge Note, and Challenged fields. The values of these fields are removed. The record itself is not deleted.
  • The Feedback Activity Goal Fields of the MC Cycle Plan Channel and MC Cycle Plan Product records - originating from the pending Edit Goal Challenges are null.
  • Model Account Territories having the Add Account, Remove Account, and Keep Account challenges are not published. However, the Model Account Territory records remain in the Modeling Project along with their respective values in the Challenge-related fields:  Challenge Reason, Challenge Status, Feedback Provider, Challenge Note, and Challenged fields.

 

2. Assume that the Automated Feedback Handling Align Setting is set to Yes (True). When the automated feedback processing detects an approved "Remove Account" request (it can be an end-dated record as well), it deletes any targets related to that account and tries to end-date any related, active Account Model Territories. How this could happen? This can occur if we clone a project that has old, outdated feedback in it - cloning a project clones all records from that project. It is advised to follow the standard process for preparing for the next sales cycle, it allows previous feedback to be incorporated into the next cycle, this process is explained here: Territory Feedback Standard Process

 

3. Another scenario may be Overwriting Feedback Data. See What is Meant by Feedback Data Overwrite in a Veeva Align Modeling Project which Contains or does not Contain an MC Cycle?

Notes:

Related Documentation:

CRM Help Documentation: 

Align Help Documentation:

Knowledge Article:

 

Powered by Zendesk