Customizing SailPoint TaskDefinitions - OOTB method

Subject: Batch processing in SailPoint

Regarding: Using a rule to execute batch processing, customization of the inputs



Creating a TaskDefinition for running a rule is normally performed by the following:

Setup -> Tasks
New Task -> Run Rule

Enter the details such as what you want the rule to be named, description, then the rule to be executed.  Save and Run



The normal method for making changes to the behavior of the rule is through the Rule Config line.  In this, the input data, separated by commas, is entered as:

key,value,key,value,key,value,key,value

Which translates into an input variable called config, which is passed into the rule as a Map.  You can verify the value exists by using this:

if(config==void || config==null || config.isEmpty()) {
    log message
}
else {
  extract the key value pairs out of the map
}

The problem with this method is that it is hard to train people how to use it.  See further posts for how to get around this.

Getting SailPoint version information

To get the current version of your environment, load and run this rule:

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE Rule PUBLIC "sailpoint.dtd" "sailpoint.dtd">
<Rule language="beanshell" name="TestRule-GetVersion">
  <Description>Get Sailpoint Version</Description>
  <Source>//
  import sailpoint.object.*;
  import sailpoint.api.*;
  import sailpoint.Version;
  String version=sailpoint.Version.getVersion();
  String patchLevel=sailpoint.Version.getPatchLevel();
  String rval="Version="+version+" Patch Level="+patchLevel;
  return rval;
  </Source>
</Rule>