FOUR-32268: [SPIKE] Add runtime Smart Extract configuration#8908
Draft
eiresendez wants to merge 1 commit into
Draft
FOUR-32268: [SPIKE] Add runtime Smart Extract configuration#8908eiresendez wants to merge 1 commit into
eiresendez wants to merge 1 commit into
Conversation
|
eiresendez
marked this pull request as draft
July 17, 2026 15:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.





Issue
Smart Extract currently resolves its dashboard URL, API host, OAuth credentials, and HITL flag from deployment-time configuration. FOUR-32268 is a Spike/PoC to validate whether authorized administrators can manage these settings through ProcessMaker Environment Variables and have updates applied on the next request or queue job without a deployment, configuration-cache clear, or worker restart.
Solution
SmartExtractConfigurationservice that lazily loads and decrypts the five Smart Extract settings in one query per request or job lifecycle.SMART_EXTRACT_API_HOSTloaded from Environment Variables in both local Docker and script microservice runners instead of overwriting it from Laravel configuration.How to Test
Run:
Expected result:
53 tests, 504 assertions.Manual end-to-end validation was completed successfully by updating the Smart Extract Environment Variables, verifying the next web request, and verifying a subsequent job on an already-running worker. The local Docker executor also completed the Smart Extract flow successfully.
Related Tickets & Packages
ci:package-smart-extract:spike/FOUR-32268