Adobe Campaign Classic – Accessing Campaign or Workflow Data in Control Typology JavaScript Rules | Community
Skip to main content
P
Pradyumn
Level 3
February 23, 2026
Solved

Adobe Campaign Classic – Accessing Campaign or Workflow Data in Control Typology JavaScript Rules

  • February 23, 2026
  • 2 replies
  • 53 views

Hello Everyone,

In Adobe Campaign Classic, I am writing a custom typology JavaScript rule that needs to evaluate recipients using campaign‑level or workflow‑level information.

While testing, I observed the following behavior in typology JavaScript execution:

  • vars is not defined
  • instance.vars is not defined
  • Workflow transition variables are not accessible
  • Campaign / operation attributes cannot be accessed via Control Typology JavaScript 

 

Is there any supported way in Adobe Campaign Classic to access campaign‑level or workflow‑level data directly inside a control typology JavaScript rule?

Or is Control typology JavaScript intentionally isolated from workflow and campaign context by design?

 

Thanks!!!

Pradyumn

 

 

​@ManviSharma ​@giuseppebaglio ​@AmitVishwakarma ​@arpan-garg ​@muskaanchandwani 

Best answer by Pradyumn

Hi @Nolan_Chabert , Yes, only nmsdelivery attribute is accessible into typo. i did not try because my requirement was along with above workflow attribute recipientId should also accessible into typology but due to limitation at typology end. I dropped this approach.

2 replies

Manoj_Kumar
Community Advisor
Manoj_KumarCommunity Advisor
Community Advisor
February 24, 2026

Hey ​@Pradyumn Typologies do not have access to vars or instance vars defined in workflow. You can only access delivery in a typology.

I have not tried it by try accessing it by using delivery.operation_id or delivery.workflow_id in the typology

Manoj  | https://themartech.pro
P
PradyumnAuthor
Level 3
February 24, 2026

Hi ​@Manoj_Kumar , thanks for response. i tried both options using log Info inside the control typology java script. only delivery related attribute available to use further.

logInfo("=== DELIVERY OBJECT DEBUG ===");
logInfo("operation_id = " + delivery.operation_id);--result -->0
logInfo("biCampaignID = " + delivery.biCampaignID); --result-->undefined
logInfo("id = " + delivery.id);--result-->11739292
logInfo("internalName = " + delivery.internalName);---result--internalName
logInfo("label = " + delivery.label); ---result--label

 

Thanks!!

Pradyumn

 

Nolan_Chabert
Adobe Employee
Nolan_ChabertAdobe Employee
Adobe Employee
March 5, 2026

Hi Pradyumn, 

have you try to inject your workflow data in your delivery variable from the delivery activity script? 

Regards,

Nolan 

P
PradyumnAuthor
Level 3
March 5, 2026

Hi ​@Nolan_Chabert , yes i tried to assign workflow variable via delivery script tab and used them to pass to control typology, it still throws an error variable is undefined.

Thanks!!!

Pradyumn

Nolan_Chabert
Adobe Employee
Nolan_ChabertAdobe Employee
Adobe Employee
March 5, 2026

Hi Pradyumn, 

as only delivery attribute can be use in the typo, Have you test to extend your delivery schema and populate this new field to access it from your typo? Thanks 

Terms & ConditionsAccessibility statement

Loading footer...