Total RP 3: Extended

Total RP 3: Extended

903k Downloads

Workflow context changes after calling a campaign workflow

Ricorei opened this issue ยท 0 comments

commented

When doing:

effect("run_workflow", args, "o", "_documentRefresh") -- 1 
effect("run_workflow", args, "c", "_itemLock")  -- 2
effect("run_workflow", args, "o", "_documentRefresh")  -- 3

-- 1) Works nicely.
-- 2) Works nicely.
-- 3) Suddenly doesn't work as nicely.
  1. Call workflow -> ActiveCampaign
  2. Call workflow -> Object

The 2nd workflow will look into the Active Campaign and not in the Object resulting as:

  1. Call workflow -> ActiveCampaign
  2. Call workflow -> [Object] ActiveCampaign instead of [Object] Current Item.

https://imgur.com/a/3zsJavT

On this screenshot and as a proof/example, _documentRefresh isn't found unless it's created in Active Campaign. Though every Object variable "o" created in the campaign workflow will be correctly assigned to the current running item.

Perhaps the behavior is on purpose but it seems counter intuitive.