@prashanth ponugoti - a couple of things to look at:

1) When you open the first link in /csp/healthshare does it open for you after authenticating?

2) Is your /csp/test web application definition set to work in the same namespace as /csp/healthshare?

3) Is a copy of your person.csp file moved to the web application root that you defined for /csp/test?

Hope that helps get you started on finding a solution.

Is there a single development server which all developers connect to?  If you are not able to have a fully isolated development environment for each developer then you will end up getting frustrated trying to use client-side source control.

You might want to consider the new server-side Git source control hooks which were recently launched:

https://community.intersystems.com/post/git-shared-development-environments

This won't solve your issue of working while not on VPN, but it will allow multiple developers to work against the same instance without stepping on each others' toes.  

@Nicola Sartore - what does your organization use for a source control strategy?  if you use server-side source control hooks and you are on at least Cache 2017.1 (or any version of IRIS) then you can mix and match Studio and VS Code as VSCode fully supports server side source control (as well as client side, but if you are a Studio shop then you don't have any client side source control in place)

Lookup Tables are covered by the Source Control hooks in the management portal so they will automatically be added to your uncommitted queue upon check-out so you can include it in a future ItemSet upload.  

See slides 12-14 of ftp://ftp.intersystems.com/isc/customers/ccrtraining/ICC530(Presentation)%20CCR%20Tier%201%20-%20Interoperability%20Components.pdf 

@Stephen Ali - thanks for asking the question (and welcome to the Developer Community!).

Typically detailed questions like this on TrakCare products are worked out directly with InterSystems Support.  Globally we have TrakCare product tuned to regional requirements so it's important to connect with you product specialists from your specific region.  

I suggest you go to https://www.intersystems.com/support-learning/support/ to see how to contact Support and they can help you get this question sorted out.

Just curious - where are you seeing this?  Could you please include a URL?

The InterSystems SSO account is what controls your access to open as well as restricted applications provided by InterSystems to help customers and prospects get stuff done.  If you go to Login.InterSystems.com you can see the various apps available to you (after you sign in).  This would include things like D.C., OEX, Learning, Download, etc for Prospects, and supported customers would also get access to WRC, iService, HS Docs, CCR, etc (depending on what products they have).

Hope that helps - let me know if any additional clarification is needed.

There are different kernels but other than that you should be able to run the same ObjectScript code on both platforms and it will behalf identically.  If you are going to be doing file interactions, then I suggest using the %File library class which will make your code portable between Windows and UNIX file systems.  Likewise if you are calling out to other executables, you will need to instrument your code to call out appropriately based on your platform. 

I am assuming you want to create a tag-based CSP page as a quick and dirty way to through up some data in a table?  If so, the basic steps would be:

  1. Load a JS library like https://www.tablefilter.com/ to make your filtering easy
  2. Write out your <table> and <th> tags 
  3. Create a <script language='cache' runat='server'> block to hold your ObjectScript which will fetch your result set 
  4. Use %SQL.Statement to create and run the query and fetch the data
  5. Iterate over the resultset, and write out a row of HTML for each row in the resultset using &html<>
  6. End your </script> tag and then end your </table> tag

Hope that gets you rolling!

@Perla Escarcega  - taking a closer look at this, I think we had an issue with a historical file clean-up routine which was a little too overeager to reclaim space.  All of your source is safe and available but you may need to create a fresh ItemSet to push this source.  Note - you should always be making fresh ItemSets anyway because the head revision may be newer than what is in your historical ItemSet, and you don't want to get an older revision of something which breaks when interacting with a newer revision of other items.  So simply create a new ItemSet for BASE and deploy it and you should be all set.

P.S.  This does raise the question of why you are initializing a new Secondary BASE environment from old ItemSets as opposed to just grabbing the head revision of the BASE source and running Refresh to pull it all into the Namespace?  I am afraid your approach may be significantly more risky than the recommended approach.