RumataActivity creation and deployment controls
Find reusable actions, create a Python activity, configure its inputs, and inspect builds and deployments.
Step-by-step guidance.
Before you start
- Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.
Activity list
Open System Explorer → Activities. An activity is a reusable action that a workflow can call. Create an activity by editing its code in the wizard, or ask the Rumata agent to create it for you.
| Control | What it does |
|---|---|
| Search activities | Filter the loaded activities by name or description. |
| All sources / Built-in by Rumata / Created by you / Third-party | Filter by origin. Source badges identify where an activity comes from; they do not establish its deployment or runtime health. |
| Runtime status filter | Filter by Active, Inactive, Deploying, Sleeping, Waking, Stopping, Unhealthy, Unknown or Checking status. Published/deployed state and current runtime health are different. |
| Activity row / Activity details | Open the activity’s Overview tab. |
| View source / View Code | Open the Source tab for the activity’s recorded builds. |
| Manage access | Control which groups can use, build, deploy, or manage the activity. |
| New Activity | Open a local creation draft. This does not create the resource until you submit Create Activity. |
Creation wizard and basic information
The four tabs are Basic Info, Activity Code, Configuration, and Machine Spec. Review all four before creating the activity.
| Control | What it does |
|---|---|
| Back | Leave the wizard and return to the activity list. This exits the wizard instead of moving back one step. An unsubmitted draft is not a saved activity. |
| Next Step / numbered step tabs | Move through the form or return to a specific section. |
| Activity Name | Enter a unique activity name using lowercase letters, numbers, dots, slashes, underscores, or hyphens, up to 30 characters. |
| Description | Explain the action in up to 120 characters. Both name and description are required. |
| Data Provider | Mark the activity as providing data to other activities. |
| Programming Language | Show Python, the language supported by this wizard. The field is disabled. |
| Create Activity | Validate the form, create the activity, and queue its build. It appears on Machine Spec and becomes Creating… while submitting. |
Activity Code: files and editing
The wizard starts with main.py. File operations here edit the creation draft; they do not publish a running activity.
| Control | What it does |
|---|---|
| Explorer toggle / divider | Show or hide the file browser and resize it beside the editor. |
| Files / Content search | Search by filename or search text within the available files. Select a result to open the file. |
| File / folder row | Open a file or expand/collapse a directory. |
| File tab / tab close icon | Switch between open files or close a tab. Closing a tab does not delete its file. |
| Code text editor | Edit the selected file in the draft. A modified indicator marks changed contents. |
| Plus / New File / New File Here | Open file creation. Choose Directory, Name, and Type, then Create. A missing extension is added from Type, and duplicate paths are rejected. |
| Folder-plus / New Directory / New Directory Here | Open directory creation. Choose its parent and name, then Create. Cancel or Close leaves the draft unchanged. |
| Rename in the file context menu | Open the filename field. In this activity-file browser, Enter or leaving the field closes it without applying the rename; Escape cancels. Use the full Code editor to rename an existing workspace file. |
| Delete file / Delete directory in the context menu | Remove that item from the creation draft. Check its contents before using this action. |
Entry point and arguments
The entry point tells Rumata which function to call. Arguments are named settings supplied to that function.
| Control | What it does |
|---|---|
| Entry File | Choose the file containing the function to run. |
| Entry Function | Enter the function’s name, initially main. |
| Package Manager | Select pip, the supported dependency manager in this wizard. |
| Edit entry function arguments | Open the detected function signature and its configurable parameters. |
| Highlighted argument / argument button | Open the settings for that parameter. |
| Type: String / Number / Boolean / Object / Array | Describe whether the setting is text, a number, yes/no, a structured record, or a list. |
| Argument Description | Explain what a workflow author should provide. |
| Default Value | Set the value to use when a value is not explicitly supplied. |
| Optional | Mark whether the caller may omit this setting. |
| Options (comma separated) | For a string setting, list the choices presented to the caller. |
| Done / Close in argument settings | Return from the argument editor. Changes already update the local creation draft; Done is not deployment. |
Machine Spec
This specification controls resources requested by the activity when it runs. It is separate from your factory development machine’s size.
| Control | What it does |
|---|---|
| Memory slider | Choose 128–1,024 MB in the current form. The displayed initial value is 512 MB. |
| CPU slider | Choose 0.1–1 CPU core in increments of 0.1. The initial value is 0.4 cores. |
| Activity Summary | Review the name, description, entry point, package manager, and configuration fields before Create Activity. |
Activity details: builds and source
Open an existing activity to inspect the versions Rumata built and the source used by those builds.
| Control | What it does |
|---|---|
| Overview / Builds / Deployments / Source | Switch between metadata, build records, running versions, and source files. |
| Source on a build | Open files for that specific build. Disabled when its repository, activity path, or commit/ref information is missing. |
| Choose a build in Source | Select the recorded revision to inspect. |
| Repository link | Open the source repository in a new tab. |
| Source file explorer / search / tabs | Browse files for the chosen build. This view is read-only; editing and file-creation controls are hidden. |
| Close activity details | Return to the activity list. |
Deploy and stop an activity
A build packages code. A deployment makes that build available for workflow calls. The deployment state is shown separately from build success.
| Control | What it does |
|---|---|
| Deploy on a build | Open deployment settings. Unavailable while the build is in progress or failed, while another request is submitting, or until an active deployment has stopped. |
| Disabled Deploy explanation | Hover over or focus the area around the disabled action to learn why the build cannot be deployed. |
| Idle before sleeping | Choose an allowed auto-sleep duration. The default and plan maximum are marked. The first request after sleep waits for the activity to wake. |
| Deploy activity | Start an on-demand deployment with that idle duration. Cancel closes the form without deploying. |
| Stop on a deployment | Open a confirmation in the Deployments tab. |
| Stop deployment in confirmation | Stop accepting new workflow requests. You can deploy a successful build again after it stops. |
| Cancel stop | Keep the current deployment. |