Task/FOUR-27119: Modify Task Edit to render iframe with smart extract URL after Operator clicks on HITL Manual Task

[CarliPinell]

Solution

TASK edit.blade.php file was modified to include an iframe to render Smart Extract Portal for Human in the loop process

Related Ticket

• https://processmaker.atlassian.net/browse/FOUR-27119
• Package Smart Extract PR

[cursor]

You have run out of free Bugbot PR reviews for this billing cycle. This will reset on November 21.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
21968551	Triggered	Generic High Entropy Secret	1588be9	ProcessMaker/Http/Controllers/TaskController.php	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[eiresendez]

The URL exposing the document has been removed from the codebase, but it still exists in the Git history since the commit containing it was already pushed. The document in question is a dummy file and does not contain any sensitive information. We can proceed with the PR and we’ll ensure to handle such cases more carefully in future commits.

cc: @CarliPinell @sanjacornelius

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube

[CarliPinell]

Thanks @eiresendez You're absolutely right, the oversight was mine, and I apologize for the error. Thank you for pointing it out and for the correction.

To prevent the URL data from being exposed, even if it's dummy data, I've redone the pull request with clean commits, removing the URL information with dummy data.

@sanjacornelius

[CarliPinell]

3. rotate this secret

Observation was fixed