Hi Chris,

From what I can see the Run Script Rule has replaced the Script/SDK Script function. This means that the script would need to be set up in advance and then called by Workflow.

Here is a quick example of the steps I'd take:

1. Go to Integrations and set up the Remote Agent - it should have a Queue with the Remote Script Source Plugin and a Worker installed on the server that will be running the script.
2. Go to Rules and create a Script called GenerateCSV - it should be assigned to the Remote Agent you just set up. Your script itself can be written in C#, Python or NodeJS (in the below example I use C#).
3. Open Visual Studio and create a Class Library (.NET Framework) project.
4. Use the following code:

   public class MyClass
       {
           public static Task<IDictionary<string, object>> MyScript(IDictionary<string, object> inputsFromRule)
           {
               //Initialize a Dictionary to store your outputs
               var output = new Dictionary<string, object>();
   
               // Build an SQL query based on the Input parameters - this is just a quick example
               string SQLquery = "SELECT * FROM "+ inputsFromRule["tableName"]+" WHERE "+ inputsFromRule["firstParameter"]+" = "+ inputsFromRule["secondParameter"];
              
               // TODO: Run SQL query, build and save your CSV file
   
               // Determines what output to send back - change this bool based on if the file was saved or not
               bool successfullyCreatedFile = true;
   
               // Change the output status
               if (successfullyCreatedFile)
               {
                   output.Add("status", "Successful");
               }
               else
               {
                   output.Add("status", "Failed");
               }
   
               // Return this status
               return Task.FromResult<IDictionary<string, object>>(output);
   
           }
       }

    

5. Build a Release version of the project and save the DLL file to the following location on the machine where the Worker is installed (you may need to change the LFPALocalAgent folder to LFPALocalAgent2 or LFPALocalAgent3 based on what Worker is being used): C:\Program Files\Laserfiche\ProcessAutomationWorkerAgent\LFPALocalAgent\GenerateCSV\bin
6. Return to the Script you made in Laserfiche Cloud and use the following settings:
7. When you test it, it should return "Successful" as I did not change the bool value.
8. Now in Workflow you can configure the following:

This example is a quick overview and should hopefully be a good starting point for what you want to accomplish.