fix businessflow activity screenshot

[sudarshan0212]

Thank you for your contribution.
Before submitting this PR, please make sure:

• PR description and commit message should describe the changes done in this PR
• Verify the PR is pointing to correct branch i.e. Release or Beta branch if the code fix is for specific release , else point it to master
• Latest Code from master or specific release branch is merged to your branch
• No unwanted\commented\junk code is included
• No new warning upon build solution
• Code Summary\Comments are added to my code which explains what my code is doing
• Existing unit test cases are passed
• New Unit tests are added for your development
• Sanity Tests are successfully executed for New and Existing Functionality
• Verify that changes are compatible with all relevant browsers and platforms.
• After creating pull request there should not be any conflicts
• Resolve all Codacy comments
• Builds and checks are passed before PR is sent for review
• Resolve code review comments
• Update the Help Library document to match any feature changes

Summary by CodeRabbit

• New Features
  • Introduced a new JavaScript file for enhanced functionality in the web client.
• Improvements
  • Updated the main JavaScript file reference in the HTML to the latest version, ensuring users benefit from the most recent updates and features.
• Asset Management
  • Enhanced management of project assets, including updates to CSS and image files, for improved performance and organization.

[coderabbitai]

Walkthrough

The changes in this pull request primarily involve updates to the project file GingerCoreNET.csproj and the HTML file index.html within the Ginger Web Client. A new JavaScript file has been added, and existing resources have been modified to ensure they are copied to the output directory. The script source in the HTML file has been updated to reflect the new JavaScript version. Additionally, several files have been removed from compilation, indicating a reorganization of project assets.

Changes

File Path	Change Summary
Ginger/GingerCoreNET/GingerCoreNET.csproj	Added main.50dca4a1d8ae08b9.js to project with "Always Copy" directive; updated ItemGroup.
Ginger/GingerCoreNET/Reports/Ginger-Web-Client/index.html	Updated script source from main.2ad51ab896990d24.js to main.50dca4a1d8ae08b9.js.

Possibly related PRs

• fix vrt artifact issue #3965: This PR involves significant modifications to the project file and asset management, including updates to JavaScript and CSS files, which directly relates to the changes in the main PR.

Suggested reviewers

• Maheshkale447

Poem

In the garden where code does bloom,
A new script dances, dispelling gloom.
With files rearranged and paths anew,
The web client shines, fresh as the dew.
Hops of joy in the code we see,
A patch of wonder, oh, let it be! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)

Ginger/GingerCoreNET/GingerCoreNET.csproj (3)

Line range hint 255-257: Update MongoDB.Driver to address security vulnerabilities

The current version (2.19.1) of MongoDB.Driver has known security vulnerabilities. Consider updating to the latest stable version (2.24.0) to address these issues.

-    <PackageReference Include="MongoDB.Driver" Version="2.19.1" />
+    <PackageReference Include="MongoDB.Driver" Version="2.24.0" />

---

Line range hint 586-590: Consider removing empty folder declarations

The following empty folders should either be populated with implementation files or removed to maintain a clean project structure:

• ActionsLib/UI/UI Element/
• Reports/Ginger-Web-Client/assets/artifacts/
• SolutionRepositoryLib/RepositoryObjectsLib/PlatformsLib/

---

1240-1242: Optimize file copying settings

Consider using CopyToOutputDirectory="PreserveNewest" instead of "Always" for the JavaScript file to improve build performance. "Always" copies the file on every build, while "PreserveNewest" only copies when the source file is newer than the destination.

     <None Update="Reports\Ginger-Web-Client\main.50dca4a1d8ae08b9.js">
-      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
+      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
     </None>

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d8c96c4 and e711c36.

📒 Files selected for processing (2)

• Ginger/GingerCoreNET/GingerCoreNET.csproj (1 hunks)
• Ginger/GingerCoreNET/Reports/Ginger-Web-Client/index.html (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• Ginger/GingerCoreNET/Reports/Ginger-Web-Client/index.html

🔇 Additional comments (1)

Ginger/GingerCoreNET/GingerCoreNET.csproj (1)

1240-1242: ⚠️ Potential issue

Remove the old JavaScript file reference

The old version of the JavaScript file (main.2ad51ab896990d24.js) should be removed since it's being replaced by the new version (main.50dca4a1d8ae08b9.js). Having both versions in the output directory could lead to confusion and potential runtime issues.

-    <None Update="Reports\Ginger-Web-Client\main.2ad51ab896990d24.js">
-      <CopyToOutputDirectory>Always</CopyToOutputDirectory>
-    </None>

Likely invalid or redundant comment.