Skip to main content
Question

Link at Lobby to 'Navigator Engineering Part'

  • November 7, 2025
  • 0 replies
  • 8 views

ZIGESAMM
Do Gooder (Customer)
Forum|alt.badge.img+7

Does anyone know how a Link in a lobby element must look like to navigate to the page ‘Engineering Part Navigator’?

Copying the standard-URL does not work when Aurena is configured with language ‘german’.

When changed to english and then copying the Browser-URL to the Lobby-Element the Jump from the Element loads but does not show any data.

Relativ path (whithout the server part in the URL) has the same behaviour.

 

this does not work:

https://>server>:46080/main/ifsapplications/web/page/EngineeringPartNavigator/Form;$filter=PartNo%20eq%20'100000'%20and%20PartRev%20eq%20'R01';searchcontext=;record=KFBhcnRObz0nMTAwMDAwJyxQYXJ0UmV2PSdSMDEnKQ%3D%3D;treeviewrec=KFBhcnRObz0nMTAwMDAwJyxQYXJ0UmV2PSdSMDEnKQ%3D%3D;treeview=EngPartStructureTree;treeclient=EngineeringPartNavigator;treenodeid=UEFSVE5PPTEwMDAwMFBBUlRSRVY9UjAx;path=0.316016970.807759036.8961333.138990472.eyJhIjoidmlydHVhbC04OCIsImIiOiIxMzg5OTA0NzIiLCJpIjoiRm9ybSIsImYiOiIvUGFnZSIsImciOiJFbmdpbmVlcmluZ1BhcnROYXZpZ2F0b3IiLCJlIjoiTmF2aWdhdG9yIC0gS29uc3RydWt0aW9uc2FydGlrZWwiLCJqIjoiRW5nUGFydFN0cnVjdHVyZVRyZWUiLCJsIjoiRW5naW5lZXJpbmdQYXJ0TmF2aWdhdG9yIiwiaCI6IlBhcnRObyBlcSAnMTAwMDAwJyBhbmQgUGFydFJldiBlcSAnUjAxJyIsImQiOnRydWUsInNlYXJjaENvbnRleHQiOiJQcm9kdWN0QW5kTW9kZWxTZWFyY2hDb250ZXh0LlByb2R1Y3RObzpudWxsLFByb2R1Y3RBbmRNb2RlbFNlYXJjaENvbnRleHQuTW9kZWxObzpudWxsIiwic2VhcmNoZmlsdGVyIjoiIn0%3D

 

this works:

https://<server>:46080/main/ifsapplications/web/page/EngineeringPartNavigator/Form;$filter=PartNo%20eq%20'100000'%20and%20PartRev%20eq%20'R01';searchcontext=;record=KFBhcnRObz0nMTAwMDAwJyxQYXJ0UmV2PSdSMDEnKQ%3D%3D;treeviewrec=KFBhcnRObz0nMTAwMDAwJyxQYXJ0UmV2PSdSMDEnKQ%3D%3D;treeview=EngPartStructureTree;treeclient=EngineeringPartNavigator;treenodeid=UEFSVE5PPTEwMDAwMFBBUlRSRVY9UjAx;path=0.316016970.807759036.8961333.138990472.eyJhIjoidmlydHVhbC04OCIsImIiOiIxMzg5OTA0NzIiLCJpIjoiRm9ybSIsImYiOiIvUGFnZSIsImciOiJFbmdpbmVlcmluZ1BhcnROYXZpZ2F0b3IiLCJlIjoiRW5naW5lZXJpbmcgUGFydCBOYXZpZ2F0b3IiLCJqIjoiRW5nUGFydFN0cnVjdHVyZVRyZWUiLCJsIjoiRW5naW5lZXJpbmdQYXJ0TmF2aWdhdG9yIiwiaCI6IlBhcnRObyBlcSAnMTAwMDAwJyBhbmQgUGFydFJldiBlcSAnUjAxJyIsImQiOnRydWUsInNlYXJjaENvbnRleHQiOiJQcm9kdWN0QW5kTW9kZWxTZWFyY2hDb250ZXh0LlByb2R1Y3RObzpudWxsLFByb2R1Y3RBbmRNb2RlbFNlYXJjaENvbnRleHQuTW9kZWxObzpudWxsIiwic2VhcmNoZmlsdGVyIjoiIn0%3D

 

 

To start to find the mistage or problem is to understand the URL-Syntax. Can anyone explain the difference?

Important is the <path=> string.

How can I find out what is coded in this string?