Expand my Community achievements bar.

SOLVED

DAM Update Asset Workflow

Avatar

Former Community Member
2/26/18 6:03:11 AM

Hi,

Our site currently runs on AEM 6.2. One of the issues we're facing in the site is that extra commas are added to the title of the asset. I've done some research and found out that when a title is set before "DAM Update Asset" workflow gets completed, the new title contains both titles separated by commas. Please let me know how this can be avoided as it is causing a bit of issues in the site.

Views

1.1K

Replies

1

Total Likes

Translate
Translate
1 Accepted Solution

Avatar

Correct answer by
Level 10
Level 10
2/26/18 7:25:57 AM

You can build a custom workflow step, get the payload data, including the title and make changes to it. We are doing an ATCE experts tomorrow on this very subject - i recommend signing up and asking these questions.

Scott's Digital Community: Ask the AEM Community Experts for Feb 2018

View solution in original post

Views

700

Replies

0
Sign in to like this content

Total Likes

Translate
Translate
Jump to reply
1 Reply

Avatar

Correct answer by
Level 10
Level 10
2/26/18 7:25:57 AM

You can build a custom workflow step, get the payload data, including the title and make changes to it. We are doing an ATCE experts tomorrow on this very subject - i recommend signing up and asking these questions.

Scott's Digital Community: Ask the AEM Community Experts for Feb 2018

Views

701

Replies

0
Sign in to like this content

Total Likes

Translate
Translate
Jump to reply
Related Conversations
Is there a way to sort the top-level folders in AEM Assets? Solved

Views

274

Likes

0

Replies

9
Retiring Tags on AEM DAM

Views

222

Likes

0

Replies

4
Tigger workflow on publish but not quick publish for all nodes using launcher

Views

183

Likes

0

Replies

8
Asset metadata property need to update

Views

165

Likes

0

Replies

5
Best practice for moving assets in AEM

Views

80

Likes

0

Replies

2
The following has evaluated to null or missing: ==> liql("SELECT id, subject, body, depth, post_time, author.login, author.id, author.rank, metrics.views FROM messages WHERE topic.id = '${topicId}' AND is_solution = true").data.items[0] [in template "analytics-container" at line 82, column 31] ---- Tip: It's the final [] step that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign acceptedAnswer = liql("SELECT... [in template "analytics-container" at line 82, column 5] ----