When creating a UI Action in SN, it will involve filling in the Action Name. This Action Name is not a display name, but a name used for other calls. This name will not be automatically verified. Usually no error will be prompted. But it will be very distressing to check when encountering problems. So its name should be as readable and unique as possible, of course the focus is on the latter.
Case:
Click a custom cancel button of a record. After clicking, the following error will be reported:
Access to api 'setAbortAction' from scope 'x_xxxx' has been refused due to the api's cross-scope access policy. (x_xxxx is just a newly created APP and does not have any other redundant actions, so we do not think it is a problem of cross-scope access).
So go check setAbortAction, this method is generally used for Business Rule.
We went through the records to find a specific Business Rule, and we found a "problematic" BR" through investigation, we set it to inactive, the problem was solved on the surface, and no more errors were reported, but in fact the data was not really processed. , because the data was working fine before, just because we created a new app?
Finally, after a more tedious investigation, we found that a student set the action to a simple cancel when setting the UI Action. So the system will search in alphabetical order, and will trigger when the first cancel is found. The newly created App will automatically generate some specific fields, so its cancel will be in the first place by default. This is the real reason for the error.
Therefore, when defining the Action Name, it should be as readable and unique as possible.