Custom services
Custom services
Introduction
Custom Services contain all the information on a service offered in a facility. An example of a Custom Service would be an adjustment of a shirt by adding an embroidery on the collar and sleeves. After creation, the Custom Service is available for usage in all facilities. A Custom Service can also reference another Custom Service (such as when one service requires another to be done first), up to a maximum depth of 25 services(A -> B -> C ... -> Y). Custom Services are executed via service jobs in the operational process.
Orders that are split by routing decisions are currently not supported with Custom Service. We do not recommend activating order split when working with Custom Services and service jobs.
Facility custom service connection
Custom Services can be available in different facilities and can have differences in execution time or (temporal) availability. To make a Custom Service available in a specific facility, it has to be connected to the facility. This is achieved through a FacilityCustomServiceConnection object. The connection allows customizing the execution time and the availability of the Custom Service in the specific facility.
Linked service jobs
Linked Service Jobs are a virtual construct that shows the sequence and dependencies between different Service Jobs. The dependencies between Service Jobs are represented by Service Job Links.
Service jobs
While Custom Services serve as a blueprint, Service Jobs are the actual instances of a Custom Service.
When a Service Job is created, it will always be part of a Linked Service Job. New Linked Service Jobs will be created when a Service Job is created. Alternatively a reference to an existing Service Job Link can be provided when creating a Service Job. In this case A Service Job Link (referencing the created Service Job) will be created and embedded in the referenced Service Job Link.
Besides the basic information like name and description, a Service Job also contains information about the line items that are required for the execution of the Service Job.
Service job links
A Service Job Link holds a reference to a Service Job and to previous Service Job Links. It also holds an array of following Service Job Links.
A Linked Service Jobs is automatically created when a Service Job is created. It is not possible to create a Linked Service Jobs object manually. However, it is possible to add Service Job Links to a Linked Service Job and thus customize the sequence of related Service Jobs.
Dependencies between service jobs
As a Linked Service Job maps the sequence of Service Jobs, it also creates dependencies between them. The order of the Service Jobs is determined by embedding Service Job Links in ServiceJobLinks. The embedded Service Job Links have higher priority than the enclosing Service Job Links. This means that the Service Job referenced in the embedded Service Job Link must be executed before the Service Job referenced in the enclosing Service Job Link can be started.
Service data
Service Data is a helper construct that contains information about the items that are available for usage in a Service Job. One Service Data object is created for all Service Jobs that are part of a Service Job Link.
While the Service Data object is created automatically, when a Service Job is created, it will be created empty, if it is created via API and it will be filled if the related Service Jobs are created via Pick Job creation. In the latter case, the Service Data object will be filled with all lineItems that are part of the pick job, even if they are not required for any Service Job.
Last updated