nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automated page generation algorithms

sabya

Automated page generation algorithms (livesite) - a sophisticated scanning algorithm automatically generates the presentation output, reducing the need for IT professionals to custom code each page every time an update is made. It would be highly appreciated if you can please provide us the alogorithm along with code.

Find more posts tagged with

Comments

Faizi

Automated page generation algorithms (livesite) - a sophisticated scanning algorithm automatically generates the presentation output, reducing the need for IT professionals to custom code each page every time an update is made. It would be highly appreciated if you can please provide us the alogorithm along with code.

As per as your requirement it will be a collection of lots process and require time devotion.
Before this, Do you have knowledge and implementation of following:

Livesite
Site Publisher
Workflow
Workflow Modeler

If no, then you should go for IW-Training.

sabya

As per as your requirement it will be a collection of lots process and require time devotion.
Before this, Do you have knowledge and implementation of following:
Livesite
Site Publisher
Workflow
Workflow Modeler
If no, then you should go for IW-Training.

HI Faizi,

I have some knowledge of teamsite and livesite.if you can just help me in letting me know about the approach atleast it would be of great help.

santosh013

HI Faizi,

I have some knowledge of teamsite and livesite.if you can just help me in letting me know about the approach atleast it would be of great help.

Hi Sabya,
What faizi is trying to say is that You should go through the LiveSite manual for the basics,it will help you a lot.
If then also You face any problem, then everyone out here will definitely try to help you out but for that you will have to go through the Pdf's provided.

Come with your specific requirement and We will try to solve accordingly.

Thanks,

sabya

Hi Sabya,
What faizi is trying to say is that You should go through the LiveSite manual for the basics,it will help you a lot.
If then also You face any problem, then everyone out here will definitely try to help you out but for that you will have to go through the Pdf's provided.

Come with your specific requirement and We will try to solve accordingly.

Thanks,

Hi, Santosh/Faizi

I am detailing you the complete scenario. We have various components added to a page( .page) file. When we update or modify any component and submit the component and later when we go and try to edit the .page file it throws a pop-up asking for update/overwrite for the mismatch in the components versions. I want that the pop-up should not populate and the .page file get updated with the latest version of the component automatically. i hope i have made it clear.

sabya.

santosh013

Hi, Santosh/Faizi

I am detailing you the complete scenario. We have various components added to a page( .page) file. When we update or modify any component and submit the component and later when we go and try to edit the .page file it throws a pop-up asking for update/overwrite for the mismatch in the components versions. I want that the pop-up should not populate and the .page file get updated with the latest version of the component automatically. i hope i have made it clear.

sabya.

Sabya,
There can be several solutions to this but The solution which I am getting right now is that You will have to make a work flow(WFM as I work on WFM) and in it You call your own java classes (through external task) where you will update the component.
Select your page and submit it through this workflow to get the updated components.

HTH.

Thanks,

santosh013

Sabya,
There can be several solutions to this but The solution which I am getting right now is that You will have to make a work flow(WFM as I work on WFM) and in it You call your own java classes (through external task) where you will update the component.
Select your page and submit it through this workflow to get the updated components.

HTH.

Thanks,

Sabya,
If you see the get latest component link under livesite menu in content center,there also a get latest component class file is being called.
If you want to know more about how the get latest component class works,then go to the \iw-home\httpd\webapps\content_center\WEB-INF\lib directory and explore the livesite.jar.

It depends upon your requirement what you want but if you want to do it without any event then I hope(worry), it is not feasible.

Thanks,

sabya

Sabya,
There can be several solutions to this but The solution which I am getting right now is that You will have to make a work flow(WFM as I work on WFM) and in it You call your own java classes (through external task) where you will update the component.
Select your page and submit it through this workflow to get the updated components.

HTH.

Thanks,

Hi HTH,

can you suggest something where we need not check which all pages have the components which are updated, rather when we submit the updated component a workflow should update the pages containing those components automatically.if possible can you provide me your contact number so that we can discuss this.

sabya..

Faizi

