The Scenario: I am building a Subcontractor Obligations Tracker on a Core Plan. I have three main tables:
-
SC_Agreements: The “Parent” table containing Agreement IDs, Project IDs, and Contract Types (e.g., T1).
-
Obligations: A master list of compliance tasks (e.g., “Submit Insurance”). Each task is tagged with a
ContractType. -
SC_ObligationLog: The “Child” table where the bot should create new rows every month.
The Goal: I want a Scheduled Bot to run monthly. For every agreement in SC_Agreements, the bot needs to:
-
Identify the Agreement’s
ContractType. -
Find all matching tasks in the
Obligationstable. -
Create a new row in
SC_ObligationLogfor each matching task, carrying over the SubContract Ref No. and the Project ID from the specific agreement it is currently processing.
The Issue: Since I am on a Core plan, I don’t have access to Enterprise Action Inputs. When the bot triggers an action in the Obligations table to add a row to the Log, it “loses” the context of the specific Agreement it started with.