Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Workflow Archiving

Avatar

Level 2

Hi Fellow Forum members,

 

My customer wants to make sure that they are able to access all the completed/Aborted/Terminated workflows for past 1 month. Now Workflow console only shows first 40 items of workflows which are either completed/Aborted/Terminated. 

            What can i do so that it will show all the instances in Archive?

Note: Workflow Purge Scheduler is already configured to purge items older than 30 days.

Any help on this item will be appreciated.

 

Thanks and Regards,

Nitin

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

I think there seems to be some bug in pagination of work flow console in CQ 5.6 and above. Check with Adobe. One of the other place where we are discussing regarding this issue http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

View solution in original post

3 Replies

Avatar

Level 1

I know for me, it only shows 40 items per page. So, they should be able to just go to the next page to see the other items. The buttons are at the bottom:

Avatar

Level 2

Hi,

Thank you for reply.

I see that my repository has 1000's of records but the workflow console only shows 40 items and it doesnt have any more pages beyond that.

Thanks and Regards,

Nitin

Avatar

Correct answer by
Former Community Member

I think there seems to be some bug in pagination of work flow console in CQ 5.6 and above. Check with Adobe. One of the other place where we are discussing regarding this issue http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot 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 answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----