This idea proposes an optional feature to export an OML as a read-only .NET project for inspection and analysis purposes.

 Export  all quizzes  for a given course , so we will have the possibility of having another "exam example" for a course/certification , this document that would be exported could be separated by topics or randomly separated.This is a great idea, to be able to export and have another way to study, besides the Sample Exam  in each different certification.

if someone wants to clean data in table or clean whole database we don't have any action in entities actions like (create,update,createorupdate,delete,...) we should have deleteall action which will delete all the records based on some permission parameter  .we can use delete action but here we have to use for loop for iteration every record.

Implement a real-time collaborative environment where multiple developers can work on the same application simultaneously, similar to Google Docs. This would enhance teamwork and reduce version control issues.

Currently, when dragging a table to create an interface using scaffolding, two screens are generated: one for the record list and another for editing. This results in the use of two application objects. Would it be possible to support a master-detail pattern using a single screen for the record list and a popup for editing or inserting a record?

Add a Basic Data Type named Timestamp that retrieve time in milliseconds, this way it is possible to calculate time or date time with milliseconds.This is very useful in audit or logs, or even in a transaction level situation when having multiple users using the same entities or records.There are some forge components to do that, but that will imply a server call, or extra logic to fetch this type ofdata.

Currently, the Forge component pages have tabs like Overview, Reviews, Versions, Documentation, and Support. Adding an “Improvements” tab would allow developers to share enhancement ideas, suggestions, and feature requests directly with the component creators. This will help Forge makers understand what the community needs most, plan better updates, and evolve their components into more complete, community-driven solutions

I recently passed one of the online exams and I didn't notice any timers and question counters on the page. Since proctors want a clean desk, one monitor, no devices it's practically impossible to track your time during the exam. Is it possible to add a 'time left' section somewhere on the page or did I just miss it?

The Regex_Replace  and Regex_Search actions from the Text  library could be added to the Built-in Functions in order to be used in AggregatesThis would help in scenarios of result filtering and in-query data obfuscation.Thank you.

 Problem Description When working on complex action flows in Service Studio, it’s often hard to visually identify the main path, the sequence that runs when everything goes right and no exceptions are thrown. Once an action starts to grow with multiple if nodes, exception handlers, and different branches, all the lines look the same. This makes it difficult to quickly understand: Which path is actually executed most of the time Where to safely add new logic Where performance-heavy steps should go How the flow is intended to run under normal conditions This becomes even more confusing when maintaining someone else’s work or revisiting a module after a long time. Idea / Proposed Solution It would be extremely helpful if Service Studio allowed us to highlight or mark the main execution path inside an action flow. Some possibilities: Manually select certain steps and mark them as the “main flow,” so they get a subtle color or visual emphasis Dim non-main branches for easier reading Add a toggle to show/hide highlighted paths Or even allow Studio to auto-suggest a main path based on the straight-through execution sequence Even a small visual cue would make a big difference when reading or designing large flows. I believe this small enhancement would significantly improve the experience of working with complex action flows, especially in enterprise-scale applications.