Issues
- Anne Krieg
Introduction
Issues represent the regular releases of a publication (e.g. the monthly issue of a trade journal or the weekly sending of a newsletter)
There are two approaches to the AdSales process:
The sale of an ad based on time (i.e. based on the first day of sale of the issues).
The booking can also refer to a specific period of time (e.g. in the online area to the booking of a website banner. The sales price is then based on the period length. Within that term, a variable quantity can be booked (e.g. the desired number of clicks or ad impressions). Here, it also makes sense to structure the term with the help of the so-called issues.
In MediaVelox, the term "issue” has a broader meaning: issues are defined not only by time of publication but also, if required, by publication period. This ensures the greatest possible flexibility in the design of offers.
Our recommendation for the structuring of issues based on examples:
Publication | Type of Issue | Publication Cycle | Booking by Time Period | Booking over a period of time |
|---|---|---|---|---|
Regular newsletter | Single newsletter | One issue per newsletter | X |
|
Recurring events | Single event | One issue per event | X |
|
Online advertising medium, offered according to the number of ad impressions, clicks, etc. | Continuous runtime | One issue per calendar week |
| X |
Print publication | Periodical journal/magazine | One issue per first day of sale | f42_dispo__Publication__r.f42_dispo__isDigital__c = true | f42_dispo__Publication__r.f42_dispo__isDigital__c = true |
The clear structuring of the offer period in so-called issues has also a positive effect on reporting and facilitates the handling of the available inventory.
Although issues can also be applied to daily publication dates, this quickly increases data volumes and complexity. Our product support team will be happy to advise you on the optimal implementation of your requirements.
Object structure:
Salesforce setup
The Issues object is already available as a tab in MediaVelox. Use the "New" button to easily create a new record or template for further issues:
When creating a new issue, the following information is the basis for the AdSales process:
Field (with example) | Explanation |
|---|---|
 | Standard field for the name of the issue
|
Automatically generated issue name, consisting of the abbreviation for the publication, the issue number and year indicated below
| |
Numbering of the issue, e.g. according to a monthly interval | |
Year of publication of the issue
| |
Only active issues can be considered in the booking process. | |
Publication date of the issue | |
The issue is published by this date. Necessary for the offering process of products that are booked over a certain period of time (e.g. from the online area). A further prerequisite for booking over a period of time is that on the corresponding publication, the checkbox f42_dispo__isDigital__c is activated. |
The issue not only has a central function in the quotation process, but also in all processes in ad scheduling. You have also the possibility to store different kind of data on each issue: absolute publication dates, issues plan, the actual AdSales revenue values, production data and, if required, control document shipping.
Technical description
API Name | Label EN |
|---|---|
f42_dispo__Issue__c | Issue |
Name | Label EN | Typ | Kommentar |
|---|---|---|---|
Name | Issue Name | Text (80) | Manually assigned issue name. |
f42_dispo__IssueNumber__c | Issue Number | Text (12) | Structures the issues’s publication sequence. The field also allows you to create alphanumeric combinations |
f42_dispo__IssueYear__c | Issue Year | Text (4) | Year of publication, 4 digits |
f42_dispo__IssueName | Issue Name | Formula (Text) | This field is set automatically by a formula consisting of publication abbreviation, number and year. This name field is taken as reference in appero quote. |
fpub42_dispo__Publication__c | Publication | Lookup field (f42_Dispo__Publication__c) | Relation to the corresponding publication |
f42_dispo__isActive__c | Active | Formula (Checkbox) | Only active issues are available for selection in the offer process. This field is automatically marked as inactive once the publication date is more than 30 days old. |
f42_dispo__PublicationDate__c | Publication Date | Date | The availability of placements in print publications is based on this date. |
f42_dispo__PublicationDateUntil__c | Publication Date Until | Date | This field is required - in addition to the publication date - for advertisement types for which duration extends over a period of time, e.g. for digital products. Required for the correct display of availability in the appero quote editor. |
f42_dispo__PublicationTime__c | Publication Time | Time | Optional. The time of publication can be specified here. |
f42_dispo__ClosingDate__c | Closing Date | Date | Optional information for ad scheduling. |
f42_dispo__SubmissionDeadline__c | Submission Deadline | Date | Optional information for ad scheduling. |
f42_dispo__DateOfDelivery__c | Date of Delivery | Date | Optional information for ad scheduling. |
f42_dispo__NumberOfPages__c | Number of pages | Number (18, 0) | Optional information for ad scheduling. |
f42_dispo__PlanningValue__c | Planning value | Currency (16, 2) | A sales target value can be defined for each issue. |
f42_dispo__issueSumBooked__c | Sum Booked | Currency (16, 2) | Used temporarily in the booking overview, but not saved on the issue record, here the field remains empty. |
f42_dispo__issueSumReserved__c | Sum Reserved | Currency (16, 2) | Used temporarily in the booking overview, but not saved on the issue record, here the field remains empty. |
f42_dispo__Description__c | Description | Long Text Area (32000) | Optional |
f42_dispo__TeaserText__c | Teaser Text | Text (255) | Optional. Used for example to specify issue highlights. This specification also appears as a note in the offer process. |
f42_dispo__SAP_Issue__c | Issue ID | Number (10, 0) | Optional assignment of an external ID, for example, when integrating third-party systems. |
f42_dispo__isTemplate__c | Template | Checkbox | Identifies an issue as a template, which are then available for selection in the Lightning component "Duplicate Issues" as templates. |
Related topics
Publication: To which publication do the issues belong?
Ad Position Placement: The issue itself has no direct relation to the previously defined placements and formats, this connection is enabled by the relationship with Publication and the object "Availabilities".
Duplicate Issues: Use issue's templates to faster create and automate a sequence of issues in Salesforce.