Executable objects

Executable objects support repeatable operational workflows (ingestion, transformation, validation, and review). They look similar to Standard objects (a record list) but include process-specific actions.

Pipeline objects (like Standard objects) are driven by object metadata and configuration.

What is an Executable object?

An Executable object record represents the run context for a process (for example: a time period, business unit, or batch). Users select a record, then execute an approved pipeline against that record.

Executable objects are available from the Pipeline Standard menu group.

Executable objects page layout

The pipeline object page contains:

• Record list (table): existing run-context records

• Row actions:

  • Execute

  • View Status

  • View Past Runs

Execute: start a guided processing run

Execute starts a guided run for the selected record. The UI is designed to keep execution predictable and auditable.

Typical execution flow:

1. Select pipeline

2. Upload input files

3. Start ingestion/processing

4. Monitor progress and review logs

5. Review outputs and resolve issues

1) Select pipeline

Biz-App opens a Select pipeline panel and presents only the pipelines configured for the object.

This ensures:

• Users can only run approved pipelines

• Each run is tied to a clear record context (the selected pipeline object record)

2) Upload input files

Biz-App opens a guided wizard with one or more upload prompts (cards). Upload prompts are configured in business language, so users know exactly what to provide.

Each upload card includes:

• Title: what to upload

• Description: what the file represents and the expected format

Common formats are CSV and Excel, depending on the client setup.

Multiple uploads

Some pipelines require multiple inputs (for example: activity data plus mapping tables). Multiple upload cards remove guesswork and reduce failed runs due to missing inputs.

3) Start ingestion/processing

After uploads complete successfully, the user starts ingestion.

Biz-App confirms that the job has started and continues processing in the background, so users are not blocked by long-running operations.

View Status: monitor a run

View Status provides the current state of execution for the selected record, including:

• What is running

• What has finished

• What steps are expected next

• Access to logs (for troubleshooting and support)

Status is designed to answer three operational questions:

• Is the run still in progress?

• Which step is it currently on?

• Where are the logs for investigation/support?

Review outputs

When processing completes, outputs are available for review (typically by an operator or data steward). This review step is where uploaded data is validated and promoted into trusted records.

View Past Runs: execution history

View Past Runs provides an auditable history of prior executions for the selected record/pipeline context.

Execution history supports operational reporting and comparisons, such as:

• When did we run this?

• How long did it take last month vs. this month?

• Did the run succeed or fail?