English
Deutsch
Español
Français
Hrvatski
Italiano
Polski
Türkçe
Русский
中文
日本語
한국어
Legal notice
powered by CADENAS

Manual

Top Links

Manual

Chapter 5.  PARTproject
5.15. Embed use cases in PARTdataManager / PARTcommunity
Prev   Next

5.15. Embed use cases in PARTdataManager / PARTcommunity

Projects uploaded to PARTcloud can be linked as Project of the type Assistant and so be displayed in PARTdataManager / PARTcommunity.

In this way you can demonstrate the use of your parts at an exemplary design and directly link into the catalog.

The following describes how to embed a PARTcloud page into PSOL / PCOM.

  1. Create a new project with Project type Assistant or use an already existing Assistant project.

    Sample projects in the CADENAS Demo catalog

    Sample projects in the CADENAS Demo catalog

    Under Project selection the respective icon is displayed.

    Under Edit project -> General -> General -> Project type the project type Assistant has to be displayed.

    Project type "Assistant"

    Project type "Assistant"

  2. In PARTcloud, call the part to embed.

    Example:

    https://b2b.partcommunity.com/community/partcloud/?
 route=part&name=Idea+No000002&model_id=67101

    Click on the button </> Embed model.

  3. The page "Configure your code and use it in your website" is opened.

  4. Under General Options, on the left, check only Show only the 3D viewer. Leave all other settings.

  5. Copy the HTML code and only use the marked part of code (see next figure).

    <iframe> tag

    <iframe> tag

  6. Modify the following files:

    • *.prj

      Create following keys or modify them accordingly.

      • Key SERVERPAGE has the value forward<xy>.html.

        [Note] Note

        Pay attention that the file name stated here is really accordingly to the used forward file.

      • The value of key LOCALPAGE is the same as the project file's name.

        Schema:

        <Name of project file>.ini

      • The value of the key PCOMSERVERPAGE is the copied part from the <iframe> tag (compare above).

      Example project file

      Example project file

      Once the keys SERVERPAGE and LOCALPAGE are created on file level, they are displayed on the tabbed page General in the rubric Assistant. These two keys can be edited here as well.

    • forward<xy>.html

      Always use a forward file according to the following schema.

      The value of the attribute window.location is the copied part from the <iframe> tag (compare above).

      Example forward file

      Example forward file

    • *.ini

      The name of the ini file has to be the same in compare to the respective project name.

      Always use an ini file according to the following example.

      The key firstdoc has the value "forward<xy>.html".

      Ini file

      Ini file

    [Note] Note

    Each project has its own project, forward and ini file.

  7. When the project is finished, it can be called in PARTdataManager or uploaded to the SVN server and published to LIVE.

    1. Then the result on PARTcommunity looks like this, for example:

      Directory with some projects opened in PARTcommunity (linked)

      Directory with some projects opened in PARTcommunity (linked)

      Project opened in PARTcommunity (linked)

      Project opened in PARTcommunity (linked)

      When clicking on the link at the top, the project is opened in PARTcloud.

      Project opened in PARTcloud

      Project opened in PARTcloud

    2. And this is how the result looks in PARTdataManager:

      Directory with some projects opened in PARTdataManager (linked)

      Directory with some projects opened in PARTdataManager (linked)

      Project opened in PARTdataManager (linked)

      Project opened in PARTdataManager (linked)

Prev  Up  Next
5.14.5. Post-processing  Home  5.16. Tips and Tricks