This is a public Forum  publicRSS

Topic

    Marcos Zurli
    No work order areas exist for this postal code - Accelerator...
    Topic posted January 28, 2017 by Marcos ZurliRookie 
    31 Views, 2 Comments
    Title:
    No work order areas exist for this postal code - Accelerator OSvC x OFSC
    Content:

    Hi,


    I'm trying to create a work order from OSvC to OFSC through the Accelerator but I'm receiving the following error:

    "No work order areas exist for this postal code, please update the Postal Code field or submit with no timeslot and data selected."

    Why is this error occurring? I've configured the OFSC with the Workzone Key (as you can see in the screenshots) and also add this workzone to a bucket by "Resource Workzone" but the error persists. Could you help me?

    Version:OFSC Version 16.8 Service Update 4 (Build 16.8.4.6.8)
    Hi,


    I'm trying to create a work order from OSvC to OFSC through the Accelerator but I'm receiving the following error:

    "No work order areas exist for this postal code, please update the Postal Code field or submit with no timeslot and data selected."

    Why is this error occurring? I've configured the OFSC with the Workzone Key (as you can see in the screenshots) and also add this workzone to a bucket by "Resource Workzone" but the error persists. Could you help me?

    Version:
    OFSC Version 16.8 Service Update 4 (Build 16.8.4.6.8)
    Image:
    File:

    Answer

     

    • Edson Junior

      Hey Zurli,

      I am not sure, but try to verify the business rules and capacity as mentioned in the following link. It is a large document. However, it seems helpful to set up and test the accelerator.

      I saw something around page 34.

      Hope it helps.

      Thank you, Edson

       

    • Todd

      Zurli,

      Did you ever resolve this error your encountered using the accelerator? If so, how did you fix it? I'm experiencing the same error message and have set everything up per the documentation.

      Any help would be appreciated.

      Thanks,

      Todd