Manuals - eCATALOGsolutions

Chapter 5. PARTproject

5.15. Embed use cases in PARTdataManager / PARTcommunity

Projects uploaded in PARTcloud can be linked via project of the type Assistant and thus displayed in PARTdataManager / PARTcommunity can be displayed.

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 in PSOL / PCOM.

Create a new project with the Assistant project type [Project type] or use an existing Assistant project [Assistant].

Sample projects in the CADENAS Demo catalog

The corresponding icon is displayed in the project selection [Project selection] is displayed.
The project type wizard [Assistant] must be displayed under Edit project -> General -> General -> Project type.

Project type "Assistant [Assistant] "

Call up the part to be embedded on PARTcloud.

Example:

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

Click on the </> Embed model button.

The page "Create a code to embed on your website " opens.
Under General Options on the left-hand side, only set the Show only the 3D viewer checkbox. Leave the other settings as they are.
Copy the HTML code and only use the marked part of code (see next figure).

<iframe> tag
Modify the following files:
- *.prj
  Create following keys or modify them accordingly.
  - The key SERVERPAGE has the value forward<xy>.html.
    
    Note
    Pay attention that the file name stated here is really accordingly to the used forward file.
  - The key LOCALPAGE has the Ini file with the same name as its value.
    Schema:
    
    <Name der Projektdatei>.ini
  - The key PCOMSERVERPAGE has the section copied from the <iframe> tag as its value (see above).
  Example project file
  
  As soon as the keys SERVERPAGE and LOCALPAGE have been created at file level, they are displayed on the General tab page in the Wizard [Assistant] section. These two keys can also be edited here.
- forward<xy>.html
  Always use a forward file according to the following schema.
  The attribute window.location has the section copied from the <iframe> tag as its value (see above).
  
  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
Note
Each project has its own project, forward and ini file.
Once the project has been completed, it can be called up in PARTdataManager or uploaded to the SVN server and published LIVE.
1. The result then looks like this on PARTcommunity, for example:
  
  Directory with some projects opened in PARTcommunity (linked)
  
  Project opened in PARTcommunity (linked)
  
  Click on the link at the top to open the project in PARTcloud.
  
  Project opened in PARTcloud
2. And this is what the result looks like in PARTdataManager looks like:
  
  Directory with some projects opened in PARTdataManager (linked)
  
  Project opened in PARTdataManager (linked)

Prev	Up	Next
5.14.1.4. Conversion from PS3 to RFA	Home	5.16. Tips and tricks