Proof of Delivery Rules
Introduction
Usually, the accounts involved (advertisers, agencies, etc.) receive one or more specimen copies after publication of an ad placement, which serve as proof that the order has been fulfilled. For this purpose, you will find a list of topics "Proof of Delivery" on the account (f42_dispo__MVX_ProofOfDelivery__c).
In MediaVelox you can create specimen copies according to various criteria:
Trigger criterion | Explanation |
|---|---|
An opportunity is set to "Closed & Won". The account field "Preferred number of specimen copies" f42_dispo__MVX_PreferredNumberOfProofsOfDelivery__c has a value > 0. | Publication-independent. You can store the required number of specimen copies for each account. If an opportunity in which the account was involved is closed (accounts 1-4 in multi-level sales and distribution) and there is a corresponding MRP book entry, the system generates the voucher copies that match the publication that was posted. Shipping address: Shipping address of the account |
An Dispo book entry is created. There is a specimen copy rule of the data record type "Based on dispo books" that matches the account. | Depending on the publication. You can use a rule to define the account for which specimen copies are generated for a particular advertiser when a booking is received. Shipping address: can be selected from the billing and shipping addresses of the account and contact. |
Manual triggering at the output. Voucher dispatch via specimen copy Rule of record type "Based on issues | Depending on the publication. You can use a rule to define the account for which specimen copies are generated for each issue independently of a posting. Shipping address: can be selected from the billing and shipping addresses of account and contact. |
Manual triggering | Via the "New" button on the topic list "specimen copies" on the account |
A report for exporting document data is currently not part of the product, but can be implemented in the project
Proof of Delivery Rules
Especially when other accounts are involved in a booking in addition to the advertiser, e.g. agencies or graphic designers, the control of specimen copies can become complex.
specimen copy rules offer greater flexibility here. MediaVelox distinguishes between two record types: Booking- and output-based rules.
As soon as rules are found for an account specimen copy, the specification in field f42_dispo__MVX_PreferredNumberOfProofsOfDelivery__c is ignored.
Proof of Delivery Rules - based on dispo books
Dispatch book-based rules are booking-dependent and are defined for a specific publication. The rule is triggered when an dispo book entry is created. Specimen recipients and advertisers, that is, opportunity accounts, do not have to be identical here:
The following fields are essential for creating the rule:
Field | Explanation |
|---|---|
| The following rule applies to this publication |
| Desired number of specimen copies specimen copies are generated after the rule for the posted output has been triggered. |
| The advertiser, that is, the opportunity account to which the offer is sent. |
| Recipient account of the specimen copy, this account does not have to be involved as another account in the opportunity. If advertiser and recipient account are identical, please select the account again here. |
| Recipient contact of the specimen copy |
Since the triggering of the rule is controlled by the advertiser, dispo book-based rules offer you the option of triggering document shipping for a third party that is not actively named in the bidding process.
Specifying the delivery address
After you have specified the recipient account and/or contact, the button for setting the delivery address opens in the lower part of the window:
You can choose between the billing and delivery address of the account and the two address fields belonging to the contact. The selected address is then stored on the specimen copy data record as the delivery address.
Proof of Delivery Rules - based on Issues
Issue-based rules allow you to control proof of delivery rules independently of booking, e.g. if you have agreed with an account to regularly send it a copy of your publication, even if it does not place an advertisement in every issue.
You create the rule and define the home delivery address in the same steps as for dispo book-based rules, except that in this case, you do not need to define an advertiser.
The issue-based rule is not triggered by the booking made but by the "Create proof of delivery" button on the issue that belongs to the publication:
Clicking the button opens a window in which you can confirm the execution of the rule:
After saving, the publication belonging to the output is checked for active rules and the corresponding specimen copies are generated:
You can only trigger document shipping once per issue, otherwise the system issues an error message. In this way, you are protected against duplicate data records:
Technical description
API Name | Label EN |
f42_dispo__MVX_ProofOfDeliveryRule__c | Proof of delivery rule |
Field Name | Label EN | Type | Comment |
|---|---|---|---|
Name | Delivery List Number | Autonummer | The individual rules receive a generic number as name |
f42_dispo__AdvertisingAccount__c | Advertising Account | Lookup (Account) | The advertiser, that is, the opportunity account of the associated booking |
Active | f42_dispo__Active__c | Checkbox | Proof of deliveries are only generated from active rules |
Account | f42_dispo__Account__c | Lookup (Account) | Recipient account of the proof of delivery |
Contact | f42_dispo__Contact__c | Lookup (Kontakt) | Recipient contacts of the proof of delivery |
number of Proofs | f42_dispo__NumberOfProofs__c | Number | Desired number of receipts |
Publication | f42_dispo__Publication__c | Lookup (Publikation) | The following rule applies to this publication |
Preferred Address | f42_dispo__PreferredAddress__c | Text | This field is filled in the background and identifies the selected recipient address |
Recipient Company Name | f42_dispo__RecipientCompanyName__c | Formula (Text) | The usually defined recipient account |
Street | f42_dispo__RecipientStreet__c | Formula (Text) | The normally defined recipient street |
City | f42_dispo__RecipientCity__c | Formula (Text) | The normally specified recipient city |
Postal Code | f42_dispo__RecipientPostalCode__c | Formula (Text) | The usually defined recipient postcode |
Country | f42_dispo__RecipientCountry__c | Formula (Text) | The recipient country usually specified |
Recipient Address Preview | f42_dispo__RecipientAddressPreview__c | Formula (Text) | Preview of the recipient address |
Description | f42_dispo__Description__c | Long Text Area(32000) | Optional description to the rule |