Activity Types
An activity is any time-consuming task such as, installation, trouble call, lunch, or team meeting that a resource does. Each activity type includes a set of features, which are yes/no flags and define the way the activity type is processed. Examples for features include whether activities of a specific type can be moved, created in a bucket, rescheduled, and so on. The Activity Types visibility controls the access to the Activity Types window. You must set the visibility for each user type that you want to manage Activity Types. If you don't configure an action for a user type or if you don't define the visibility, users of the user type cannot see the Activity Types. If you select ReadOnly, Activity Types is available in a read-only mode. If you select Read/Write, users can manage Activity Types.
Here is the detailed description of the features that may influence the processing of activity from the back office applications through Oracle Field Service.
| Feature | If enabled, the activities of the type... |
|---|---|
| Allow to create from Incoming Interface | … can be created from external systems, including Oracle Field Service ETAWorkforce |
| Allow move between resources | … can be moved between resources |
| Allow creation in bucket | ... can be created in bucket through routing plans and profiles |
| Allow reschedule | … can be moved to another day |
| Support of not-ordered activities | … can be not-ordered – such that can be started by the resource before/after any other activity within the route |
| Allow non-scheduled | ... can be activities without a date |
| Support of time slots | … can use time slots (time-period within which they are to be started can be defined) |
| Calculate activity duration using statistics | … are estimated using statistics that are gathered at the resource level and company level |