Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Optional attributes in ACS workflows

Kornel_Keseru
Level 3
Level 3

Hello!

I'm trying to build reusable workflow templates in Adobe Campaign Standard that can handle variable input structure (without having to reconfigure certain workflow steps every time the input changes).

For example, in the the Extract file step I want to be able to cope with optional attributes (that may or may not be present on the input transition), and default them to empty string for the output.

I thought that an expression like this - for the missing 'optionalAttribute' - could handle the attribute that is not always present, and write out an empty string:

Case(When(NULL != optionalAttribute, optionalAttribute),Else(""))

But the workflow fails with the following error:

- 'optionalAttribute' element unknown

I understand, that to ensure consistency, we should always configure a fixed structure for input files and transitions, but being able to handle the case like above would make our workflows easier to reuse.

Is it possible to write an expression for e.g. the Extract file step, that handles the case above?

Thanks!

1 Accepted Solution
florentlb
Correct answer by
Level 10
Level 10

Hi Kornel,

This seems unlikely to work from my understanding. Activities work with defined schemas, so I'm not sure how it can work with a structure that can change between 2 executions.

As of now, you cannot use such variables with ACS anyway.

I'd recommend creating a workflow template that you'd be able to adapt manually for each case (that would limit the manual actions to take).

Hope this helps,

Florent

View solution in original post

1 Reply
florentlb
Correct answer by
Level 10
Level 10

Hi Kornel,

This seems unlikely to work from my understanding. Activities work with defined schemas, so I'm not sure how it can work with a structure that can change between 2 executions.

As of now, you cannot use such variables with ACS anyway.

I'd recommend creating a workflow template that you'd be able to adapt manually for each case (that would limit the manual actions to take).

Hope this helps,

Florent

View solution in original post