Expand APIs and better documentation
Better support for web services, etc.
In Winter 12 we have implemented new APIs:
Add/modify/delete notes
Add/modify/delete AB entries, including UDF
Support downloading documents
These and other APIs are documented as part of Customization Suite.
-
Ken Strickland commented
On the better documentation side, it would be nice to know ahead of time when structural or encoding changes to the database are made in major or minor version updates as some of these changes cause issues with direct SQL calls.
As for the reference web-site idea, I fully support this. Recognizing that Maximizer IS closed source, I understand that it would necessarily need to be limited to currently licensed users. However a central repository where your programmers and other customization users can make notes and generally help improve integration and functionality would be great.
Some more documentation on formula UDF's and what commands are recognized would be helpful too.
-
Paul Battaini commented
In response to "what areas", I agree with Web Services. Also better support for adding Triggers to Maximizer SQL Tables.
-
Paul Battaini commented
Areas of the API that are using latest technology should include at least one example for every single function/method/call. Ideally this should be made available on a reference style web-site like MSDN, PHP & Wp offer for example:
http://msdn.microsoft.com/en-us/library/ms189826.aspx
http://www.php.net/manual/en/
http://codex.wordpress.org/Function_ReferenceThese might even allow (moderated) comments and ability for other developers to post their own code snippets or findings when using a given area.
-
Frank Jaeschke commented
With each version documentation should include all changes to views and tables so partners and clients can track what has changed and easliy adjust any customizations that have been made.
-
Any specific areas that are more important for enhancements?