Why does copying and rerunning deprecated Code Step, even despite changing the connection, still make it as deprecated?

[JeffreyYu]

please see: https://forum.pabbly.com/threads/why-doesnt-work-in-code.17121/

When I tried to just recopy the deprecated code step, and change the action step from Run Python (deprecated), to Run Python, and then execute it, it worked. BUT there was still a notification in the top left corner saying the step was deprecated.

Thus, I had to create an entirely new code step and copy paste it in. The problem was that, then, I had to trace through the rest of my entire workflow for every single new code step, and then reassign the output. Since I missed a few (there were other 21 affected steps), it actually caused some issues in our emailing line this morning.

To solve this, could Pabbly make it so when a deprecated step is copied, and the connection fixed, it removes the deprecated sign?

 

[ArshilAhmad]

Hi @JeffreyYu,

please see: https://forum.pabbly.com/threads/why-doesnt-work-in-code.17121/

When I tried to just recopy the deprecated code step, and change the action step from Run Python (deprecated), to Run Python, and then execute it, it worked. BUT there was still a notification in the top left corner saying the step was deprecated.

Thus, I had to create an entirely new code step and copy paste it in. The problem was that, then, I had to trace through the rest of my entire workflow for every single new code step, and then reassign the output. Since I missed a few (there were other 21 affected steps), it actually caused some issues in our emailing line this morning.

What seems to have happened here is that you copied a deprecated action step and ran the code using this step. Since the code executed as intended, you proceeded to map the response in the next steps. However, because you copied a deprecated step, the sign remained.

To solve this, could Pabbly make it so when a deprecated step is copied, and the connection fixed, it removes the deprecated sign?

Thank you for the suggestion. I will pass this on to our technical team, and they will look into it.

 

[JeffreyYu]

Great, thank you!

I should have clarified: when I copied the deprecated code step, I also changed the Action Event from the deprecated version to the non-deprecated one. But, the deprecated sign still remained

 

[ArshilAhmad]

That seems unusual. Could you kindly verify if the deprecated sign is still visible or is it fixed now?

 

[JeffreyYu]

I unfortunately already got rid of all the deprecated code steps by manually adding a new one. BUT next time, if this happens again, I will record it happening and put it in a post!

 

[JeffreyYu]

Hi Pabbly! I found a code step I had skipped over before, and was able to manually reproduce the issue!

Please see the Loom I recorded on it:

Loom | Free Screen & Video Recording Software

Use Loom to record quick videos of your screen and cam. Explain anything clearly and easily – and skip the meeting. An essential tool for hybrid workplaces.

www.loom.com

 

[JeffreyYu]

Update: when I reload the page though, the step appears to no longer be deprecated! But this behavior is deviant from other steps, which say that the step has been fixed as soon as we run and save a successful test

 

[ArshilAhmad]

When making changes to a deprecated application, ensure that you select the application from the 'Choose App' field. This will help resolve the issue.

 

[JeffreyYu]

Ohhh that’s different from other steps. I Will try that next time, thank you!

Doesn’t that mean though, if I change the step, all subsequent steps that are dependent on it will lose the connection? Aka will show up as “No Data”?

 

[ArshilAhmad]

Mapping depends on the Key received from a particular step response. As long as the Key remains the same, your mapping should not be impacted. However, this is something you will have to try at your end

 

[JeffreyYu]

Ohhh got it!