Can I cancel one process model in another process model

In my designs, I try to not use "Cancel Process", as it creates process alert messages which I have to tell people to ignore.

I use process messaging to just tell the other process to complete whatever it needs to do.

Thanks for your suggestion. If it is convenient, can you give me an example for reference or some more detail on process message

https://docs.appian.com/suite/help/22.4/Messaging_Best_Practices.html

https://docs.appian.com/suite/help/22.4/Receive_Message_Event.html#

docs.appian.com/.../Send_Message_Event.html

Using Cancel Process Smart Service in Process, Unable to cancel process with Basic User, but able to cancel process with Administrator Access.

That's how it works.

But in production /UAT -  testing team users is not System Administrator..., Even production users are not System Administrators, So is there any alternate way to cancel the process even with Basic user type of users..?

In my scenario I am I making a case Id delete(In record action) like soft delete(making isActive =0 in table) having defauld filters as where isActive =true , so that deleted row is getting removed from the recordList,

But here I am using Cancel Process Smart service to remove task related to deleted row from the list in MY TASKS PAGE on Site

But in production /UAT -  testing team users is not System Administrator..., Even production users are not System Administrators, So is there any alternate way to cancel the process even with Basic user type of users..?

In my scenario I am I making a case Id delete(In record action) like soft delete(making isActive =0 in table) having defauld filters as where isActive =true , so that deleted row is getting removed from the recordList,

But here I am using Cancel Process Smart service to remove task related to deleted row from the list in MY TASKS PAGE on Site

https://docs.appian.com/suite/help/23.4/Process_Node_and_Smart_Service_Properties.html#unattended-activities

Your users do not need to be admins nor should they. But the account that deployed the model should be a admin type user. Then assign nodes that need admin permissions like below: