Limiting Past Call Submission
Users can be prevented from submitting calls that occurred too far in the past. The CALL_SUBMISSION_MONTHLY_WINDOW Veeva Setting points to the corresponding Veeva Message to limit the number of days into the current month a user can submit calls which occurred in the previous month. For example, Verteo Biopharma requires its users to submit calls from the past month no later than the 10th of the next month. Sarah Jones creates a call for Dr. Ackerman on December 20th, but she fails to submit it before January 10th. When she views the call report on January 11th, the Submit button does not display and she cannot submit the call.
Configuration for Limiting Past Call Submission
Ensure initial configuration is complete before enabling this functionality.
To set a monthly window for past call submission, enter the appropriate text in the CALL_SUBMISSION_MONTHLY_WINDOW Veeva Message. The syntax for the Veeva message must be as follows:
CALL_SUBMISSION_MONTHLY_WINDOW = <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_vod field on the Call2_vod object is used as the reference.
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 to be submitted until September 5th. After this date Calls cannot be submitted.
For months not defined in the setting, the previous month’s calls have no submission limit. Also, zero is not a valid value.
Using Limits on Past Call Submission
Users cannot submit calls that fall outside of the time range specified in the Veeva Message; the Submit button is disabled for calls outside the allowed time range. Unsubmitted calls remain in their saved status and can be managed later via an external process since they can still be synced from offline devices.