Closed mtebusi closed 8 months ago
Hello @mtebusi , thank you for submitting an issue we appreciate your time. We will take a look and give you an update as soon as we can. We aim for a 72 hour response time.
Thanks for raising this @mtebusi. I have never spent any time investigating this but have raised a case with Salesforce to ask what might cause this. In theory, Professional Edition Orgs should be supported by managed packages that have been through a security review - but will ask Salesforce.
I'll update their response here. No ETA.
Thanks a ton! And happy to beta test with my client. They are in love with the app / I shared how we would use it at Salesforce in the SDO.
Okay @mtebusi Salesforce needed to add a permission to the packaging org to support Professional Edition.
They tell me they've done it so it should now be working.
Do you want to try and install in a PE org - since seeing is believing?
You're my hero @deejay-hub
Is your feature request related to a problem? Please describe. I have a client that is currently on Professional Edition of Salesforce (with API access add-on) and is very interested / excited about the possibility of the Time Warp application. Upon install, it returns a few errors related to Enterprise-specific features that are not enabled in the destination org. I understand that there may be reasons that this is suited for Ent only, but curious if there are a few small tweaks that could potentially enable this for all Professional Edition users?
Describe the solution you'd like Allowing the deployment of the application to Professional Edition orgs by modifying key components that are preventing install currently. Namely, the following Apex Classes which throw the following error:
Installing this package requires the following feature and its associated permissions: Apex Classes.
Classes referenced during install include:And (understandably) all following references to TimelineService throw errors due to the previous feature errors as well:
Describe alternatives you've considered Potentially allowing for deployment of the application without activation of those specific dependencies or features, and then allowing some sort of UI 'checkbox' that would enable them within the application.
Additional context N/A