Hi,

Thank you for bringing this issue to our attention.

The reason for this is the next: 

This is related to changing a process builder's name when you change its status to active: when you create a process builder file on your Salesforce Organization, it is inactive and its name contains the suffix with the version, and when you make this process builder active - the suffix is removed.

The IDE doesn't handle this correctly and this is why you can download to your TWS project process builder files which have the default name only. in other words - only inactive ones. Our developers will work to solve this issue.

I will let you know when you will be able to pull your active process builders.

If you have any other questions, please share them with us. We will be happy to assist.

Regards,

Kate

Hi,

Any update on this?  we have quite a few active flows and having the ability to find fields used in these via metadat search is a common use case for our org. Currently evaluating TWS on a 30 day trial...

thanks,

shyz

Hi Shyz,

Thank you for your post.

This is still included in our plans, however, right now I cannot tell you when exactly we will work on this.

I will keep you updated when this issue will be solved.

Regards,

Kate

Hi Katie - is there any update to this please? It's 6 months since the last comment on this thread and this is still an issue. I cannot retrieve active processes from our Salesforce org using Welkin.

Hi Mark,

Thank you for your question.

This is still present in our plans to work on, and I will let you know when we will solve this issue.

Right now, I'm afraid I cannot tell you when exactly this will be done, however, I will inform you for sure.

Regards,

Kate

Hi,

I am evaluating the suite and have just realized this problem.  This is a major functionality flaw.  It basically makes working with process builder useless within the IDE - I can only work with old versions of a PB? 

Is this going to be fixed really soon?

Please let me know.

Thanks,

Avi

Hi Avi,

Thank you for your post and for your question.

This is present in our development backlog and I hope we will have an ability to work on this during the nearest months.

I will let you know when this functionality will be available for you in the IDE.

If you have any other questions or suggestion, please let us know - we'll be happy to hear them and assist.

Have a nice day!

Regards,

Kate

I also need to see this resolved to make this product an implemented solution.

Thanks,

ZW

Hi ZW,

Thank you for your post.

This is still present in our plans to implement, and our developers are looking for a proper solution to solve this issue.

I hope we will do this in one of the nearest versions of the IDE.

I will keep you updated on our progress on this.

If you have any other questions or suggestions, please let us know - we'll be happy to answer them.

Regards,

Kate

Hi Kate,

Is there any update on this ? I believe Salesforce fixed the underlying issue with the winter 19 release - https://releasenotes.docs.salesforce.com/en-us/winter19/release-notes/rn_forcecom_flow_fullname.htm

Hi Joe,

Thank you for your post!

We are analyzing the released changes from Salesforce and our developers will work on this issue soon.

I will let you know on our progress on this or when the issue is solved in the IDE.

Have a nice day!

Regards,

Kate

Hi guys,

I hope you are doing well, and I'm happy to let you know that recently we have released the updated version of The Welkin Suite for Windows - Bloom R25.

This version contains a fix for the current issue, so now you can download or pull your active flows to your TWS project.

If you have any questions on this or any other topic, please let us know.

I'll close the current topic as Solved.

Have a nice week!

Regards,

Kate