You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/08/07 16:50:00 UTC

[jira] [Commented] (OFBIZ-13480) Add OFBiz Routing Management REST APIs and Services

    [ https://issues.apache.org/jira/browse/OFBIZ-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102864#comment-18102864 ] 

ASF subversion and git services commented on OFBIZ-13480:
---------------------------------------------------------

Commit 0d9f242c29c2195e59402456d170ace8e01136c9 in ofbiz-framework's branch refs/heads/trunk from diveshdut
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=0d9f242c29 ]

OFBIZ-13480 Add routing cost REST API contract

Expose the Routing and Cost Management REST resource and map mutation endpoints to existing OFBiz services wherever their native contracts fit the request shape. Routing and task create/update operations delegate to WorkEffort services, routing task associations delegate to WorkEffortAssoc services, product/output links delegate to WorkEffortGoodStandard services, tool assignments delegate to WorkEffortFixedAssetStd services, operator assignments delegate to WorkEffortPartyAssignment services, and cost-rate creation delegates to WorkEffortCostCalc services.

Keep custom routing services focused on read payload aggregation, lookup payloads, and the explicit WorkEffortGoodStandard expiration flow needed for REST delete semantics.


> Add OFBiz Routing Management REST APIs and Services
> ---------------------------------------------------
>
>                 Key: OFBIZ-13480
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13480
>             Project: OFBiz
>          Issue Type: Sub-task
>            Reporter: Divesh Dutta
>            Priority: Major
>
> Implement OFBiz backend REST APIs and service support for the Routing Management PWA, using OFBiz-native services and utilities wherever possible.
> Scope includes:
>  * Add Routing Management REST API definitions under Manufacturing.
>  * Add read/query wrapper services for routing list/detail and operation/task list/detail payloads.
>  * Add lookup services needed by the PWA for products, parties, fixed assets/work centers, purpose types, and cost component options.
>  * Expose required native OFBiz services for routing write operations, including work effort, work effort associations, good standards, fixed asset standards, cost calculations, and party assignments.
>  * Keep write wrappers thin and delegate to native services where practical.
>  * Support REST paging, filtering, and sorting using framework utilities.
>  * Use native service types such as {{{}Timestamp{}}}, {{{}BigDecimal{}}}, {{{}Integer{}}}, and {{{}Long{}}}.
>  * Use path/query parameters for DELETE native key fields where OFBiz REST request mapping does not reliably pass DELETE JSON bodies.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)