Newer Version Available
ActivityTiming
Supported Calls
create(), delete(), describeLayout(), describeSObjects(), getDeleted(), getUpdated(), query(), retrieve(), search(), undelete(), update(), upsert()
Fields
| Field | Details |
|---|---|
| ActivityCountPerRepetition |
|
| ActivityDuration |
|
| ActivityDurationUnitId |
|
| ActivityTime |
|
| ActivityTimeOffset |
|
| CountInPeriod |
|
| LastReferencedDate |
|
| LastViewedDate |
|
| MaxActivityCountPerRepetition |
|
| MaxActivityDuration |
|
| MaxCountInPeriod |
|
| MaxRepetitionCycleLength |
|
| Name |
|
| OwnerId |
|
| PeriodEndDateTime |
|
| PeriodLength |
|
| PeriodLengthLowerLimit |
|
| PeriodLengthUnitId |
|
| PeriodLengthUpperLimit |
|
| PeriodStartDateTime |
|
| RepetitionCycleLength |
|
| RepetitionCycleUnitId |
|
| SourceSystem |
|
| SourceSystemIdentifier |
|
| SourceSystemModified |
|
| TimingCodeId |
|
| UsageType |
|
| WeeklyActivityTimeId |
|
Usage
ActivityTiming records are referenced from MedicationDosage records to specify the timing of their activities. Here’s an example of an activity’s timing information and how an ActivityTiming record would represent that information.
Scenario: Let’s say your doctor tells you that you have to run for 10 minutes every 2 days, 30 minutes after your meals. You need to run at least 5 times in the span of those 2 days. You have to do this for 3 to 4 weeks. You’re also told that you shouldn’t run for more than 15 minutes at a time, and that you shouldn’t do it more than 7 times in 3 days. So in those 3-4 weeks, you should run somewhere between 60-84 times.
Sample Record:
Associated Objects
This object has the following associated objects. If the API version isn’t specified, they’re available in the same API versions as this object. Otherwise, they’re available in the specified API version and later.
- ActivityTimingFeed
- Feed tracking is available for the object.
- ActivityTimingHistory
- History is available for tracked fields of the object.
- ActivityTimingShare
- Sharing is available for the object.