Visit Freshworks.com Visit Freshworks

Workspace nor not to workspace

  • 9 January 2023
  • 4 replies
  • 68 views
Daniel Söderlund
Rank
Userlevel 7
Badge +11

Hi, 

 

I have started to looking into WS in FS in my trial.  
Found few things that I’m questioning “why didn’t they do like this”. 

Wounder if anyone else have been looking into using? 
 

  • No global custom objects, if you have WorkFlowAutomations that uses custom objects you need to create them in specific workspace. You need to duplicate/mirror (manually) the custom object if the same ticket going to be moved to another workspace. 
  • The prefix for the ticket is default workspace(IT)set to SR(type: service request), so of a ticket is routed back to IT workspace it will get SR and not the same it was before like a INC. (You could mitigate this with an WFA and a hidden field that contains the original type)

 

My findings for now, except they way access it handled and few other settings that has moved around. 

A new error is always a sign of progress!

4 replies

Daniel Söderlund
Rank
Userlevel 7
Badge +11

I created this, if you think it would be good please vote it up. 

Workspace - Global Custom objects | Freshworks Community

A new error is always a sign of progress!
rashmi.nag
Userlevel 7
Badge +9

@daniel.soderlund - Thank you for sharing your feedback here and also including your request as an Idea. This will certainly help our teams get perspectives from our users.

Tagging @Deepthi for visibility! 

Cheers, Rashmi || Team Refresh Community
8
Rank

I'm also running into issues with Workspaces - the api doesn't seem to work since we switched to using workspaces. This applies to both azure user provisioning and other api queries, We get these error messages when trying to connect to the api.

 

"field": "workspace_id",

"message": "Unexpected/invalid field in request",

"code": "invalid_field"
 

Is there updated api documentation when enabling workspaces in Freshservice?

Daniel Söderlund
Rank
Userlevel 7
Badge +11

I'm also running into issues with Workspaces - the api doesn't seem to work since we switched to using workspaces. This applies to both azure user provisioning and other api queries, We get these error messages when trying to connect to the api.

 

"field": "workspace_id",

"message": "Unexpected/invalid field in request",

"code": "invalid_field"
 

Is there updated api documentation when enabling workspaces in Freshservice?

I have seen the same. I looked at the API docs and they haven’t been updated what I can see. 

 

 

A new error is always a sign of progress!

Reply


Terms of UseCookie settings