Web page composer for creating static pages

[Former Member]

Hi there,

I have a scenario where I need to develop static pages in Web page composer. That is I dont want to build a complete site but only static pages. And then I want to enable the Approval workflow from KM for these static pages. Can someone throw some light on this how I can acheive?

Regards,

Ponraj M

[jonh_goldberg]

I don't think the KM Approval workflow is functional in the current (SPS13) release of WPC. As far as developing the pages, that should be no problem, you can create them in WPC, all within the same site, and create a PCD folder for each page that uses the WPC navigation connector. The pages are then added to your portal navigation using those proxy folders. Alternatively, you can create an IView that contains a WPC page, but the edit-in-place functionality does not work quite properly under this scenario.

[Former Member]

Ah! When you say that the edit-in-place functionality does not quite work, what do you mean? Do you mean that it replaces the entire portal space? And then it is a pain to get back to the portal?

If so, then does this not happen if you publish the site navigation, then add this link as an external connector for a folder underneath a role?

I have been pretty much just using the wpc iview to house my pages, and the editing in place is a pain.

[jonh_goldberg]

Yeah, using the WPC page embedded into an iview, WPC does not return to the page containing the iview after editing is complete. If the page is added using the external connector, then things work as expected.

[Former Member]

Hi Jon/Eric,

Can you please tell me on how I can make an iView out of content created by WPC. Since all the documents are in XML format I am not able to use KM document iView. Kindly help.

Regards,

Ponraj M

[Former Member]

Ponraj -

Procedure

...

1. In the Web Page Composer, navigate to the Web page that you want to integrate into the portal navigation.

2. To copy the path to the Web page to the clipboard, choose Copy Path from the context menu for the Web page.

3. Choose Content Administration → Portal Content.

4. Choose New → iView from the context menu of a folder.

5. Choose Portal Component as the source type.

6. Choose the com.sap.nw.wpc.runtime portal archive. On the next screen to appear, choose default.

7. Once you have created the iView, choose the Web Page Composer category in the property editor.

8. In the RID of Compound Document property, enter the path to the KM folder representing the Web page.

Example: /wpccontent/Sites/MyWebSite/Web Pages/MyWebPage

You can paste this path from the clipboard.

9. Open the workset or role that you created when you carried out the initial configuration.

10. To add the iView to the workset or role, choose Add iView to Workset/Role → Deltalink from the context menu of the iView.

[Former Member]

You could use Web Page Composer for this, but you don't have to.

You could just use normal KM.

From a KM folder, select in the menu, Folder --> New --> HTML File...

To activate approval workflow for a folder, go to the details of the folder.

Then choose Settings --> Approval.

Follow the steps/wizard after that.

[Former Member]

Eric,

Can you please tell me the reason why I should not use Web page composer for this. That will be a great help for me.

Regards,

Ponraj M

[Former Member]

Ponraj -

I am not saying to not use WPC. I am only saying you do not have to use it.

It depends on what your requirements are.

If you just want a plain html page, KM html pages are fine.

If you want pages like SDN, then use WPC.

We are using WPC with success.