Skip to Main Content
InterSystems Ideas

Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.

The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.

💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.

🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.

Start by sharing what could be better - the community and our teams will help take it from there.

Status Ideas Contest
Categories Documentation
Created by Pierre LaFay
Created on Dec 21, 2023

Best practices in a documentation chapter

I think it would be interesting to address in a chapter of the documentation good practices both in programming and in the design of persistent classes.

It would be ideal to present some code examples.

Some examples to illustrate my point:

How to transform a data transfer Object (dynamic object) coming from a Rest API to create a persistent object?

How to implement design patterns (factory, facade, query-builder, etc.)?

In which case to favor the object approach of persistent classes over the SQL approach and vice versa.

  • ADMIN RESPONSE
    May 9, 2025

    Thank you for submitting an idea for the Ideas contest. The status changed to "Ideas Contest".

    Please answer the experts' clarifying questions, if any, during the contest and voting period.

  • Josh Lubarr
    Dec 3, 2024

    LS Documentation management reviewed this. We agree that having more best practices is a good idea.

    Given the extremely wide breadth of our content, we would want to add specifics in particular areas. Further, we don’t have this information available to us, so an authoritative source would need to provide it for each area -- this is in part because we sometimes get conflicting information from multiple parties and are not the arbiter of such decisions. If anyone has specifics that they'd like us to add, they should contact PM or Dev Mgmt for the relevant area to move forward.