...
In the claiming process it should be possible to create several claiming sets which consist of several claiming levels and templates for the reminders. It is necessary, because some types of resources or acquisitions acquisition methods need distinctive:
...
Configuration of claiming/reminders
Claiming sets
consists several claiming levels
activation of the reminder by checkbox
the reminders and reminder levels should be managed in the Claiming app (no setting is yet available for the Receiving app)Wait for feedback from PO
Claiming levels
are defined by the number of days, weeks, month, ... until the reminder is sent
five claiming levels should be available for each claiming set
BUT: not all levels need to be configured in one claiming set - for example, only claiming levels 1 and 2 a re necessary for one specific acquisition methodthe number of claiming levels should be configurable for each claiming set. For example, if only 2 claiming levels are necessary, it should not be necessary to configure the claiming levels 3-5.
the following fields are required for each claiming level
number of days, weeks, month, ... until the object is marked as overdue and ready for claiming
Templates for sending e-mails
reminder levels can be evaluated via token (1st reminder, 2nd reminder, ...)
In the SLUB and UBL, texts can be configured for each claiming sets
→ Discuss suggestions with PO as to where the configuration takes place - but this should be configurable in an ONE app for all objects/acquisition types/...
E-mail dispatch of the reminder
single email-dispatch per order
contact information is derived by the applied integration in the order
plain text (and with HTML if necessary)
each reminder should be clearly separated from the other ones
Export function for overdue orders
the records of the overdue orders should be exportable for external examination
...