Teamspace and relative path

Hi Knimers,

I tried to share/save a component in a teamspace and I noticed that the “Create workflow relative link” option is disabled whereas it is enabled if I use the local workspace.

I would like to know if it is a normal behavior with the version 4.1 ?
Because I was able to save metanode with the relative path option in version 3.7.

Regards,
Joel

Hi @joel,

yes that is normal behavior. I just double checked that it was the same with 3.7.2.

Best,
Marten

Hi @Marten_Pfannenschmidt

Thanks for your reply.
I didn’t mention it but it was version 3.7.1 not the 3.7.2.

So, does it mean that you modify the behavior between 3.7.1 and 3.7.2 ?

Regards,
Joel

Hi @Marten_Pfannenschmidt

I tried to save my metanode on another teamspace using 3.7.1 and it was not possible to use relative path.

Is it possible that I was able to save my metanode using relative path on my TeamSpace because it is located in my home directory ?

Regards,
joel

Workflow-relative paths only work within the same mount point. Therefore if your workflow is in your local space and you save the component in the team space you can only create an absolute link containing the team space mount ID.

2 Likes

Hi @thor

Thanks for your reply.
I understand now the concept.

Regards,
Joel

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.