Latest Updates for OS1 Services
Release Date: March 21, 2023 and March 28, 2023
Hello OS1 Developers 👋
We’re excited to announce our latest improvements to our OS1 services. Our team has been working hard to improve your experience, and we have some great enhancements to share. So let’s dive into the details!
We’ve significantly improved the Workflow Service and Dispatch SDK which will make the Field Executive (FE) experience faster and more efficient. With this release, FEs can now execute tasks across different objectives simultaneously instead of processing individual shipments one by one.
This change enables Field Executives (FE) to complete multiple deliveries in one trip. For example, suppose an FE has three Cash-on-Delivery (COD) packages addressed to the same customer. In that case, they can now deliver all three in one visit instead of making three trips. This reduces the turnaround time and ensures a smoother, more seamless experience for both FEs and customers. OS1 developers can benefit from developing apps that enable delivery completion in a cost and time-effective manner.
We’ve upgraded our Dispatch SDK with the ability to send out Event Tasks (ET) event information asynchronously! Previously, the workflow execution did not send notifications without moving from one event to another. With our latest update, the Dispatch SDK will now emit two asynchronous events – one just before and another right after the execution of every ET in the workflow.
Here’s a brief rundown of the enhancement:
- Task Start Event: This event is triggered upon the arrival of an ET, providing you with input data to kick off the task. With this, you can quickly get a heads-up when a task is about to kick off, allowing you to prepare for any necessary actions.
- Task End Event: This will be triggered before moving to the following Event Task. You’ll receive the output data of objectives executed in the current ET and the ID of the next ET to be completed. This allows you to wrap up any loose ends before diving into the next task.
Now you can easily stay informed as your workflow progresses, allowing you to listen to these events and take any necessary actions to tailor your business use cases. Learn more about the Dispatch SDK
We’ve enhanced our Execution Tasks capabilities to provide more flexibility. Previously, our ET configuration allowed you to define only one Event Code each for success and failure events. Additionally, you could specify the underlying Reason Codes for these events. With this improvement, you can now define multiple Event Codes based on your specific business needs and seamlessly associate them with the success or failure of your Execution Tasks.
This release greatly improves our Workflow Designer’s Form Execution Tasks (ET) feature! Form ET has been a valuable tool for admin users, enabling them to easily create custom input fields such as text boxes, radio buttons, and more for their workflows. This is especially useful when workflows require real-time on-the-ground input.
Until now, Form ET only supported static values for fields that needed to be preloaded with data, like radio buttons. To enhance this functionality, we’re excited to introduce the ability to pass dynamic values in Form ET!
With this powerful new feature, developers and admin users can now configure Form ET to accept dynamic values, giving you even more flexibility and control over your workflows. This means you can quickly tailor your forms to meet your unique needs.
In some instances during workflow execution, FEs may need to go back and review or modify previous steps in a workflow. Whether it’s a rescan of shipments or updating NSLs/ER Codes based on the seller’s response to the ePOD, we’ve got you covered!
With this release, we’ve introduced the ability to return to previous ETs in your execution workflow. This handy feature creates a more adaptable workflow experience with the flexibility to revisit and adjust your tasks as needed.
Learn more about Execution Tasks.
We’re excited to share some significant improvements to the Participant, Container, and Entity services. We have successfully upgraded our database validations and destination state checks from synchronous to asynchronous operations, providing a smoother and more responsive user experience. Now, when calling state transition or update APIs immediately after receiving a 202 status from a POST API call, you’ll experience enhanced performance and responsiveness.
Here are some highlights of the key enhancements:
- Async instance-specific validations: We have moved instance-specific validations to the async handler, such as checking if a participant instance is present. This change ensures a more efficient and streamlined validation process for your instances.
- Command handler updates: We’ve made important updates to our command handlers! We’ve reconfigured the Create, Update, and AppplyEvent command handlebars to work seamlessly within a single go, following the changes made to our event sourcing library, providing more streamlined operations when working with OS1.
Click the Run in Postman button below to open a modal where you can fork our latest collection to your workspace and stay up to date with the latest changes.