At-a-Glance: Atlassian Government Cloud is now generally available, giving U.S. government agencies and regulated organizations secure access to the full […]
At-a-Glance: What the announcements from Atlassian Team ’25 Europe Mean for Regulated Industries Atlassian Team ’25 Europe introduced a significant […]
Atlassian Data Center will retire in 2029, but Oxalis has already prepared the path forward. With proven expertise in regulated industries, we ensure continuity today while guiding customers toward secure, compliant, and future-ready cloud platforms. From Atlassian Government and Isolated Cloud to tailored alternatives, Oxalis delivers stability now and innovation for tomorrow.
Yesterday, Atlassian announced that their Data Center products will reach end of life on March 28, 2029. While any change of this scale can feel significant, I want to take a moment to share what this means for our customers, and how Oxalis is already preparing to make sure your teams remain secure, compliant, and mission-ready.
Today, the need to modernize ITSM for SLED agencies has never been more urgent. Atlassian’s Jira Service Management (JSM) offers a modern, secure, and cost-effective alternative that empowers agencies to streamline workflows, improve collaboration, and future-proof IT operations. This blog explores why migrating to JSM is more than an upgrade—it’s a strategic move toward better service delivery, operational resilience, and long-term value.
In the public sector, compliance isn’t optional, but it doesn’t have to come at the cost of agility. Federal, state, and local agencies face tight budgets, critical infrastructure demands, and constant oversight, yet traditional systems built for accountability have often slowed progress instead of enabling it. IFS changes that equation by pairing strict governance with flexible, responsive execution, empowering teams to innovate while maintaining full compliance. At Oxalis, we help agencies adopt IFS to modernize operations, meet regulations with confidence, and adapt seamlessly to mission demands.
Modern ERP systems like IFS Cloud embed compliance into daily operations—from audit trails and role-based access to automated reporting and policy-aligned workflows. This blog highlights 10 ways ERP modernization helps public sector teams reduce risk, prepare for audits, and eliminate the stress of manual oversight. For CIOs and compliance leaders, it’s not just about passing the next audit—it’s about building a system that supports every one after that.
Legacy ERP systems like SAP ECC, R/3, Oracle EBS, and JD Edwards weren’t built for today’s mission-driven, asset-intensive operations. Modern ERP platforms like IFS Cloud deliver what legacy systems can’t: real-time visibility, mobile field service, compliance-first architecture, and rapid time-to-value. This blog explores 10 essential capabilities that distinguish modern ERP from its predecessors, offering public sector leaders a smarter, more resilient path to operational excellence.
If you're seeking an ERP solution that can flex with your needs, simplify compliance, and drive smarter service delivery, IFS Cloud—backed by Oxalis—delivers a future-ready foundation.
If you're seeking an ERP solution that can flex with your needs, simplify compliance, and drive smarter service delivery, IFS Cloud—backed by Oxalis—delivers a future-ready foundation.
Legacy ERP systems are no longer built for the way modern businesses operate. They’re costly to maintain, difficult to integrate, and lack the agility needed in fast-paced industries. Cloud ERP solutions—like IFS Cloud—solve these challenges by offering flexibility, security, and real-time data access. In this blog, Oxalis explains why organizations are making the shift and how IFS Cloud supports scalability, compliance, and smarter operations. As an experienced partner, Oxalis helps organizations migrate with confidence—delivering a tailored, future-ready ERP solution.
Used by Google Analytics 4 to persist session state and track usage across visits. The XXXXXXXXXX portion corresponds to the Oxalis Google Analytics property ID.
1 year
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.