Core platform implementation - phase 2

[carinanfonseca]

Objective

Enable Appsmith to turn on any integration on the Paragon dashboard within one day.
Below are the milestones for implementing native SAAS integrations in Appsmith using Paragon.

Core platform implementation

Preview Give feedback

1. Multiple Envs Enablement for External Saas Integrations
2. Optimisation - LRU Caching in CS for Paragon token
3. Headless connect API integration (Not Supported by Paragon, hence marking as closed)
4. UQI Conversion logic
5. Populating Enabled Integrations from Paragon in CS & Appsmith Server
6. Automated mech. for UQI conversion, storage and population in CS and Appsmith Server.
7. Custom Action Implementation
8. Feature flag implementation in CS for enabled integrations based on business plan
9. Feature flag implementation in EE based on license type (business, enterprise, free plan)
10. Create a strategy for Overriding UQI config
11. JUnit, Jest & Cypress Tests
12. Logging API metrics to NewRelic and error logs to Sentry
13. Enable JIRA
14. Enable Slack
15. Used defined UQI (Showing custom attributes for salesforce, JIRA)

(Reference: Paragon Engineering Implementation doc)

Success Metrics

The ability to successfully activate an integration on the Paragon dashboard and use it in the Appsmith IDE, with 100% functionality validated for at least four integrations: Salesforce, Zendesk, Slack, and JIRA.

Prioritised User Stories

User Story
As a user, I want to easily find new integrations, so I can quickly explore and choose the one I need.
As a user, I want to authenticate seamlessly with an integration, so I can securely connect my account.
As a user, I want to write queries on the datasource, so I can interact with it consistently, like with other SaaS datasources.
As a user, I want integrations to perform reliably and maintain high quality, so I can use them confidently without disruptions.

Developer Handoff Document in Figma

No response

Test Plan

No response

RACI matrix

Role	People
Responsible	@NilanshBansal @AmanAgarwal041
Accountable	@NilanshBansal @AmanAgarwal041 @carinanfonseca
Consulted	@nerbos @carinanfonseca @Nikhil-Nandagopal, @mohanarpit
Informed	@areyabhishek