Server-Side Requirements Data file Views - Simple, Easy and Effective way to share!

 

Server‑Side Offline Data File Views introduce a simple but transformative capability to OpenRose: the ability to host exported project data directly on the server and make it instantly accessible to any authorized user. This dramatically improves how teams share information, collaborate, and maintain visibility across projects.

Here are the key reasons this feature stands out:

Zero‑Complexity Hosting

You export a JSON file and place it in a server folder. That’s it.

Accessible to All Team Members

Anyone with access to the OpenRose instance can open the hosted file—no emailing, no file transfers, no setup.

Perfect for Non‑Technical Contributors

If someone can write Markdown, they can create content that can be exported and hosted.

Centralized and Always Available

Hosted files remain accessible even if the SQL Server or API layer is offline.

Ideal for Documentation and Reference Material

Requirements, onboarding guides, snapshots, and structured notes can all be hosted as static JSON files.

Fast to Update

Export → Upload → Instantly available to everyone.

Great for Distributed Teams

No syncing, no version confusion, no dependency on local files.

No Load on SQL Server or API

Offline files behave like local copies, avoiding heavy queries.
“You’re not sending too many large queries… it’s pretty much like a local copy of your project.”

Introduction

OpenRose now includes Server‑Side Offline Data File Views, a powerful capability that makes sharing structured project information easier, faster, and far more accessible. Teams can now host exported JSON data files directly on the server, allowing any authorized user to browse the content in a read‑only, safe, and familiar interface—without needing a live connection to the backend repository.

This feature is especially useful for sharing requirement snapshots, documentation, or reference material with stakeholders who don’t need full editing access. It also ensures that important information remains available even during maintenance windows or backend outages.

Demonstration Overview

To illustrate how the feature works, the demo uses a sample Stock Trading Platform application. The project contains several categories of requirements:

• Business requirements
• User requirements
• Functional requirements
• Non‑functional requirements
• Security requirements

Each category includes multiple levels of a requirements breakdown structure.

While connected to the live system, the user can edit, restructure, and update these requirements. But the goal of the demonstration is to show how the same information can be exported and hosted in a read‑only offline mode.

Exporting Project Data

OpenRose allows exporting:

• The entire project
• A specific item type (e.g., User Requirements)
• A single requirement and its children
• A baseline snapshot

These exports generate compact JSON files.

In the demo, the presenter exports the User Requirements item type:

“I’m selecting the ID of user requirement item type… and export this data out using item type option.”

The exported file is then placed into the server’s configured offline‑file directory.

Hosting the File on the Server

Once the JSON file is uploaded to the server folder:

• There is no need to email it
• No need to share it manually
• No need for users to download anything

Anyone connected to the OpenRose instance can open the hosted file directly.

“You don’t need to email them… you just host your scoped data on your own server.”

This makes it extremely easy to distribute scoped project information to large groups.

Opening the Hosted File

Users open the file through the Server Data File View option. When they do:

• The requirement tree loads
• Items can be expanded and browsed
• Traceability links work
• Parent/child relationships are visible
• All content is read‑only

This ensures safe, consistent visibility without risking accidental edits.

What Happens If the API or SQL Server Goes Down?

One of the most impressive parts of the demonstration is when the presenter stops the API service entirely.

When the API is offline:

• Live project data disappears
• The UI shows a connection‑lost warning
• No SQL Server access is possible

Yet the server‑hosted offline files continue to work perfectly.

“My server data file are still available… I should still be able to go and open the file.”

This means:

• Documentation remains accessible
• Requirements remain visible
• Reference material stays online
• No backend load is generated

It’s a powerful resilience feature for teams.

Client‑Side vs Server‑Side Offline Files

OpenRose supports two offline modes:

Client Data File Mode

Users open a JSON file stored on their own device.

Server Data File Mode

Users open a JSON file hosted centrally on the server.

Both modes work even if the API and SQL Server are offline.

“I still can work with offline data whether it is the client side data or the server side data.”

This flexibility is ideal for distributed teams and external collaborators.

Multilingual Support

The demo also shows that multilingual requirements work seamlessly in server‑side offline mode:

“We have support for multilingual requirements… and it works beautifully with the server JSON data file mode.”

Returning to Live Mode

Once the API service is restarted, the UI reconnects automatically. Users regain full access to:

• Editing
• Creating new items
• Moving data
• Import/export
• Baselines
• All live project features

Switching between live and offline modes is smooth and intuitive.

Conclusion

Server‑Side Offline Data File Views bring a new level of simplicity, resilience, and accessibility to OpenRose. Whether you’re sharing requirement snapshots, publishing documentation, or ensuring availability during backend downtime, this feature provides a safe, fast, and reliable way to distribute structured project information.

OpenRose, a free and open-source requirements management application / tool. For more information, visit 

https://github.com/openrose