-
asmith posted an update in the group
Rest 4 years, 9 months agoDid you know: in Omnis Studio 8.0.2 support for ISO8601 based date and date-time values was added to REST-based Web Services; in addition, the CORS settings are now stored in a separate config file CORS.json rather than the main Omnis config.
-
Lou Picciano posted an update in the group
Rest 4 years, 10 months agoThe new RESTful features in Omnis will open up a world of possibilities…
- Load More
show less
show more
Public Group
active 1 year, 5 months agoGroup Admins
Restful coding
Recent Replies
Recent Topics
-
Scorrere un lista orizzontalmente
by
Lorenzo Pisarri
1 month, 1 week ago -
Convert Microsoft Access to Omnis
by
Paul Mulroney
1 month, 3 weeks ago -
Getting the page number that an object is on, inside a $sendall
by Paul Mulroney
1 week, 6 days ago
-
keyboard state
by
Joel Thibaux
1 week, 6 days ago -
$10.2 $getdrivers()
by
Denis Woodbury
3 months ago
Recently Active Members
Question: why is the CORS.JSON not created automatically during installation of Studio?
Greg – the default is to not have CORS setup, so no file is on place, but I guess we could create the file template and place it in a sub-folder of the ‘studio’ folder, which would then require you to move it to the Studio folder to enable CORS. I will enter an Enhancement Request to this effect.
This would be a good for developer I think. Currently the note about the CORS.JSON is buried in the manual and one has to copy/paste the content from PDF to create the file, this leads to formatting problems that cause the file not take any affect.
Greg – added an ER as ST/WS/284 – I’ve suggested that we create a sub-folder in the ‘studio’ folder called ‘config’ and place a template CORS.JSON file in there – you would then need to move it into Studio to enable CORS.
That is very nice. Now, can we call this new subfolder “config_template” instead?
This would be more intuitive as the name says clearly what the purpose of this subfolder is.