You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we create a new API (or Soap Service) on a brand new installation of GReg, after succeeding on artifact creation , the application goes to the screen that list existing artfacts but nothing is shown..The API that i just created is not listed.
If we click to go to Home screen and go back to the screen that list that artifact, it is shown.
This kind of behavior creates a bad feeling on our customers because Greg says that creation operation was successful but it is not listed at first time.
Steps to reproduce:
Go to /publisher and hit add SOAP Service
Do the creation and confirm.
Greg goes to screen listing existing itens (Here is the error. The item that i just created is not listed.)
The text was updated successfully, but these errors were encountered:
HI,
This is the expected behavior. Once the asset is created it takes some time to index the asset. So sometimes the Solr search does not return newly created asset in the soap service list. Anyway if you are using G-Reg 5.3.0 , there is an notification appears in the top giving you the link to the newly created asset.
Hi,
When we create a new API (or Soap Service) on a brand new installation of GReg, after succeeding on artifact creation , the application goes to the screen that list existing artfacts but nothing is shown..The API that i just created is not listed.
If we click to go to Home screen and go back to the screen that list that artifact, it is shown.
This kind of behavior creates a bad feeling on our customers because Greg says that creation operation was successful but it is not listed at first time.
Steps to reproduce:
Go to /publisher and hit add SOAP Service
Do the creation and confirm.
Greg goes to screen listing existing itens (Here is the error. The item that i just created is not listed.)
The text was updated successfully, but these errors were encountered: