Hi John,

Thank you for your question.

Thanks for the response.

Although the APEX Code for managed packages are hidden, we do add custom fields and triggers and workflows, etc. based on these objects.  If we are to use the Welkin Suite to integrate our environment with Git, we need ALL of our updates and changes, including these.  

Regards,

John Harcourt

Hi John,

Thank you for your use case.

We will consider these details during the implementation process.

Right now I cannot tell you when this will be added to the TWS functionality.

I'll keep you updated about this.

Regards,

Kate

Hi Kate,

Any update on managed package object functionality? I work for a managed package vendor and perform custom implementations in our customer's orgs against our managed package. This functionality is extremely important for me, as I primarily work on extending our managed package objects.

I'm an old C# developer, so I was very excited to see your product at Dreamforce in 2016. Unfortunately, not being able to download package object metadata is a deal killer for me. We have several other developers here with similar backgrounds that are in the same boat.

Right now I am using the trial version, but I won't be able to justify buying a license until I can use this feature. Would it be possbile to restart my 30 day trial once this feature is supported?

Best Regards,
Scott Mercer

EDIT: I forgot to add that I am using Spire R3 Version 1.0.31.4 for Windows. Operating system is Windows 10.

Hi Scott,



Thank you for your post and for the details of your workflow which are related to the current feature request.

May I please clarify with you what exactly is necessary for you from managed packages? Do you use the interfaces for global classes or you are interested in sObjects? If your goal is sObjects, can you please tell me if they are important for you for suggestions in Apex files or you work on editing their xml files?

The reason for my questions is that right now we are starting our work on declarative development inside The Welkin Suite IDE, and the work with objects is our main direction in a frame of this extension of the IDE functionality. We are going to implement all the missed and required options in near future. The further part of the work will include getting an access to manage package objects. In addition, this will help us to solve the issue when objects are absent in the Code Completion suggestions.

As for your trial license, we will keep this in our mind. In general, we have some ideas and visions about extending or refresh of trial licenses. Currently, we discuss this to find the best opportunity for our users to use the test period for The Welkin Suite IDE.

Thank you,

Kate

Hi,

we also have a similar problem.

A primary concern would be intelliSense on sObjects in managed packages (and also to view them in the object browser, that should be a no brainer once you aquire the metadata). Having to type namespace prefixes is extremely annoying. The IDE could be of great help here.

Best regards,

Florian

Hi Florian,

Thank you for letting us know about your use case - this information is helpful for us. This feature is still in our roadmap for the nearest future and we are going to implement it in a month or two if nothing won't change.

Thank you,

Vladimir

Hi Kate,

I didn't see an answer from Scott above when you asked for some additional details, so I'll add some answers for our needs

My company has several managed packages we sell.  And my team is responsible for extending the functionality those managed packages.  For example, we use the standard Opportunity class, but then we have custom objects for RFP, PROPOSAL, etc that are part of the managed package.  Those managed package is all under the namespace of "NICX".  When I pull down source frrom Salesforce, none of the NICX objects are pulled down.  Those objects have custom fields that we've added for specialized customizations.

We do also use global interfaces, to allow certain classes to be modified (ones tied to Site pages for example).

Hope this helps.

George

Hi George,

Thank you for your detailed answer with the examples.

We will implement the functionality that will cover the case you've described. 

Righ now I cannot tell you when exactly this will be done, however, we will work on this during the nearest months.

I will keep you updated on the process of the implementation this feature.

Thank you one more time

Kate

Same use case as John Harcourt above. 

Any updates on this feature? Have worked with TWS for about two hours and I love it. Unfortunately the lack of this feature means I can't actually use it for work. 

Any updates on this? I'm on a trial and a huge fan so far. However, I just realized I can't view/edit the field-level security for fields on a custom object that is part of a managed package. I'm hoping this has been added and I'm just missing a new setting.

Hi guys,

Thank you for your posts.

We have included implementing this functionality to our October's sprints.

I will keep you updated when files from your managed packages will be accessible in The Welkin Suite Bloom.

Thank you for your collaboration.

Best Regards,

Kate

Hi guys,

 

I'm happy to inform you that we have implemented the support for managed packages in The Welkin Suite Bloom R12.

Now you can add the necessary files from your packages to your TWS project.

Also, the code completion suggestions will include global classes, sObjects and their fields from downloaded managed packages.

 

 

We will be happy to hear your feedback or any other new suggestions!

 

Best Regards,

Kate