Publishing & Testing Your Application

Make your Rayven application live and ensure it performs as intended.

Overview

Once your Rayven application is configured—including tables, workflows, interfaces, and users—the final step is to test and publish it. This process ensures that all logic executes correctly, interfaces display the right data, and permissions behave as expected for different user groups. In Rayven, publishing an app doesn't mean deployment to a new environment—it means it is now live for the intended Application Users.

Publishing and testing are ongoing activities throughout the build process, but this article outlines the steps to take when you're ready to conduct structured testing and move toward release.

Testing Your Application

Before publishing, validate that your app behaves as expected. This involves simulating real usage scenarios, verifying data processing, and ensuring front-end layouts are correct for different users.

1. Test with Application Users

To simulate the actual user experience:

• Create test users in your Users section of the Workspace.

• Assign these users to appropriate User Groups with defined label filters and interface access.

• Log in to the App Interface via https://app.rayven.io using test user credentials.

• Confirm:

  • Interface access matches group permissions

  • Widget layout and data visibility are correct

  • Label-based filtering behaves as expected

2. Validate Widget Display

• Confirm that all widgets render as intended in the App Interfaces.

• If using prebuilt widgets:

  • Validate data appears in real-time or as expected from workflows.

• If using custom widgets (via UI Code Node):

  • Check rendering, styling, and interactive elements.

3. Debug Workflow Execution (if needed)

While most workflow logic should be tested and validated during the build phase, you can still inspect runtime behaviour using the Inspect Data tab:

• Use this tool only if you encounter unexpected outputs or want to verify that a particular input is processed correctly.

• View incoming and outgoing payloads at each node.

4. Review Label Filtering Behaviour (if applicable)

If your application uses labels to segment data access:

• Log in with users from different User Groups and confirm the data displayed matches their assigned label filters.

• If no label filtering is configured, this step can be skipped.

Publishing Your Application

Once tested and validated, your application is effectively “published” and live. In Rayven, there is no separate deploy step—what you build in the Workspace becomes live for users with access.

Key Steps:

• Ensure All Required Users Are Created: Add final users to the correct user groups and confirm login credentials.

• Assign Interface Access: Double-check that each user group has access to the intended interfaces.

• Confirm Permissions: Review permission levels (e.g. Super Admin, Editor, Viewer) for each user.

• Interface Locking Defaults: Interfaces are locked for all new users by default, because the Edit Interfaces and Edit Widgets options are not enabled when a user is first created. Only users explicitly granted these permissions can rearrange or edit widgets.

• Notify Users: Share login URLs, credentials, and usage instructions.

Summary

Publishing your application in Rayven is a straightforward process once you’ve thoroughly tested your configuration. Testing should simulate real usage across all user groups, workflows, and front-end components. Because applications are always live to assigned users, care should be taken before adding real users to groups or sharing access links.

FAQs

What happens when I update an application that’s already live?
Changes to workflows, interfaces, or user configurations apply immediately. Always test thoroughly before making updates in production environments.

Can I preview an interface before assigning it to users?
Yes. You can create a temporary User Group with access to only the new interface and test it yourself using a test user.

Do I need to publish interfaces separately?
No. Once interfaces are added and assigned to user groups, they are automatically available to those users.

How do I lock the layout of a page so users can’t move widgets?
By default, interfaces are locked for all new users because the Edit Interfaces and Edit Widgets permissions are not selected when creating a user. To prevent users from modifying widget positions, ensure those permissions remain disabled in the User settings. Only users with these permissions will be able to move or resize widgets on the App Interface.

What’s the difference between publishing and deploying in Rayven?
Rayven does not require a separate deployment step—changes made in the Workspace are live for users based on access and group settings.