Reminder campaign letters or emails must not be printed without using the print server. During the validation of a campaign, the print requests are stored in a print queue and processed sequentially.
To use a print server, it is necessary to update the NBMAXJOB parameter with a value greater than the sum of the letters and emails indicated in the To send block.
If possible, you can modify the default value of the NBMAXPROC parameter in the print server's administration console and set up the execution of N print requests in parallel.
The following activity codes (sorted by type) may have an impact on the way the function operates :
FUP :
Reminder and late payment mana
The following general parameters may change the way the function is working :
CURSHRFLD (defined at level Folder) : Common field currency
TYPCURSHR (defined at level Folder) : Common field rate type
FUPCRM (defined at level Folder) : Links between reminders and CRM
FUPRPTDIR (defined at level User) : Report destination directory
RPTBATCH1 (defined at level Site) : Letter destination batch
RPTBATCH2 (defined at level Site) : E-mail destination batch
RPTDST1 (defined at level Site) : Letter destination
RPTDST2 (defined at level Site) : E-mail destination
The sequence numbers used to number the documents managed by this function are :
FUP : Reminder campaign number
The sequence number assignment function defines the sequence number which is used
An authorization can be granted for this function to limit the processes to a company or a site.
When creating a campaign, there is a warning message if some sites cannot be accessed. If you proceed anyway, the campaign is created but only contains the open items relating to the sites you have access to.