The value can be positive, negative, or zero. The default value is 1. Title: Serial Number. The serial number of the inventory. For serialized inventories, this is the unique key or a part of the unique key along with 'inventoryType' of an inventory for a particular resource.
This key is determined by the value of the 'identifySerializedInventoryBy' parameter. For non-serialized inventories, the value of this parameter can be specified but it does not hold any meaning. Title: Created. Title: Deleted. Title: Items Failed. Title: Results. The array of results. Each item in the 'resources' array in the request has a corresponding item in the 'results' array. The 'results' array items are in the same order as the 'resources' array items.
Title: Updated. Nested Schema : Results. Title: Result. Nested Schema : Result. Title: Errors. This field is returned only if any item fails. It contains human-readable description of the error such as type, title, HTTP status, and so on. Nested Schema : Errors. Nested Schema : Error. The detailed description of this error. The HTTP status code of this error. The brief description of this error. There are millions of records in customer table but we are assuming that there are records in customer table.
We need to execute all the ways and need to check the e performance of the different update statements. Scenario 1 : Traditional way to update individual records and commit after for loop. If you can check the first example where we are trying to update all records using for loop and then use commit statement. It is taking around 2 mins and 42 seconds to complete the procedure and to update the records. Scenario 2 : Traditional way to update individual records and commit inside for loop. If we can check the process and timing to execute the records or update the records in database it is approximately 3 mins and 58 seconds.
Here loop will run commit statement after every record update so the time to update the record is higher than single commit record. The bulk collect method is faster method than traditional methods.
We require to create a type variable where we can fetch all customer data and we need to use bulk collect statement in forall clause so that the records in the forall clause or specified table will be updated correctly.
If we can see the Elapsed time it is around 54 seconds which is more faster than other methods. Title: Sla Window End. If activity type configured with parameter 'SLA and Service window use customer time zone' then SLA is accepted in the time zone of customer field 'timeZone' , otherwise SLA is accepted in the time zone of the resource to which this activity is assigned Note that if the activity is later moved to another resource, and has activity type feature 'SLA and Service window use customer time zone' enabled, then SLA will be recalculated, so that in the customer's time zone these fields remain unchanged, but appear changed in the time zone of the new resource.
Title: Sla Window Start. Title: State Province. Title: Status. Allowed Values: [ "cancelled", "completed", "suspended", "started", "pending", "notdone" ]. As the technician performs the activity, it changes its status. Based on this status different actions are available for an activity. Initial status is "pending" for newly created activities, after that they can be "cancelled" or "started".
Activities with status "started" can be made "complete", "notdone", or "suspended". Title: Street Address. Title: Team Resource Id. Title: Time Delivered End. Title: Time Delivered Start.
Title: Time Of Assignment. Title: Time Of Booking. Title: Time Slot. Title: Time Zone. Customer's time zone name. Nested Schema : items. Title: Inventory. Nested Schema : Inventory. Id of activity this inventory is assigned to. Title: Exchanged Inventory Id. If an inventory was exchanged by resource with another inventory, then this field contains Inventory Id of the inventory it was exchanged with.
Title: Inventory Id. Title: Inventory Type. Type of the inventory as defined in OFSC. The inventory type marks inventory as serialized identified by its serial number or non-serialized having no serial number. Title: Quantity. Resource that has this inventory or resource that is assigned an activity that has this inventory. Title: Serial Number. Allowed Values: [ "customer", "resource", "installed", "deinstalled" ].
Current status of inventory: whether it is located e. Nested Schema : Items. Title: Activity link. Nested Schema : Activity link. Title: Link Type.
Type of relation between activities. These types have to be configured in Oracle Field Service Manage app. Minimum Value: 0. For links that define relative order of activities, this defines maximum acceptable time interval between subsequent activities minutes. For links that define relative order of activities, this defines minumum acceptable time interval between subsequent activities minutes.
Title: Required inventory. Nested Schema : Required inventory. Title: Required Inventory Type. Title: Required Inventory Model. Title: Required Inventory Quantity. Title: Resource preference. Nested Schema : Resource preference. Title: Preference type. Allowed Values: [ "required", "preferred", "forbidden" ]. Preference type. Nested Schema : Set Position in Route.
Title: activityId. If "position" is "afterActivity" then this is the activityId after which the other activity will be put. Title: position. Nested Schema : Set travel time. Title: Position. Expected position of the activity in a route In order to adjust a travel time to a given activity, it is also necessary to specify a location this travel is expected to be started from. Title: previousActivity. This field can be used as a replacement to the 'previousActivityId' one when it is impossible to use internal IDs.
Title: previousActivityId. It is an ID a previous activity that requires a calculation of travel time has the 'Calculate travel' feature. If there is an activity that doesn't require traveling for example: Call to manager , ID of this activity cannot be not used as 'Travel previous activity ID'. In this case, it is assigned to an ID of a previous activity that has a requires traveling.
Title: Source. Origin of the provided travel time data The 'manual' option is expected to be used when the adjustment value is entered by a human. Title: Travel time. Nested Schema : previousActivity. Title: Property name.
0コメント