Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHi All,
It would be a given wherein IT would have invested effort and time building workflows and other components using some of the tools which became deprecated with the latest versions.
It is good to have the deprecated versions still available to make the code backward compatible, but at the same time there should be some option where in a deprecated tool can be promoted to the new tool available without impacting the code.
Following are the benefits of this approach -
1) IT team can leverage the benefits of the new tool over existing and deprecated tools. For e.g. in my case I am using Salesforce connectors extensibly, I believe in contrast to the existing ones the new ones are using Bulk API and hence are relatively much faster.
2) It will save IT from reconfiguring/recoding the existing code and would save them considerable time.
3) As the tool keeps forward moving in its journey, it might help and make more sense to actually remove some of the deprecated tool versions (i.e. I believe it would not be the plan to have say 5 working set of Salesforce Input connectors - including deprecated ones). With this approach in place I think IT would be comfortable with removal of deprecated connectors, as they would have the promote option without impacting exsiting code - so it would ideally take minimal change time.
In addition, if it is felt that with new tools some configurations has changed (should ideally be minor), those can be published and as part of
promotions IT can be given the option to configure it.
Thanks,
Rohit Bajaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.