You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project portal to day may have som upcoming issue that we need to address. This regarding the context-id in the url. When a context is selected the portal will ty to add the context to the url as follows.
Teh GUSID is the context identifikator. After looking at som applications in fusion such ass people-search this application does not support context after the application key. this may result in applications not able to load in project portal, but business may want the user to be able to use these applications, but sins applications routes ar not consistent. this is not possible at the moment.
We have been able to enable the meetings applications sint this is a legacy application and all legacy applications handle context them selvs.
the issue here is not providing the right context to the application self. but how do we provide the context to a context first portal?
I have purposed adding the context as a query parameter. but this has been argued against.
another solution might be adding context to the path before appKey as follows.
// projset.fusion.com/:contextId/apps/:appKey/
but this may result in issues with some applications.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The project portal to day may have som upcoming issue that we need to address. This regarding the context-id in the url. When a context is selected the portal will ty to add the context to the url as follows.
Teh GUSID is the context identifikator. After looking at som applications in fusion such ass people-search this application does not support context after the application key. this may result in applications not able to load in project portal, but business may want the user to be able to use these applications, but sins applications routes ar not consistent. this is not possible at the moment.
We have been able to enable the meetings applications sint this is a legacy application and all legacy applications handle context them selvs.
the issue here is not providing the right context to the application self. but how do we provide the context to a context first portal?
I have purposed adding the context as a query parameter. but this has been argued against.
another solution might be adding context to the path before
appKey
as follows.but this may result in issues with some applications.
@odinr
Beta Was this translation helpful? Give feedback.
All reactions