As long as the FME Server Playground still has examples on how to do everything using the API I would have no issue upgrading our clients. Particularly examples on how have the file drag and drop functionality, that is mainly where I start off using the JavaScript API.

I am trying to use a "Where" clause for the reader but it does not identify the field in the existing geodatabase. 

I have a Esri Geodatabase connection named vg_esri and I wanted to select a table named vg_esri.sde.mm_poly_gh and select a polygon wíth its id polygon_id = 852364, I have used 

SELECT polygon_id FROM vg_esri.sde.mm_poly_gh WHERE polygon_id = '852364';

Could not find the features in the table 'sde.mm_poly_gh'. One possible reason is that a WHERE clause was specified that references a column/field that does not exist in the table. The error number from ArcObjects is: '-2147216081'. The error message from ArcObjects is: {Invalid SQL syntax fERROR:  syntax error at or near ";"
LINE 1: ...FROM dg_esri.sde.mm_poly_gh WHERE polygon_id = '852364';)

But I get this above error, What am I doing wrong, I cannot figure it out. Any input will be very help. Thank you...

We run an internal javascript application that lets us monitor jobs, queue and progress - I use it daily to keep an eye on how things are going... !

Curious if the decision has been made to continue updating the Javascript API as I know v4 of the FME Server REST API is under development. I find it really useful to use.

@Chris Warren​  We are not planning to continue maintaining the JavaScript API, but have not yet made a formal announcement with more information. When available, it will be shared in the FME Community.

Thanks for the info. Maybe this could be a project for the FME community to maintain and develop. Having the JavaScript API does make it easier to work with the REST services, but it is by no means essential to have. This could be an opportunity to build different API-wrappers around the FME Server REST API for multiple programming languages.