Genesys Cloud - Developer Community!

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

archy create task not working when trying to create a flow that contains Decision Tables calling

  • 1.  archy create task not working when trying to create a flow that contains Decision Tables calling

    Posted 20 days ago

    Hi Guys

    I'm using archy to migrate flows from Division A (uat) to Division B (prod) on the same Org, I was able to migrate several IVR flows; however, when trying to migrate a flow that contains a decision table call, it fails with the following error:

    [ERROR] unsupported data type of 'customJson'. Available data types are ''agentScorePair', 'audio', 'boolean', 'currency', 'dateTime', 'date', 'decimal', 'duration', 'integer', 'externalOrganization', 'externalAddress', 'externalFacebookInfo', 'externalFacebookId', 'externalLineInfo', 'externalLineId', 'externalTwitterInfo', 'externalPhoneNumber', 'externalWhatsAppInfo', 'externalContact', 'json', 'prompt', 'skill', 'string', 'userQueue', 'queue', 'utilizationLabel', 'wrapupCode', 'group', 'phoneNumber', 'emergencyGroup', 'schedule', 'scheduleGroup', 'skillExpressionFilter', 'issueInfo', 'languageSkill', 'agentScorePairCollection', 'booleanCollection', 'currencyCollection', 'dateTimeCollection', 'dateCollection', 'decimalCollection', 'durationCollection', 'integerCollection', 'externalOrganizationCollection', 'externalAddressCollection', 'externalFacebookInfoCollection', 'externalFacebookIdCollection', 'externalLineInfoCollection', 'externalLineIdCollection', 'externalTwitterInfoCollection', 'externalPhoneNumberCollection', 'externalWhatsAppInfoCollection', 'externalContactCollection', 'jsonCollection', 'promptCollection', 'skillCollection', 'stringCollection', 'userQueueCollection', 'queueCollection', 'utilizationLabelCollection', 'wrapupCodeCollection', 'groupCollection', 'phoneNumberCollection', 'emergencyGroupCollection', 'scheduleCollection', 'scheduleGroupCollection', 'skillExpressionFilterCollection', 'issueInfoCollection', 'languageSkillCollection''.
        Path: '/inboundCall/tasks/task[Main_12]/actions/updateData[_^_archy_updateData_67__]/statements'
        Property name: 'customJson'

    when reviewing the .yaml flow export, it saves both the input and output JSON to the decision table as 'customJson', and this variable type is not inside the archy definition.

    Has anyone faced this issue and can provide some tips here?

    Thank you!

    Juan.


    #Archy

    ------------------------------
    Juan Tami
    PS Consultant
    ------------------------------


  • 2.  RE: archy create task not working when trying to create a flow that contains Decision Tables calling

    Posted 19 days ago

    Hi @Juan Tami,

    I have seen similar behavior when migrating Architect flows that contain Decision Table actions through Archy.

    Based on the error, Archy is failing during validation because the exported YAML contains variables of type customJson, while the Archy schema currently recognizes json and jsonCollection, but not customJson.

    A few things you may want to verify:

    1. Architect vs. Archy version compatibility
      • Decision Tables are a relatively newer Architect feature and sometimes the flow export contains internal data types that are not yet fully supported by the Archy validation model.
      • Make sure you are using the latest Archy release available.
    2. Review the generated YAML
      • Check the Decision Table input/output variables in the exported flow.
      • In many cases, you'll notice that Architect exports them as customJson even though the actual data structure is JSON based.
    3. Test replacing customJson with json
      • In a non-production copy of the YAML, replace the variable type definitions from customJson to json and try the import again.
      • Several users have reported success when the underlying payload is standard JSON and no strongly typed custom object is required.
    4. Validate Decision Table dependencies
      • If the Decision Table itself was created in Division A, ensure the equivalent Decision Table exists in Division B and that all references are correctly mapped before importing the flow.
    5. Open a Genesys Care case if reproducible
      • If the flow exports customJson directly from Architect and Archy rejects its own exported artifact without modification, that looks more like a product gap or defect than a flow configuration issue.

    As a quick test, try exporting a minimal flow containing only a Decision Table action and see whether the generated YAML still contains customJson. If it does, that would help confirm that the issue is related to the Archy parser rather than the specific flow logic.

    Please let us know which Archy version you are using and whether replacing customJson with json allows the import to complete.

    Regards, 



    ------------------------------
    Cesar Padilla
    INDRA COLOMBIA
    ------------------------------



Related Content