Skip to main content

Step 6 - Build the Augment Events Supporting Pipeline

⏱ 6 min. Use AI Copilot to join user, workspace, model, action, and audit code context to raw Anaplan events.

🔍 What You're Doing

This is the core of the audit pipeline. Anaplan's raw audit events arrive as a stream of records carrying internal IDs and numeric event codes that are not analyst-ready. This Pipeline joins the events to your Anaplan Users, Workspaces, Models, and Action records (the combined output from Step 5), then layers on the human-readable event messages from your Activity Event Codes lookup. The result is a single enriched dataset where every audit record carries who did what, in which workspace and model, against which action, and what that action means in plain language.

You describe the join logic as a sequence of phases in plain English, and AI Copilot generates the deterministic transformation steps for you to review before they run on your data.


✅ Summary of Steps

  1. From the Workflow's Pipelines tab, click Add to create a new Supporting Pipeline.

  2. Enter Augment Events in the Name field and click AI Copilot.

  3. Add the following six datasets: Anaplan - Events, Anaplan - Users, Anaplan - Workspaces, Anaplan - Models, Activity Event Codes, and the Stack Actions output.

  4. Set Anaplan - Events to Primary and confirm all six datasets are listed.

  5. Click into the description text area and paste the prompt below. Drag the resize handle to expand the text area if needed.

  6. Click Generate Instructions, review the AI-generated plan, and click Approve & Build.

  7. Watch the Pipeline build out each transformation, then click the last transformation step to view the enriched output.


📋 Prompt to Copy

Paste this into the AI Copilot description field in step 5:

Augment the events dataset using the following operations. Order matters.

Complete every step within a phase before starting the next phase. Do not

batch renames at the end. Each rename must occur immediately after the join

that introduces the field.

Phase 1: Join Users

1. Left join the users dataset, joining events.userId to users.id

2. Rename userId to USER_ID

3. Rename userName to USER_NAME

4. In USER_NAME, replace blank values with INTERNAL_USER

Phase 2: Join Workspaces

5. Left join the workspaces dataset to the events dataset by joining additionalAttributes.workspaceId to id

6. Rename additionalAttributes.workspaceId to WORKSPACE_ID

7. Rename name to WORKSPACE_NAME

Phase 3: Join Models

8. Left join the models dataset to the events dataset by joining additionalAttributes.modelId to id

9. Rename additionalAttributes.modelId to MODEL_ID

10. Rename name to MODEL_NAME

Phase 4: Join Actions

11. Left join the output of the Stack Actions supporting pipeline by joining the additionalAttributes.actionId to id

12. Rename additionalAttributes.actionId to ACTION_ID

13. Rename name to ACTION_NAME

Phase 5: Audit

14. Left join the Activity Event Codes to the events dataset by joining eventTypeId to Event Code


Did this answer your question?