Setting Up Programs

1. Open the Interactive Code page in ToolBox (Administrators can navigate to the ToolBox -> Interactive Code page).
2. Write your AL code in the provided editor. For example:
   
   var
    Customer: Record Customer;
begin
    if Customer.FindSet() then
        repeat
            Message(Customer.Name);
        until Customer.Next() = 0;
end;

3. Run the program. ToolBox compiles and executes it instantly, displaying any Message() outputs or errors.
4. Save the program with a meaningful name:
   
   • Provide a title (e.g., Customer List)
   • Optionally include version notes or descriptions.

Why Use Programs?

• Rapid prototyping or testing of AL logic.
• Quick custom reports or data processing tasks without needing a full extension lifecycle.
• Handy automation scripts you can share with colleagues.

Making Programs Publicly Available

By default, only super users can see and run programs in ToolBox. If you want other (regular) users to run a particular program:

1. Go to ToolBox -> Interactive Code
2. Select the program you want to share (from the Load list).
3. Enable “Available for Public Usage”.
4. (Optional) Assign a permission set if only users with a particular permission set should run this program.
   
   • For example, you might require the “Sales Clerk” permission set to run a particular invoicing script.

Once marked “Available for Public Usage,” the program will appear in the Run Programs list for qualifying users.

Allowing Regular Users to Run Programs

When a regular user (non-super) opens ToolBox:

1. They will see a simplified menu, with only Run Programs available (or other limited options, depending on their permissions).
2. Under Run Programs, they can see any programs marked “Available for Public Usage.”
3. By selecting a program and clicking Run, the program executes. Any Message() outputs or results will display to them in the ToolBox interface.

Tip: As the administrator, you can configure each user’s privileges within ToolBox under ToolBox -> Setup -> Users. For instance:

• God Mode: Full access to create, edit, delete, and run programs.
• Normal: Run programs and optionally edit data in permitted tables.
• Read-Only: Only read data; cannot modify records.

Integrating with the Job Queue

You can schedule programs to run automatically and repeatedly, just like any typical AL codeunit:

1. Open ToolBox -> Run Programs.
2. Select the program you want to schedule, then choose Add to Job Queue.
3. In the Job Queue setup window, configure:
   
   • Recurrence (e.g., daily, weekly).
   • Start time and Days of the week.
4. When the job queue entry runs, any output that would normally appear in the ToolBox output window will be logged in the Job Queue Log, including Message() outputs.

This allows for hands-off automation of tasks such as data cleanup, report generation, or other repetitive work.

Using Excel Integration as a Simple UI

ToolBox provides an embedded Excel workbook that you can manipulate from AL code to simulate a simple request page or user input form:

Writing Data to Excel

Use exset(Row, Column, Text) to place text or data in a specific cell:

Reading Data from Excel

Use exget(Row, Column) to read text or data from a cell:

Opening the Excel Sheet for User Input

You can create a script that prompts the user to fill in certain cells and then proceeds:

When the user runs the program:

1. ToolBox opens an Excel sheet with relevant cells pre-labeled.
2. The user enters data (e.g., start date, end date) in the specified cells.
3. On closing Excel, the script reads those values and proceeds accordingly.

Saving the Excel Configuration

When you save your program, you can also save the current Excel sheet layout. This means when the program is loaded again, it restores your custom cells, labels, and any default values.

Best Practices

• Restrict sensitive scripts to administrators or super users; mark only safe, tested scripts as publicly available.
• Use permission sets to fine-tune who can run which scripts.
• Document your scripts within ToolBox so other team members understand their purpose.
• Limit direct table writes when assigning programs to regular users; consider read-only or limited table access to protect data integrity.
• Regularly review publicly available scripts to ensure they remain relevant, secure, and correctly permissioned.