History

sneha122 0377b37bbc fix: explicit automatic actions to be included in layout on load actions as well (#40778 ) ## Description This PR fixes an issue in reactivity where if we have configured any action to be automatic explicitly (By changing from settings in action editor), then this action was not getting included in the layoutOnLoadActions (This matrix informs frontend on what actions it needs to execute on page load). Since we want all automatic actions to be on page load as well, whatever actions user configure explicitly to be automatic, should be included in page load as well. This PR fixes that. Steps to test: 1. Create an app with 2 queries -> Query1 and Query2 2. Go to Query1 -> settings and change run behaviour to be automatic. 3. Bind this query Query1 to Table1 widget 4. Reload the page and see if the table is getting populated or not Fixes #40781 _or_ Fixes `Issue URL` > [!WARNING] > _If no issue exists, please create an issue first, and check with the maintainers if the issue is valid._ ## Automation /ok-to-test tags="@tag.Sanity" ### 🔍 Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/15318982252> > Commit: 0eca6f90a21ab10faaf7794a98567ccce4bef541 > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=15318982252&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.Sanity` > Spec: > <hr>Thu, 29 May 2025 08:24:56 UTC <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [ ] No <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Summary by CodeRabbit - Bug Fixes - Improved detection of actions set to run automatically on page load, ensuring both "ON_PAGE_LOAD" and "AUTOMATIC" run behaviors are now recognized. This enhances reliability for users who configure actions to execute when a page loads. - Refined the logic for identifying user-configured executables that should not run on page load, now accurately recognizing only those set to "MANUAL" run behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: “sneha122” <“sneha@appsmith.com”>		2025-05-29 15:01:06 +05:30
..
.run	feat: Databricks plugin (#29746 )	2023-12-26 10:04:09 +05:30
appsmith-git	fix: eliminate concurrency bug in file deletion logic by removing side effects from parallel stream (#40744 )	2025-05-23 12:34:58 +00:00
appsmith-interfaces	feat: backend changes for updating run behaviour to automatic (#40671 )	2025-05-21 13:31:17 +05:30
appsmith-plugins	chore: added automatic option to run behaviour behind feature flag (#40608 )	2025-05-16 16:29:31 +05:30
appsmith-server	fix: explicit automatic actions to be included in layout on load actions as well (#40778 )	2025-05-29 15:01:06 +05:30
envs	chore: Move signup_disabled and form_login_enabled from envs to DB (#39882 )	2025-03-26 11:26:00 +05:30
mongo-seed
reactive-caching	feat: Restrict cron execution for single pod in clustered environment (#39171 )	2025-02-25 17:20:11 +05:30
scripts	chore: Revert "chore: delete redundant files" (#35022 )	2024-07-18 16:18:10 +05:30
.gitignore	chore: Removed failed tests file from git (#29602 )	2023-12-14 13:02:36 +05:30
build.sh	test: Enable server tests for the PRs with base PG branch (#33429 )	2024-05-22 15:55:20 +05:30
buildpack-run.sh
pom.xml	chore: Added capability of running ITs on maven (#38354 )	2024-12-25 02:08:49 +05:30
Procfile
README.md
system.properties

README.md

Appsmith Server

This is the server-side repository for the Appsmith framework.

For details on setting up your development machine, please refer to this Setup Guide.