HI Faizi,

I have some knowledge of teamsite and livesite.if you can just help me in letting me know about the approach atleast it would be of great help.

Hi Sabya,
I always welcome for query and it will be my happiness if pointers given by me help to sort out the problem.

As your requirement has a degree of complexity and what i told earlier that nothing is impossible to do. Smiley Happy

Now come to your requirement. In Teamsite there is a menu action and "Get Latest" for updating the workarea with the STAGING or vice-versa the same thing would be achieve through CLT "iwupdate". In workflow using external task we can call CLT in Java class/ipl file for updating the workarea.

In your case you want to perform same kind of thing. But as per as my knowledge there is no any CLT for "Get Latest Components". But still there are various way to do. I am pointing some of them:

1. Simplest way (if you dont want to dig into coding)

When we update or modify any component and submit the component and later when we go and try to edit the .page file it throws a pop-up asking for update/overwrite for the mismatch in the components versions. I want that the pop-up should not populate and the .page file get updated with the latest version of the component automatically.

The person who is goining to edit the page or who had updated the component invoke the "Get Latest Component" from the Livesite menu from the site folder then while editing the .page the POP-UP will not come.

2. Develop a workflow which has a URL External Task, using this task you call your own custom Java class. Now you need to know how to write own custom java class and extend the existing fuctionality. You can find GetLatestComponentAction class in livesite.jar, this will help you in java coding.

3. Another way would be again using workflow, there is term calling "Custom_Url" in CGI Task. So, you have to use a CGI Task in which call the custom url "GetLatestComponentForm.jsp" (or related to) that you can get from \\iw-home\httpd\webapps\content_center\livesite\Component\GetLatest folder.
Basically it will invoke the same UI and process which we follow from the Livesite Menu "Get Latest Component" but from the workflow.

Now its upto you what you can follow. Hope you understand. Any query/doubt feel free to ask.

Hope this helps.

sabya

Hi Sabya,
I always welcome for query and it will be my happiness if pointers given by me help to sort out the problem.

As your requirement has a degree of complexity and what i told earlier that nothing is impossible to do.

Now come to your requirement. In Teamsite there is a menu action and "Get Latest" for updating the workarea with the STAGING or vice-versa the same thing would be achieve through CLT "iwupdate". In workflow using external task we can call CLT in Java class/ipl file for updating the workarea.

In your case you want to perform same kind of thing. But as per as my knowledge there is no any CLT for "Get Latest Components". But still there are various way to do. I am pointing some of them:

1. Simplest way (if you dont want to dig into coding)

The person who is goining to edit the page or who had updated the component invoke the "Get Latest Component" from the Livesite menu from the site folder then while editing the .page the POP-UP will not come.

2. Develop a workflow which has a URL External Task, using this task you call your own custom Java class. Now you need to know how to write own custom java class and extend the existing fuctionality. You can find GetLatestComponentAction class in livesite.jar, this will help you in java coding.

3. Another way would be again using workflow, there is term calling "Custom_Url" in CGI Task. So, you have to use a CGI Task in which call the custom url "GetLatestComponentForm.jsp" (or related to) that you can get from \\iw-home\httpd\webapps\content_center\livesite\Component\GetLatest folder.
Basically it will invoke the same UI and process which we follow from the Livesite Menu "Get Latest Component" but from the workflow.

Now its upto you what you can follow. Hope you understand. Any query/doubt feel free to ask.

Hope this helps.

Hi Faizi,

thanks a lot for your help.it solved our purpose.

thanks you.

Faizi

Hi Faizi,

thanks a lot for your help.it solved our purpose.

thanks you.

Welcome,
Finally, you solved it.:cool:
So what you have followed?

ssharma48

Hi Sabya,

We also have the same requirement where we need to take latest Component update on a page.
Can you please explain the step how you ahave relsove the issue.

Regards,
Shikha

Faizi

If you read properly my reply then you will find different solutions. It's up to on your use case / requirement what exactly fit there.

As you didn't mention your use case then it is difficult to assume the solution.