Request to Reintroduce and Enhance Resource Sharing Functionality

Comments

6 comments

  • Scott Henderson CTO
    Celigo University Level 1: Skilled
    Answer Pro
    Top Contributor

    Hey James Hamilton, the ability to reuse an existing export/import is not going away ever. We just moved the decision to reuse vs clone onto the next page, after you select the connection. See pic below. Also, please see here for an overview why we made these changes, and the direction we are heading in the next 2 months, etc...

    0
  • James Hamilton

    Gotcha, thanks for the swift reply.

    I do believe this is a bug in my instance as I'm given only the option to select an application and then "create from scratch" or select existing steps for that application/connector type from within my account; there is no option to select an existing step. In any event, the step should follow choosing a specific application connection/creating a connection, not after. So I'll submit a ticket to investigate why my Celigo instance is behaving differently than you're describing.

    Thanks,

    James.

     

    0
  • Scott Henderson CTO
    Celigo University Level 1: Skilled
    Answer Pro
    Top Contributor

    There shouldn't be any bugs (as of this morning). Here are the exact steps you should take to reuse an existing step.

    1. First, you need to select an existing step using our new UX, and click on next. See 1st pic below.
    2. Second, you need to pick the connection that you want to use for that existing step. See 2nd pic.
    3. Only after you select a connection, the option to clone vs use existing will dynamically display (i.e. when the new connection selected matches the connection on the existing step, etc...)

    0
  • James Hamilton

    Thanks, again. This did indeed capture some of the functionality but there are still some broken elements here. See GraphQL connectors as an example.

    • If I want to use an existing resource that is created using the GraphQL application, I have to access it via the HTTP application type. Being that GraphQL steps are simply HTTP requests with a different form view, this somewhat makes sense but is unintuitive.
    • If I do manage to locate the HTTP step that I need among the 100s that exist in my account (again, this problem is exacerbated by the classification of the flow steps as HTTP even if created using the GraphQL form,) then I continue to the next step where I'm able to select the connection. Here, I'm not getting the "How would you like to use this step...." radio buttons, and, in addition, the variables are missing in HTTP form view and they don't return when switching to GraphQL form view. 

    It seems to me like this update was intended for a streamlined flow builder experience that can help less experienced users, but in the example above, it takes a fairly robust understanding of the Celigo process to even access an existing GraphQL flow step (knowing to use HTTP instead of GraphQL,) and even then I'm not met with the functionality I need. 

    I'll eagerly await the return of the search functionality but would really like to see if there's a way to balance this new UI and "step before connection" idea with the existing "connection ---> step" hierarchy which was used before. 

    No GraphQL Steps available

    The existing step, shown in an existing flow.

    0
  • Scott Henderson CTO
    Celigo University Level 1: Skilled
    Answer Pro
    Top Contributor

    We will look into the GraphQL issues asap. Stay tuned.

    0
  • Scott Henderson CTO
    Celigo University Level 1: Skilled
    Answer Pro
    Top Contributor

    I just got an update from engineering that the GraphQL search issue is fixed.

    0

Please sign in to leave a comment.