Ideas

Better collaboration for better solutions

Handling legacy information from source systems that use AoC

We are redesigning a component called the Catalog Profile and it drives codes we use in the workflow. The fields the codes are in rely on reference data. The legacy codes won't be in the reference data, but they can come down with the source work order. When the legacy codes don't match anything in the reference data table, the MWFM system produces a blank. We'd rather that the legacy code was able to display, but not be selected from the drop-down.  

  • Guest
  • Aug 1 2018
  • Investigate
  • Attach files
  • Guest commented
    9 Jul, 2020 11:10pm

    Hi Debbie,

    We've discussed and I want to confirm if this would work for you:

    • Don't blank out child values when parent value changes if child values exist in new parent value, or parent value is blank.

    This would mean that the worker can still see the child values when choosing the new parent if needed.

    Cheers,

    Duncan

  • Guest commented
    1 Aug, 2018 09:12pm

    A drop-down field (tied to Reference Data) displays blank when the field contents do not match a selection on the Reference Data list.  We propose to show the actual contents (instead of blank) and allow selection from the Reference Data list.