Uploaded image for project: 'OFBiz'
  1. OFBiz
  2. OFBIZ-6307

Add ability to change Routing statuses

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Implemented
    • Affects Version/s: Trunk
    • Fix Version/s: 16.11.01
    • Component/s: manufacturing
    • Labels:
      None

      Description

      Only ROU_ACTIVE statusItem exists for statusTypeId ROUTING_STATUS. Adding another such as ROU_INACTIVE would allow for more control over routings. Doing so entails adding the statusId to the find and edit screens.

      1. OFBIZ-6307.patch
        6 kB
        Christian Carlow
      2. OFBIZ-6307.patch
        7 kB
        Jacques Le Roux

        Activity

        Hide
        ofbizzer Christian Carlow added a comment -

        ROU_INACTIVE was add as a StatusItem and currentStatusId was added to the routing find form as a multi-drop down which depends on OFBIZ-6308 to allow filtering of multiple statuses.

        Show
        ofbizzer Christian Carlow added a comment - ROU_INACTIVE was add as a StatusItem and currentStatusId was added to the routing find form as a multi-drop down which depends on OFBIZ-6308 to allow filtering of multiple statuses.
        Hide
        swash78 Swapnil Shah added a comment -

        Yes, this is valid addition in order to allow any Inactive routing to not be used by a production run. Possibly we could support the status based application/association between a routing and production run as well if it doesn't exist currently.

        Show
        swash78 Swapnil Shah added a comment - Yes, this is valid addition in order to allow any Inactive routing to not be used by a production run. Possibly we could support the status based application/association between a routing and production run as well if it doesn't exist currently.
        Hide
        jacques.le.roux Jacques Le Roux added a comment -

        Here is an updated patch with use of common/webcommon/includes/setMultipleSelectJs.ftl

        Show
        jacques.le.roux Jacques Le Roux added a comment - Here is an updated patch with use of common/webcommon/includes/setMultipleSelectJs.ftl
        Hide
        pfm.smits Pierre Smits added a comment -

        For most, running a manufacturing business means that they do repeat runs of a production schema to execute production runs. This means that the production run is defined by the production schema (or in OFBiz parlance: the routing). And each production schema is defined by its associated schema tasks (OFBiz: routing task) and other elements.

        In this construct the associated schema tasks have a lifespan (fromDate and thruDate fields). This should ensure that a new production run isn't build with tasks from a schema that has tasks outside of the intended sweet-spot.

        This, however, poses unnecessary constraints in the situations where the initial production run is based on an existing schema and then gets enhanced with additional schema tasks.
        To this date the list of available schema task encompasses all. So, in that respect a statusId value that would limit the list of available is warranted.

        However, this kind of work effort definition also has to adhere to a lifespan. IMO, this should be the first way to show visibility for direct selection.

        Show
        pfm.smits Pierre Smits added a comment - For most, running a manufacturing business means that they do repeat runs of a production schema to execute production runs. This means that the production run is defined by the production schema (or in OFBiz parlance: the routing). And each production schema is defined by its associated schema tasks (OFBiz: routing task) and other elements. In this construct the associated schema tasks have a lifespan (fromDate and thruDate fields). This should ensure that a new production run isn't build with tasks from a schema that has tasks outside of the intended sweet-spot. This, however, poses unnecessary constraints in the situations where the initial production run is based on an existing schema and then gets enhanced with additional schema tasks. To this date the list of available schema task encompasses all. So, in that respect a statusId value that would limit the list of available is warranted. However, this kind of work effort definition also has to adhere to a lifespan. IMO, this should be the first way to show visibility for direct selection.
        Hide
        jacques.le.roux Jacques Le Roux added a comment -

        Thanks Christian for your patch, Swapnil and Pierre for your comments.

        At revision: 1741789 I committed the patch enhanced with multiple.js and French labels.

        If we want more options please create other Jira issues...

        Show
        jacques.le.roux Jacques Le Roux added a comment - Thanks Christian for your patch, Swapnil and Pierre for your comments. At revision: 1741789 I committed the patch enhanced with multiple.js and French labels. If we want more options please create other Jira issues...

          People

          • Assignee:
            jacques.le.roux Jacques Le Roux
            Reporter:
            ofbizzer Christian Carlow
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development