How to Convert custom Action button in the Sales order screen classic to Modern UI

​@Sid if that’s a button that shows up among the other actions on top of the screen you don’t need to do anything actually. 

Having the button definition in the graph extension is enough to show the button both n old UI and new UI.

​@Dmitrii Naumov 

I have had issues with that previously, 24R2, unless I declared the action as so: 

export class GCQCRecord extends PXView {

	ViewBatch: PXActionState;
	ViewOrder: PXActionState;
	ReleaseFromHold: PXActionState;
	PutOnHold: PXActionState;
	Release: PXActionState;
}

Was this changed in 25R1, or should this have been standard functionality also in 24R2?

​@aiwan you are only supposed to declare them like that if you want to put them in some non standard place (e.g. link it to a field or put the button in the middle of a form).

Otherwise the declaration in the graph is enough to show it on top of the screen in both old and new UI (and should be the case in 24r2 as well).

​@aiwan it could be but dont quote me on that. ​@Dmitrii Naumov  is correct. See the documentation below:

The actions that are defined in the graph or in the workflow have corresponding commands displayed on the More menu of the form toolbar by default. You do not need to define them in the TypeScript code of the Acumatica ERP form.

However, if you need to place a button for an action on an area of the form other than the toolbar or the More menu, you need to do the following:

• To place a button on a table toolbar, you specify the property with the name of the corresponding action in the view class of the table, as shown below.
• To place a button in a dialog box or somewhere on the form (outside of the form toolbar or table toolbar), you specify the property with the name of the corresponding action in the screen class, as the following code shows. You then add the qp-button tag for the action in HTML.
• To execute an action when a user clicks the link on the field, you specify the property with the name of the corresponding action in the screen class and use the linkCommand decorator for the field that displays the link. An example of such action is shown in the following code.

ref: Button: Configuration