I also think the first approach will be good. Regarding the migration i
think all published APIs wont have any impact due to this migration.
APIs in prototype state should be in prototype state after migrating. So if
existing deployment migrated to 3.2.0 there will not be any changes in APIs
and
Hi Kasun,
On Wed, Apr 22, 2020 at 9:17 AM Kasun Thennakoon wrote:
> Hi Hasunie,
>
> Out of the above three suggestions, I'm +1 to the 1st approach you have
> suggested, Where
>
>
>- Combination of *prototype *state and *enableStore=true*(API artifact
>property) will depict the *testing*
Hi Hasunie,
Out of the above three suggestions, I'm +1 to the 1st approach you have
suggested, Where
- Combination of *prototype *state and *enableStore=true*(API artifact
property) will depict the *testing* state
- *enableStore *property will control the visibility in the developer
Hi All,
We have been working on a testing console for the API Publisher. The main
> intention of this feature is that the developer(creator, publisher) can
> make sure that the API is working as expected by performing functional
> tests before publishing to the dev portal.
> For example, test
Hi all,
We have been working on a testing console for the API Publisher. The main
intention of this feature is that the developer(creator, publisher) can
make sure that the API is working as expected by performing functional
tests before publishing to the dev portal.
For example, test the
