Limiting Past Call Submission
To prevent users from submitting calls that occurred too far in the past, call submission for the previous month’s calls can be restricted past a certain number of days into the current month. The limit on past call submission can be customized for each month of the year.
For example, the limit on past call submission is set so call reports from the past month cannot be submitted after the 10th of the next month. If a call report created on December 20th is not submitted, the Submit button is disabled on January 11th and users cannot submit the call.
Who can use this feature?
- Browser, iPad, iPhone, Windows Users
- Users do not require an additional license
- End Users
Configuring Limiting Past Call Submission for
End Users
To configure this feature:
- Ensure Configuring Call Reporting is complete.
-
Enter the appropriate text in the call_submission_monthly_window__v Veeva Setting. The syntax for the Veeva Setting must be as follows:
<MONTH_NUMBER>,<NUMBER OF DAYS OF WINDOW>;<MONTH NUMBER>, <NUMBER OF DAYS OF WINDOW>,
where <NUMBER OF DAYS OF WINDOW> determines the number of days of the defined <MONTH NUMBER> that the organization allows calls to be submitted in the previous month (<MONTH NUMBER> - 1 unless January, then it would be 12). The call_date__v field on the call2__v object is used as the reference.
For example, if CALL_SUBMISSION_MONTHLY_WINDOW = 1,10; 2,5; 3,10; 9,5; then for January, calls from December are allowed to be submitted until January 10th; January calls until February 5th; February calls until March 10th; August calls until September 5th. After September 5th, calls cannot be submitted.
For months not defined in the setting, the previous month’s calls have no submission limit. Zero is not a valid value.
Alternatively, use the CALL_SUBMISSION_MONTHLY_WINDOW Veeva Message instead of the Veeva Setting:
-
Populate the call_submission_monthly_window__v Veeva Setting with the following text: CALL_SUBMISSION_MONTHLY_WINDOW;;CallReport
-
Enter the appropriate text in the CALL_SUBMISSION_MONTHLY_WINDOW Veeva Message, using the same syntax as would be used for the call_submission_monthly_window__v Veeva Setting:
<MONTH_NUMBER>,<NUMBER OF DAYS OF WINDOW>;<MONTH NUMBER>, <NUMBER OF DAYS OF WINDOW>,
where <NUMBER OF DAYS OF WINDOW> determines the number of days of the defined <MONTH NUMBER> that the organization allows calls to be submitted in the previous month (<MONTH NUMBER> - 1 unless January, then it would be 12). The call_date__v field on the call2__v object is used as the reference.
For example, if CALL_SUBMISSION_MONTHLY_WINDOW = 1,10; 2,5; 3,10; 9,5; then for January, calls from December are allowed to be submitted until January 10th; January calls until February 5th; February calls until March 10th; August calls until September 5th. After September 5th, calls cannot be submitted.
For months not defined in the setting, the previous month’s calls have no submission limit. Zero is not a valid value.
Using Limits on Past Call Submission as
End Users
Users cannot submit calls that fall outside of the time range specified in the Veeva Message; an error message displays and users are prevented from submitting the call. Unsubmitted calls remain in their saved status and can be managed later via an external process since they can still be synced from mobile devices.
