Has anyone seen or used this? Sounds too good to be true, we can now upload Cloud rules without expert service charge.
Hi @ugochuik - Yes and it works very well! We have seen an average of about 15 minutes in most cases. Now no more waiting a day to retest rule changes 
Hello @ugochuik,
I believe the “Upload Cloud Rules without Expert Services charges” feature was introduced approximately a month ago. We have successfully used this automated deployment capability to deploy rules to our tenants. The process is very straightforward. After submitting the rule, the platform performs validation and immediately displays the results. If the validation fails, the corresponding errors are shown, making it easy to identify and resolve issues before deployment. Once the rule passes validation and is submitted, deployment is typically completed within a short time. In our experience, it has taken around 15 minutes.
One thing to note is that there is currently no automated option to delete a deployed rule. However, if you need to make changes, you can deploy an updated version using the same rule name, which will overwrite the existing deployed rule. We have used this approach successfully for updating deployed rules(Rules deployed with the automated featue) using this automated feature.
Yes, it has worked well for us too. Most of our deployments landed in about 15 minutes, in line with what @ryan_toornburg and @Jerinhrb04 saw. A couple of them took closer to 55 minutes, though, so if a rule does not show up after 15 minutes, give it up to an hour before assuming something went wrong or resubmitting.
+1 to @Jerinhrb04’s point on updates: submitting a new version under the same rule name overwrites the deployed one, which is what makes the quick retest loop practical. I wonder how this works with 
's previous rejections of versioned rules
I used it succesfully for a before provisioning rule. However when i added a hard-coded source ids in the rule using a map, it failed asking me to validate the rule with -a option using the rule validator. The -a option adds a signature with your email. The resultant rule failed to deploy.
I added the following lines
SOURCE_ID_BY_NAME.put(“source1”, “261561c0f27040ed9bad9cacb94df1f0”);
SOURCE_ID_BY_NAME.put(“source2”, “7c5878e99b974e30931fd7ca387fb7cd”);
SOURCE_ID_BY_NAME.put(“source3”, “a1f4b39fe4e946a5a7776b46eec893c8”);
SOURCE_ID_BY_NAME.put(“source4”, “32b6f99ddea74f18a904104f0ffadd00”);
SOURCE_ID_BY_NAME.put(“source5”, “e1cabb2f3488471e9210ac617e769f21”);
The validator succeeds, but the rule deployment fails
Line 34 - [bsh.LintValidatorSecretsForLiteral] Message: “PII/Secrets rule WEAK_PASSWORD:Possible Password, checked for at least one number, one letter , matched with text: ‘\“e1cabb2f3488471e9210ac617e769f21\”’”
______________________________________________________________________________
Warnings: (1)
Line 119 - [bsh.LintValidatorForStatement] Message: “For statement detected: for ( int i = 0 ; . . \“For Loops\” can cause issues when looping with incorrect exit conditions. Ensure Looping exit conditions are correct.”
10-07-2026 09:02:21 CDT - SystemAdditional comments
An unexpected error occurred during the automated deployment process of your files. Our technical team has been notified.
Yes, we get that too. It is a huge problem. I would love to know if there is a workaround for this
Hello @jrossicare , @nileshnikalje-cf ,
This is because Validator is treating the sourceID’s as PI or secret sensitive information.
The solution I have used:
Refer this page - IdentityNow Rule Validator | Knowledge Base | SailPoint Community
- Download SailPoint Rule Validator and extract the file.
- Make Sure you have java installed correctly (specific versions).
- Go to the folder which the validator resides and open cmd
- Then run the command sp-rv --file “Path which your rule is saved\RuleName.xml”
- Make sure your rule file saved in the format “Rule - Rule Type - Rule name in the code”. (This rule file must be used in the command while executing the previous step).
- If you are seeing the exact results in cmd which you saw in online Rule deployment validator, we are close.
- To inform validator to ignore the sourceID like data, Run the same command with an addition of --approve emailadress. Example : sp-rv --file “Path which your rule is saved\RuleName.xml” --approve emailadress.
- An approval signature will be appended to rule and you can use that rule file for automated rule deployment in support portal.
If you are observing the rule deployment failure with error “An unexpected error occurred during the automated deployment process of your files. Our technical team has been notified” after submitting the rule and a deployment case opened. For the past two days , we are also facing the same issue with one or two rules we have submitted to deploy. It should be taken care by the support team within one day or proper follow up through CSM will help.
Thank you for the reply @Jerinhrb04 , it has helped a lot
How to get this functionality enabled in our tenant. what is the process to upload the rule in ISC without SP support.
It available to everyone. Instructions are in the support article