How do I validate EIN formatting upon lifecycle transitions on Public Cloud?

A client has a specific format for their EIN. We would like to ensure that any item that has an EIN has a well-formatted EIN before promoting the item to Frozen or Released. 

This client is currently using Public Cloud. The ER Generic Server Openings page linked below implies that the "Promote" business rule opening is not available on Public Cloud because it is a precommit opening. 

I'm stumped--the documentation seems a little inconsistent as well: lower down the page, it implies that precommit and compute openings should be used responsibly, so it lists various scenarios for the usage of functions to ensure that their operation does not disrupt other users of the same server resources. 

 

What is/are recommended best practices for evaluating EIN upon lifecycle transition, given that Generic Server openings, like Promote, are not available on Public Cloud?

Is migrating to private cloud really necessary for something like this? Or am I missing something rather obvious.

Please let me know: 

 

 

EKL Links:

ER Generic Server Openings: https://help.3ds.com/2024x/English/DSDoc/PjrUserMap/pjr-c-ERGenServer-computePrecommitOpenings.htm?contextscope=cloud

Promote specifically: https://help.3ds.com/2024x/english/dsdoc/PjrUserMap/pjr-r-Precommit-promote.htm?contextscope=cloud

 

CC: @RB , @RB