[eiresendez]

Issue & Reproduction Steps

A duplicate Script Executor name shows a validation error that stays visible after changing the name or language. Open Admin > Script Executors, enter an existing name for the same language, and select Save and Build. Then change the name or language.

Solution

• Clear the name error when the name or language changes.
• Clear the language error when the language changes.
• Clear previous errors before each save attempt. Keep server-side uniqueness validation unchanged.

How to Test

Browser smoke passed: duplicate names are rejected, changing the name clears the error, retrying a duplicate shows the error again, and changing the language clears the error.

Component checks passed for create and update retries with simulated API responses. Successful executor builds were not exercised.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-33960

[cursor]

PR Summary

Low Risk
Client-side error state only; server-side uniqueness validation is unchanged.

Overview
Fixes stale validation messages on the Admin Script Executor modal when a duplicate name/language save fails.

Watchers on formData.title and formData.language remove the corresponding entries from errors as the user edits (language changes clear both title and language errors, since uniqueness is per language). save() now resets errors before each build/save attempt so prior server errors don’t linger until the next failed response.

^{Reviewed by Cursor Bugbot for commit d9077d7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[decisions-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube