Table of Contents

Search

  1. Preface
  2. Introduction to Enterprise Data Manager
  3. Enterprise Data Manager
  4. ILM Repository Constraints
  5. Partition Exchange Purging
  6. APIs
  7. Salesforce Accelerator
  8. SAP Application Retirement Entities
  9. Import Formats for Constraints
  10. Glossary

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Partial Recurrence Activities

Partial Recurrence Activities

In Salesforce, you can create normal activities or recurring activities (both event and task). When you select records to archive, if the particular criteria selects only part of the recurring activities, then those activities are not archived.
For example, a recurrence activity was created on 30-Dec-2015 to recur 30-Dec-2015 to 1-Jan-2016. The activity has four records, where one record is the parent record and three are child records, as shown in the table below.
ID
Recurrence ID
Subject
Start Date
End Date
Recurrence End Date Only
XXXXXXX1
XXXXXXX1
Recurrence Test
30-Dec-2015
30-Dec-2015
01-Jan-2016
XXXXXXX2
XXXXXXX1
Recurrence Test
30-Dec-2015
30-Dec-2015
XXXXXXX3
XXXXXXX1
Recurrence Test
31-Dec-2015
31-Dec-2015
XXXXXXX4
XXXXXXX1
Recurrence Test
01-Jan-2016
01-Jan-2016
If you want to archive all of the 2015 data and give the "End Date" parameter in the Event entity of the archive job definition as 31-Dec-2015, then the first three records in the table are filtered. Data Archive will not archive these records, however, because the particular date selected partial records, or a partial selection of the transaction. These records are eliminated by the business rule, so none of the records will be archived or purged with the particular end date criteria.
To further understand how partial recurrence activities are archived, see the following example of an archive project that contains both the Task and Event entities.
The Task entity parameters are configured with the values in the following table:
Task Parameter
Value
CreatedDate*
31-Dec-2015
DueDate
null
LastModifiedDate
null
Created By
null
Status
Completed
The Event entity parameters are configured with the values in the following table:
Event Parameter
Value
EndDate*
31-Dec-2015
StartDate
null
CreatedDate
null
LastModifiedDate
null
Created By
null
Given these start and end dates in the entity parameters, see the table below for a description of how Data Archive would archive different types of records in different scenarios.
Activity
Description
StartDateTime/ActivityDate
EndDateTime
RecurrenceEnd DateOnly
No. of Records in Transaction
Filtered Records
Ready for Archive/Purge
Past normal record
Normal activity that is older than the particular date 31-Dec-2015
8-Sep-14
8-Sep-14
-
1
1
Yes
Today normal record
Normal activity that is happening on the particular date 31-Dec-2015
31-Dec-15
31-Dec-15
-
1
1
Yes
Future normal record
Normal activity in the future with the particular date 31-Dec-2015
5-Jan-16
5-Jan-16
-
1
0
No
Normal Event record which starts today and ends tomorrow (one normal event can span for 14 days)
Normal activity happening on the particular date 31-Dec-2015, but ending on a future date
31-Dec-15
1-Jan-16
-
1
0
No
Past recurrence parent record
Recurrence activity older than the particular date 31-Dec-2015
8-Sep-14
8-Sep-14
10-Sep-14
4
4
Yes
Future recurrence parent record
Recurrence activity in the future with the particular date 31-Dec-2015
8-Feb-16
8-Feb-16
10-Feb-16
4
0
No
Recurrence parent record that ends in future
Recurrence activity ending in the future with the particular date 31-Dec-2015
30-Dec-15
30-Dec-15
1-Jan-16
4
3
No
Recurrence parent record that ends today
Recurrence activity ending on the particular date 31-Dec-2015
29-Dec-15
29-Dec-15
31-Dec-15
4
4
Yes
Edited recurrence parent record (After creating, one of the child dates has been moved to a future date, for example 05-Jan-2016)
Edited recurrence activity which ends in future with the particular date 31-Dec-2015
27-Dec-15
27-Dec-15
29-Dec-15
4
3
No

0 COMMENTS

We’d like to hear from you!