Hello,
I am trying to debug a workflow by setting it up from a row action on the sales order detail extension. I have tried customizing the sales order apps (h/d) in the dev environment (RPDevPartner - coxauto) and testing environment (RPDevPartner - coxauto_test) and am not seeing the row action appear in either case. What is the expectation for setting up a row action on an extension within a lifecycle?
To clarify I only have one set of customizations, I deleted the ones in test when trying to do the customization in dev.
@ian.p do you know a good person to tag for this? Maybe someone from client?
It should show up without any extra effort required if it is configured correctly and the user has applicable security allowing them to execute the row action.
With all those customizations (are you sure you need them all?) is there a chance you’re in the predicament I’ve previously called out here?
What I have seen catch people out frequently is situation d. where intuition might suggest that the sequence is 4 then 2 then 3 then 1. However that is not the case. A customization in xxx_test base lifecycle trumps a customization in xxx nonbase lifecycle.
If it’s not that, book a slot on my calendar to help troubleshoot.
If I am understanding correctly, you need to delete customization in base in xxx_test before customizing in your lifecycle to see the action appear? @ian.p
That is one option, or if you don’t want to delete that customization, create an additional customization in branch lifecycle in xxx_test to get changes you’ve made in branch lifecycle in xxx to become available.