Connect Platform (OCP)

Problem: App settings form are defined in static YAML files. The only way to make them dynamic is to hide some of the form elements and unhide them based on some rules. This has its limitations as all hidden elements must be defined in the YAML fi...

Problem: Sometimes it is not possible to register OCP webhook URL in third-party service, e.g., because a third-party service uses static URL and identifies an account by some piece of information from header or request body. This forces OCP devel...

Problem: developers are unable to test global functions of app already in production. Additionally, dev versions of an app can override a global function of already deployed beta version Solution: allow testing of global functions Impact: making d...

Problem It currently takes prospective OCP developers 10-15 days to get on board and ready to use OCP. The process of getting an ODP sandbox, partnership approvals, and then keys for an OCP API is long and confusing. Scope Anything with in BB8’s c...

Problem: Testing an app version in a sandbox account requires few steps now: bumping dev version (can be automated with a flag to ‘ocp app prepare’), building and publishing (can be one command), installing to test account or waiting for auto-upgr...

Problem: OCP app settings form elements can now be placed only one under another. This is sometimes not enough. One common example is a form that would map fields from one service to another – such form requires a table layout Solution: Allow tabl...

Problem We have a variety of models for presenting apps, integrations, and the associated information about each of them. Our experience is confusing for our customers and end users, leading them to make poor decisions, or possibly a choice not to...

Problem OCP apps are not publicly discoverable. They can only be found today by an authenticated ODP user. We believe this will impact adoption and use of OCP apps by our customers. Scope OCP App Directory (not public) com/apps: https://www.optimi...