Page Activation Workflow | Adobe Higher Education
Skip to main content
mikezooz
Level 4
October 16, 2015
Risolto

Page Activation Workflow

  • October 16, 2015
  • 9 risposte
  • 3423 visualizzazioni

Hi

I am trying to create a page activation workflow.

Currently i am facing the issue with the assets belongs to the current page is not get activated.(ie) Only the page got activated.

My Idea is get all the reference which belongs to current page and activate them.

is it a correct way to do?

if so how to get the reference?

else kindly route me in correct direction.

Bunch of thanks in advance,

Michael Vino

Questo argomento è stato chiuso alle risposte.
Migliore risposta di joerghoh

Michael,

see this example [1]. Basically you should use the AssetReferenceSearch service, which does the work for you.

Jörg

 

[1] http://wemcode.wemblog.com/get_asset_reference_in_page

9 risposte

Love_Sharma
Level 4
October 16, 2015

Hi,

In CQ, you can't publish both page and related DAM asset together. Only way to publish page and asset in DAM is doing that separately. DAM and Page are decoupled in CQ. So whenever you will publish the page, only your page will get published not DAM assets.

Regards

Scott_Brodersen
Level 8
October 16, 2015

There is an example installed called Scheduled Page/Asset Activation:

http://localhost:4502/cf#/etc/workflow/models/scheduled_activation.html

The "activate" step uses an existing OSGi service called Activate Page, which is installed with CQ. Are you using this service?

scott

joerghoh
Adobe Employee
joerghohAdobe EmployeeRisposta
Adobe Employee
October 16, 2015

Michael,

see this example [1]. Basically you should use the AssetReferenceSearch service, which does the work for you.

Jörg

 

[1] http://wemcode.wemblog.com/get_asset_reference_in_page

Level 2
October 16, 2015

I also have the same use case. I am also using the Page Activate service but it only activates the page, it doesn't activate the DAM assets associated with the page. 

I have checked Scheduled Page/Asset Activation workflow, it also uses the same service and doesn't activate the page assets, only activates the page

Michael, did you get any solution for this ??

mikezooz
mikezoozAutore
Level 4
October 16, 2015

HI Jorg,

Thanks a lot. its working fine.

Regards,

MIke

mikezooz
mikezoozAutore
Level 4
October 16, 2015

Hi KapilDev.

We have a JSON service which provides the list of asset available on the page as JSON data.

Then you have to create workflow  in that u have to make a HTTP Client call to the below service and read the path in JSON result  and activate both the assets and page using replication  API.

http://localhost:4502/libs/wcm/core/content/reference.json?path=pagepath

Regards,

Mike

Level 2
October 16, 2015

I am using CQ5.5.2

Scott_Brodersen
Level 8
October 16, 2015

michaelvino86 wrote...

Hi KapilDev.

We have a JSON service which provides the list of asset available on the page as JSON data.

Then you have to create workflow  in that u have to make a HTTP Client call to the below service and read the path in JSON result  and activate both the assets and page using replication  API.

http://localhost:4502/libs/wcm/core/content/reference.json?path=pagepath

Regards,

Mike

 

 

Similarly, page information providers might be interesting to you: https://dev.day.com/docs/en/cq/current/developing/pageinfo.html 

scott

mikezooz
mikezoozAutore
Level 4
October 16, 2015

Scott Brodersen wrote...

michaelvino86 wrote...

Hi KapilDev.

We have a JSON service which provides the list of asset available on the page as JSON data.

Then you have to create workflow  in that u have to make a HTTP Client call to the below service and read the path in JSON result  and activate both the assets and page using replication  API.

http://localhost:4502/libs/wcm/core/content/reference.json?path=pagepath

Regards,

Mike

 

 

Similarly, page information providers might be interesting to you: https://dev.day.com/docs/en/cq/current/developing/pageinfo.html 

scott

 

Wav... Its provide all the information about the page.

Bunch of thanks.

Mike