Skip to main content
Solved

API data show in popup grid

Tejo van de Bor
Captain
Forum|alt.badge.img+5

hi,

For a calculation module we use a 3rd party API, which gets us a json with +/- 10 records, the user has to pick 1 of these options. Each record has a unique code, this is the only field we actually have to store in our model.

So I thought of a processflow, starting from a task, get the json, show the data in a pop-up grid to the user, choose 1 record, save the code in our model, and we’re ready. Is this the proper way to do this? 

  1. Do we have to save all data from the json to the database to show it in a grid? We only need the selected code, the other data is on-the-fly but needed for the user to make the decision, is there a more temporarily way?
  2. How to popup the grid on top, so the user has to select a record to close the popup?

 

Best answer by Erwin Ekkel

How I would solve this: 

Store the JSON as a string in a table. 
In the process flow navigate to a view.
The view shows the JSON data mapped as a table.
On the view add a task to select and store the value of the chosen row. 
Set a tickbox: completed on the table with the json data. 
Continue with the process flow. 

(optional add a task to clean up the json data in the table after x days/months.)

View original
    P
    1 person likes this
    • P
      Peter van Leenen
    Did this topic help you find an answer to your question?
    This topic has been closed for replies.

    4 replies

    E
    Moderator
    Forum|alt.badge.img+17
    • Erwin Ekkel
    • Moderator
    • 768 replies
    • Answer
    • August 25, 2022

    How I would solve this: 

    Store the JSON as a string in a table. 
    In the process flow navigate to a view.
    The view shows the JSON data mapped as a table.
    On the view add a task to select and store the value of the chosen row. 
    Set a tickbox: completed on the table with the json data. 
    Continue with the process flow. 

    (optional add a task to clean up the json data in the table after x days/months.)

    Tejo van de Bor
    Captain
    Forum|alt.badge.img+5

    Thanks Erwin, never thought of a view getting the json data. Now I got the view showing (set the extended properties for floating document width), selecting the record and save the code.

    Still wondering how to continue with the initial process flow. By opening the document the flow is stopped right? Or can it be continued after executing the task in the view? e.g. after saving the code there are some extra things I’d like to execute.

    E
    Moderator
    Forum|alt.badge.img+17
    • Erwin Ekkel
    • Moderator
    • 768 replies
    • August 26, 2022

    Perhaps instead of showing the view. Start a second task that has a lookup to this view. This way you won't have to navigate to the view and can stay within the context of the process flow. 

    Tejo van de Bor
    1 person likes this
    • Tejo van de Bor
      Tejo van de Bor
    Tejo van de Bor
    Captain
    Forum|alt.badge.img+5

    Ah, thanks Edwin. The lookup option is indeed a beter way for handling the popup, and all steps are now in 1 processflow. Got it working now!

    E
    1 person likes this
    • E
      Erwin Ekkel
    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings