Custom Code

The logistics industry handles a wide range of operations that deals with both the forward and the reverse flow of goods and services. It works on a point-to-point basis with the number of milestones between origin and point of delivery. Handling the operations and providing relevant information can be unique for each company according to its business logic. In such cases, the biggest challenge is to provide a technical layer that could meet each business’s requirements and to provide the scope of enhancing the logic layer in the future.

Custom Code support in CoreOS can help developers implement business-specific logic in their applications at different places.

Custom code helps the developers in defining the rules that govern the complete operational cycle. According to their needs, developers can configure Custom Code in the existing Core API services, such as Order, Dispatch, Entity, Container, and Participant.

Developers can modify the Core API services for creation, management, and execution in a self-service model. Here, we will further help you to understand the overall functionality and use of Custom Code.

CoreOS services that support Custom Code configuration functionality are:

Note: The link for implementing Custom Code is provided with each service.

Different categories where Custom Code is applicable:

Method Validation: While updating a value of an attribute, the method/function/code can check for attribute values of objects in the same service or a different service.

Example: Any billing method changes in the billing service should be notified to the relevant user groups/downstream services.

State Changes: A subset of Method Validation, this point caters to the state change of objects. Objects have states and they move from one state to another based on predefined rules. These rules vary from one business to another and depend on the values of attributes belonging to the same or different CoreOS service or an external application.

Example: For a client state to be changed to ‘Active’, there can be checks on the pricing information (from a pricing service) or attributes of the same client object or a third-party API service that determines the rules of activation.

Data Enrichment: Populating the values of attributes of an object at any point in the life cycle of that object in CoreOS.

Example: Waybill prefixes for a client are generated based on predetermined rules and used for any new waybills.

There are two ways to provide Custom Code: