Geocortex Workflow 5 provides additional flexibility and value alongside your Esri applications. Rather than writing custom code to build the widgets you need to satisfy requirements in your Web AppBuilder for ArcGIS® applications, chose from a growing library of activities to build virtually anything quickly and seamlessly.
We’ve recently applied several big updates to Geocortex Workflow 5: in this webinar, we will give you an overview of the design experience, how the technology is being used in real-world applications, and some of the recent developments that we’ve made – including on-premises deployments, server workflows, SDKs for custom activities and form elements, and more!
If you’ve been looking for a GIS solution that goes beyond out-of-the box capabilities with your Web AppBuilder for ArcGIS® applications, while also avoiding the resource strains associated with custom development, check out the webinar below!
Geocortex Workflow 5 gives you the control to re-imagine the user experience in any way you see fit. With a constantly growing library of pre-built activities that can be chained together in nearly limitless ways, you can pick and choose which elements hide and appear based on how a user interacts with your application.
An example of one of these elements is the search results section, which can be displayed in a variety of formats to make your end-users receive their spatial data in a way that caters to their specific needs.
This week, we explore some of the ways you can show the search results using the item picker in Geocortex Workflow 5.
“Hi, I’m Ken. I’m on the workflow team, and today I’m going to show you how to show search results in an item picker using Geocortex Workflow 5. Let’s get started!”
Okay, so here we got a workflow where there is a form with a search area and then results in a separate section which is not visible by default. We're going to use the template here for filling the item picker. This is just the standard template that queries a layer with US states and then presents them in whatever form element we’re populating.
In this case, we're going to move that – I just did a cut - and then we want to paste into the event handler for the click event on the search button.
I’m just going to make a few little changes to the default template.
The query is now going to be based on the text you just typed. I will say where state name - let’s make it case insensitive - so ‘UPPER(STATE_NAME) LIKE ‘UPPER’, and then this is where we're going to put in the value from the textbox. Then, we're going to put a percentage after that. So it's anything that starts with that text.
The element that this is going to populate is going to be ‘itemPicker1’ and we're going to show the section too. Let’s save that and then run that in the sandbox and take a look.
There we go! So, you can see you just get the names there (fairly straightforward). If we want to make it more interesting we can do a few things; we can include the geometry to show the actual areas on the map, and we can actually use markdown to style this and include more fields in the text.
For the label here, I'm going to change this into a more complex expression. When you've got other texts in there you have to pick curly braces around the field names, and for a new line I'm going to do two spaces. Actually, you know what I’m going to do here is I want to put this state name - or the abbreviation, rather - in the square brackets after. So that would be ‘STATE_ABBR,’ and then the population I’ll put on the next line.
In order for this to work, I'm going to have to remember to include this field in the query and then with Return Geometry, set that to true. In order for that to work, the spatial reference has to match the map.
So, I’ll make these changes and save it. Run this again.
Now you can see a few things have happened. We've got the state abbreviation in square brackets, we’ve got the number in the next line, the state itself is bold and over on the map you can see as I roll through these that highlights them on the map.
These are just a few ideas of how you can show search results using the item picker in Geocortex Workflow 5. I hope you find that helpful. Thanks for your time!
Not a Geocortex Workflow 5 user and want to give it a try? Discover all it has to offer below!
Located in the heart of Detroit’s northern suburbs, the city of Troy, Michigan is the largest city in Oakland County. Known for its upscale shopping and business facilities, this lively city with a population of 83,000 (and growing) adopted GIS to allow both its citizens and public workers to make quicker, accurate, and more sophisticated spatial decisions when it comes to modifying city services and infrastructure.
In order to not only comply with Municipal Separate Storm Sewer System (MS4) permitting requirements, but get ahead of them, the City needed to come up with an innovative GIS solution that focused specifically on tracking time and equipment, and provided the ability to connect this data with their assets.
By utilizing both Geocortex Essentials’ workflow capability and the Cityworks® Extension for Geocortex Essentials, the City of Troy built an intuitive application that guides City staff through collecting all the essential elements needed during an inspection. Elements like equipment, staff, and all relevant options that could be pursued in regards to preventative maintenance of storm inlets.
Additionally, the City’s GIS team also leveraged database views to mark recently cleaned drains, enabling them to identify structures that had recently received preventative maintenance and avoid accidentally overlooking (or duplicating) any buildings that required their immediate attention.
Since launching this application, it has been adopted by the City’s Drains Division and Sewer Division for field maintenance tracking. They are also now able to monitor individual repairs and costs, allowing them to better manage the use of their resources and focus their efforts more intelligently.
Geocortex Reporting 5 allows you to better understand and visualize critical relationships in your data through its highly-configurable and versatile reports.
In addition to the wide range of ready-made controls available for you to deploy with this technology, those using or considering the on-premises version of Geocortex Reporting 5 have the added option to use scripting to include attachments in reports.
We explore precisely how this is done in this week's Geocortex Tech Tip.
Note: this Tech Tip requires using code in the Attachment Script, which can be accessed by clicking here. You’ll need this to try it out for yourself.
"Hi everyone, my name is Houtan Emad and I’m with the technical marketing team. Today I’m going to show you how to use scripting to display feature attachments in Geocortex Reporting 5.
Let’s do this!
The first thing we want to do is make sure we’re using an on-premise version of Reporting 5. The on-premise version, as of 5.1.0 includes the ability to attach scripts to a report.
In this example, we would like to generate reports for specific service requests, where each service request feature may have an image as the feature attachment.
We’ll first set up a basic Web AppBuilder site that consumes a web map which includes our service requests layer. Once that’s set up, we will open up Geocortex Reporting 5 on-premise version 5.1.0, add our service requests layer as a data source, and create a basic layer report using the wizard.
We can add this report to our Web AppBuilder site and target the Service Requests layer.
We’ll save our site and test our report.
Look good! Let’s go back to the report designer.
To include feature attachments in our report, we will drag a PictureBox element into our design area and then switch over to the Scripts section of designer.
Right, now we’re going to copy and paste the standard image attachment script here. You can find a copy of this script in the description. Once added, we will need to make a couple of customizations.
Our first adjustment is on line 2. Here we’re pointing to a “No Image Available” URL which will be displayed when we’ve selected a feature that has no image attachments.
Next, we’ll specify the service URL on line 3. We want to point to our layer containing the feature attachments.
On line 4, we’re targeting the Object ID field which is used in composing a link to the feature attachment.
Finally, on lines 2, 31, and 32 we’re making a reference to the ID of the picture box element we’re targeting in our report. Our example targets pictureBox1. We can validate our script by using the script validation button, and then navigating back to the report design interface.
As the final stage in our set up, we select our picture box element and expand the Behavior section of the Properties tab. Under Scripts, we will use the dropdown options for Before Print and select ‘Detail1_BeforePrint,’ which is the name of the function we just wrote in the scripts section.
We can then save our report and test it again in Web AppBuilder.
That looks good too!
By spending a little more time on the report, we can fully brand it, add additional fields, and even feature maps.
If we wanted to generate a report for more than one Service Request at a time, and provide the user with a more guided interaction, we can leverage Geocortex Workflow 5 in conjunction with Geocortex Reporting 5 to achieve that."
Discover how Geocortex Reporting can be used alongside Web AppBuilder to enhance and extend your applications. Check out our webinar, Enhancing Web AppBuilder for ArcGIS® with Geocortex Reporting by clicking the button below.
One of the many benefits of our Geocortex Essentials technology is its ability to integrate with virtually any key 3rd party business system or data source.
There is no need to duplicate, move or reconfigure your data for a proper integration when it comes to using Geocortex applications; your data can simply flow seamlessly between systems, allowing for you to access your information faster and more efficiently.
With that in mind, we thought that this week’s Geocortex Tech Tip would be a great opportunity to focus on this in more depth by showing you how to use Geocortex Essentials to integrate with third party map providers like Bing Maps and Pictometry.
“Hello and welcome to Geocortex Tech tips. My name is Jonathan and today we are going to be talking about how to integrate third party maps with your applications such as Pictometry, Bing and other providers.
Let’s get started!
First of all, I got a viewer set up here, so let's take a look at the feature and see how it works! If I go to the ‘Linked Maps’ button here, I can bring up a view at the bottom of the screen and - make that a little bit bigger - and our default provider here is Bing Maps. You can see I've got an icon on the map here that I can move around to change the point on the map that I'm looking at, and drag it over to that heliport there, and then down here on Bing Maps we can see a heliport on top of that building right there - it's probably the same one.
If we look at that we can see that's the Los Angeles Times building and the Los Angeles Times Heliport. Nice! So how is this configured? Let's take a look first at our desktop json.js. We can see the integration module, and then in the configuration for the integration module we have some external components, ‘bingMaps’ and ‘pictometry’ and we have defined ‘bingMaps’ as the default component. And bingMaps tells it to load a page from ‘Resources/3rdPartyMaps/BingsMaps.html’, and it tells it to use this icon for the little dragable indicator that you see on the map.
If we go and we look in the viewer installation directory (that's what this is pointing to so it will be HTML5 viewer/Resources/3rdPartyMaps in your IIS folder) and then we'll take a look at a copy of that file, and first thing you need to know - you don't need to know any of this code necessarily - but you do need to find the spot on the page where it says ‘bingAPIKey’ and you need to put your API key that you got from the Bing Maps API developer website, and put it in there to make it work properly because otherwise you will get a nice message from Microsoft on top of your map.
So that out of the box is the only step required to make this all work properly and then you can configure it here like so and view it in the viewer like so.
Let’s look at another provider that we have called Pictometry. We're going to move over to this version of the site here because I don't have an API key that works on mine, so open the linked maps, and you can see that's not the one that we want (whoops!)
All right, there’s Pictometry - and let's pop this out to get a little bit of a better view. That came up in a new tab by default, but let's just put it side-by-side on the screen with our map like so.
We can see our marker here (we're a little bit in an industrial wasteland). Let's take a look at something a little bit more interesting. See if we can go over to Dodger Stadium. There we go!
So, we have some very nice high-res Pictometry imagery of Dodger Stadium. Doesn't look like a game is on today. We can look at some different imagery to see what's happening. No game there. Oh there look a game is on, oh but not there. The field is closed for maintenance.
Anyway, I won't go into depth on how to use the Pictometry tool – it’s basically the same as any other third party maps integration. If we take a look at the configuration page, it's very similar. Now we need an API key and a secret key and you'll get those from your Pictometry vendor, and they go in those spots and that's all that's required to make this work.
Now I'd like to cover how you would hook this system up to any third party map provider. Say you wanted to make your own, and you didn't want to use these default ones.
Then we make a new third party map, we call it ‘bingMaps’ and we pass it in a function to initialize the map and then our three handler functions that were defined above there. The initialize map function is just down here and that's where the API key is provided.
So, what goes in initialize map is whatever that third party API needs to bring up a map on a webpage. And what goes in here is, you have to return a center with an ‘X’ and ‘Y’ a scale and a heading, and just return an object with those values that you get from the API of the third party map’s control. Then when you handle the viewpoint indicator updated you just get a point with ‘X’ and ‘Y’ coordinates because you're just sitting in your ‘X’ and ‘Y’ on the map.
The viewer position updated event is a little bit more complicated because we could also be zooming in and out of different scales and changing the extent. So that takes an object with a bunch of properties like extent, positions, scale, heading, pitch - we can use some of these extra properties to handle things like a street view type map as well as your traditional 2D mapping applications.
Without getting into too much of the details of coding, that's basically the interface for creating your own, and that's all you really need for something as simple as Bing Maps to something more complicated like Pictometry or a street view application.
Thanks for listening. This has been Geocortex Tech tips and I hope you have fun using this feature on your own viewer’s insights.
To learn more about how you can extend the reach and capabilities of your mapping applications, download our integrations eBook below!
The Geocortex team recently returned from Austin, Texas where we hosted one of our last Geocortex Regional User Group meetings of the year. The event had no shortage of exciting moments, like a thought leadership piece on the evolution of the modern GIS pattern, a Geocortex technology update, a review of available resources for our customers, an open feedback session and various customer presentations. During our time down there, we also visited the City of Austin at their offices, and a group of Esri Natural Resource and State & Local Government staff in San Antonio. While visiting, we heard quite a few great stories about how our customers are using our technology, and we wanted to take a moment to share a few of them with you.
City of Austin Watershed Protection
The City of Austin Watershed Protection group’s FloodPro Application is a public-facing app that allows the public, developers, surveyors, realtors and insurance agents to access property information. It incorporates data from 7 sources including spatial data from FEMA and contains 10 layers. Users can download floodplain models including the 100 year and 500 year elevations of a property, elevation certificates that are necessary for permitting, and hydraulic/hydrologic models. The app has eased the burden on staff to produce and provide these models, and use of the application has doubled every year since it launched!
Texas Boll Weevil Eradication Foundation
Founded in 1993, the Texas Boll Weevil Eradication Foundation is a non-profit government agency tasked with eradication of the invasive Boll Weevil that nearly devastated the Texas cotton industry. One of our longest customer relationships, the Foundation won the Esri Award for Special Achievement in GIS at the 2016 Esri User Conference. Before the implementation of Geocortex, each Weevil trap had a bar code that was scanned and data manually entered into the system by inspectors. This data could not be downloaded or viewed until the inspectors got back to one of 40 offices throughout Texas. If there were errors or a trap was missed, the inspectors would not know until they had returned to the office, and would then have to make another trip out to the trap. The traps were not geolocated and often locations where estimated. After the implementation of Geocortex, all of the trap data was centralized; traps were geolocated, inspectors could work offline, and the office was able to get real time updates.
Inspectors and the office now know immediately if a trap has been missed and inspectors only need to edit a feature when they are within a certain proximity of a trap, eliminating the possibility of faking reports. Found Weevils can be reported right away and spraying can be coordinated by the next day to prevent their spread.
The success of the Foundation with the support of Geocortex technology has freed up a lot of internal resources, while completely eradicating the Weevil in Northern Texas. The Foundation is now exploring how Geocortex Mobile Viewer can take their mobile offline efforts to the next level and is working with other government agencies to explore how their model can be used to address the eradication of other invasive species.
Harris County Flood Control District
Harris County includes the Houston metropolitan area and is the third most populous county in the United States, containing 4.5 million people.The Harris County Flood Control Districtmanages projects and infrastructure to reduce flooding across 1,500 water channels totaling over 2,500 miles in length. Several hundred thousand homes and businesses are located in Harris County’s floodplain.
The District characterizes flooding as the county’s natural disaster and that proved devastatingly true when Hurricane Harvey hit in August of 2017, dropping over 1 trillion gallons of water on Harris County over 4 days. Statewide, Harvey caused $125 billion in damage, with 68 people losing their lives.
Before the implementation of Geocortex in 2011, the District had several disparate, siloed, in-house solutions for everything from vegetation management to channel repair projects. They needed a standard, intuitive solution with a common look and feel and Geocortex fit the bill. When Hurricane Harvey hit, the District was able to quickly incorporate their Harvey ad-hoc GIS products into their Geocortex applications. This information included channel damage and debris information collected via a helicopter aerial survey and field crews armed with Esri’s Collector App. This information was easily incorporated into Geocortex without any post-processing like was required in the past with ArcMap.
Using these applications, the District was able to visualize before and after information to issue repair orders. They also use Geocortex for land records and document management solutions. They have over 5,000 channel plan sets available in their Geocortex application and they love the hyperlink feature that allows them to search and access channel plan sets from Geocortex.
These were just some of the customer stories we heard during our visit in Texas, and we can't wait to head back again soon to hear what everyone is up to!
To everyone who made it out to the Geocortex Regional User Group, a special thank you. These events wouldn't be possible without your involvement, and it means a lot to see you make the effort to come our and share your feedback and success with us.
If you have any questions about these customer stories, or would like more information about what our customers in Texas are doing with Geocortex, don't hesitate to reach out to us.
To view more Geocortex Customer Stories, click the button below.
One of the things we set out to accomplish with Geocortex Workflow 5 was to dramatically boost efficiency and reduce complexities, ultimately increasing the value of your GIS applications.
In today’s Geocortex Tech Tip, we take a look at how Geocortex Workflow 5 can interact with the Attribute Table widget inside Web AppBuilder for ArcGIS. Using fire hydrant data as an example, you’ll discover how Geocortex Workflow 5 can be used to populate this Attribute Table, simplifying the experience of viewing and comparing your layer data.
“Hi everyone, my name is Patrick Fingler. I work in our technical marketing department, and in this video I’m going to show you how you can populate the Attribute Table within Web AppBuilder using Geocortex Workflow 5.
Let’s take a look!
Okay so in this Tech Tip video, I'm going to going to show you how you can populate the Attribute Table within Web AppBuilder using Geocortex Workflow 5. Here you can see I've got a web map displaying within Web AppBuilder that's got some hydrants, it has some service requests, a couple of tax parcels, and often you'll want to have a workflow that presents the user with a form that allows them to search for a layer on the map and then send that information to the attribute table within Web AppBuilder.
In this example I've already built a workflow to accomplish this. It's a pretty simple workflow, and essentially what it's doing is it's presenting the user with a form that is asking them to search for a fire hydrant. They've got two options; they can search for a hydrant by just entering the ID of that particular hydrant, or they can search for hydrants on the map.
So in this example, I might be interested in these three particular hydrants, and if I click ‘Next,’ what we're doing is we're first selecting those hydrants (well, we're actually performing a query on those hydrants), then we're sending the results of that query to the Attribute Table using the ‘Show Results’ activity within workflow 5 and then we're actually panning the map to the extent of these features.
If I wanted to, I could also search by a single Facility ID, and this example again panning to that hydrant and displaying the attributes.
So let's see how this works in the back end within workflow designer. This is the workflow that I've developed that's being run within Web AppBuilder, and I've deployed to Web AppBuilder and here you can see we've got our initial form here that's just presenting the user with the two options to either search by ID, or search by selection. Then within here, I'm saying if the user clicked submit within that form, we're then going to query for those hydrants.
We'll then switch depending on if the user is selecting them via the geometry, or if they're selecting them by the ID. In this example what I've done is actually dynamically generated the hydrant layer URL and I'll show you how to do that. Then I'm running a query based on the geometry that we selected. Then I'm saying if we got some results - if there's more than one hydrant that we've selected - we're then going to show those results within Web AppBuilder’s Attribute Table. This is the ‘Show Results’ activity that you're going to want to use, and here I'm passing in the features from my query.
Now in order to actually get them to show up and be highlighted within the Attribute Table within Web AppBuilder, you have to pass in a layer ID as well as a layer name.
Now again I'm dynamically getting these values from this hydrant layer and I'll show you how to do that - it's really useful if you're building workflows within Web AppBuilder.
Last but not least, I'm then getting the extent of those features, I'm using this activity, and then I'm setting the map extent to the extent of those features and then I'm expanding it by three. It's zooming out a little bit, and then we're just displaying our final form asking if they want to return to the start, generate a report or exit.
Now I mentioned being able to get the hydrant layer so you can dynamically get the URL, the ID, and the layer name. In order to do this you can use the ‘Get Layer’ activity within workflow 5 and it accepts a layer ID.
For Web App Builder, this layer ID is the name of the layer within the web map itself. So here I can see this is the Web map that I'm using. And this is the name of that. So I've selected that in here.
Once I do that, you'll see I'm getting the layer and these are all of the properties for the layer, so I'm able to retrieve the layer ID. I can even get the layer name as well as the layer URL, and if you're using the secured services you can also retrieve the token as well using this process, so it's a really useful activity. And that's essentially how you dynamically pass that those values into the show results activity as we can see here.
That’s essentially how you can populate the Attribute Table!
Now I also was clearing the Attribute Table as well. In this example I'm still using the layer ID and layer name, but I'm just passing in blank features. So if we rerun this workflow, and search by selection so let's select a couple of these and click “Next,” we can see I’ve selected them. If I click ‘Return to Start,’ I'm then clearing my selection, and if I wanted to generate that final report we can do that by searching for a facility ID and running a report on that. So again that's how you use these show results activity within Workflow 5 to populate the Attribute Table within Web AppBuilder.
Thanks for watching!”
Curious to try Geocortex Workflow 5? Check out our Discovery Center and see everything it has to offer!
We’ve come to expect that the apps we use have a good chance of knowing where we are (with our permission, of course). This technique - known as geolocation - identifies our locations by processing digital information and using either GPS or other related technologies to assess our whereabouts. Whether you are creating a web map application or not, geolocation is an important piece of functionality.
Our Product Development team has been hard at work ensuring that you can quickly and easily add geolocation functionality to all your applications and workflows across platforms. We’re eager to show you just how simple it is!
In this developer webinar (or “Devinar,” as we like to call it), Lucas and Matt will explain exactly what geolocation is, how it works, the options available for getting it into your application, their experience implementing it in our next-generation viewers, and the valuable lessons they learned in the process.
If you’re interested in learning more about geolocation and how it can be applied to your applications, watch the devinar below!
Communication can often be a very difficult challenge in a lot of organizations. When it comes to solving these challenges spatially, Geocortex Essentials provides real-time, map-based tools that can streamline the way your processes are being relayed from one user to another, ultimately opening the doors to a more efficient communicative environment.
Our Geocortex Tech Tip explores precisely how this functionality works for both the room administrator and other users in the room. It also shows some of the different ways it can be configured and the various types of user privileges that can be granted.
“Hi, I’m Ian Sutton and I’m a Geocortex developer. Today I’m going to show you collaboration in Geocortex Viewer for HTML5 2.10.
Let’s jump right in!
For this demo I'll be signed in and to viewers to show multiple users collaborating together on the same map. Now the first thing we want to do when we're using collaboration is sign in. You can't use collaboration unless you're signed in. Now, we're going go to our toolbar and open up collaboration.
First thing we're going see is this big empty space where all of our collaboration content will be. At the top we see a list of rooms that we can join and you can join one or more of these rooms at the same time, and all of the messages will be blended together. But for the purposes of this demonstration we are going to create a new room which we can do with this button here.
So we're going choose a name for our room and you can also choose a color if you don't like the randomly assigned one and you can also manage user access here. but we're going leave that for now. Now that we've created our room, it's going to show up in the room list and we're going to automatically join it and we can go and post some text in our room that will only be visible to people who have joined the room and have permissions to see it. Of course, that doesn't mean much unless we have another user in the room. So, let's go ahead and invite my dummy account. Since right now he can't see it. We're going go to the room list and select this room details menu here and then we're going to hit edit and you can see that it looks very similar to the screen that we had when we were creating the room.
So we're going to look up our dummy account here which is called Web EOC and we're going to add him to our room permissions and you can see we can give him no permissions specifically excluding him if we want to be mean, or we can let him just view the room or we can let him edit the room and we're going to let him edit the rooms so we can have a bit of a conversation then we're going to save so that those changes are registered to the server.
Now you see that on our dummy account here we've got a notification that a new room has been added and we can open up and see that we have access to the test room now. So we're going to open that up!
You can see in our room details that the list of active members has been updated and we can see that Web EOC has joined the test room. And now that we have more than one person in the room, we can see each other's messages, we can share a drawing on the map and we can even post images located to specific points on the map which we can open up and view in our browser. And when we leave the room in question drawings are no longer visible and you can see that our dummy user knows that he's now alone in the room.
So that in a nutshell is collaboration. Thanks for watching!”
Interested in leaning more about the collaboration feature of Geocortex Essentials? Click the button below for additional insight or to schedule a demo.
You might recall that 2018 kicked off with a big announcement from Esri. They made the decision – following feedback they received during the 2017 Esri User Conference – to allow ArcGIS Enterprise customers to add Viewers (Level 1 Named Users)at no additional cost. You might not recall that Level 1 users were first introduced in December of 2016, so perhaps it’s fitting, following this annual cadence, that we wrap up 2018 with another big announcement from Esri: the introduction of several new User Types:
Viewer (formerly Level 1);
Field Worker (new);
Creator (formerly Level 2); and
GIS Professional (new).
These continued, iterative licensing improvements are extremely positive for Esri customers looking to right-size their use of the ArcGIS platform, and come alongside our observation of ever-increasing adoption of Web GIS implementations worldwide.Our impression is that Esri is listening to (and understanding) their customers’ needs.
Meanwhile, Geocortex Essentials softwareis in the middle of an evolution, and 2018 has been a big year for the Geocortex Essentials 5-Series, which we introduced with the launch of Geocortex Workflow 5 in mid-2017. This product has enabled our customers to easily automate guided end-user interactions in a SaaS environment. Since then, we’ve been busy building four completely new 5-Series products inspired by capabilities in Geocortex Essentials 4.x:
Geocortex Reporting 5 was released in June, designed to help users create production quality, printable reports using spatial and non-spatial data, maps, and charts.We’re thrilled to see customers worldwide adopting the software in both Geocortex Viewer for HTML5 apps, and within Web AppBuilder for ArcGIS®
Geocortex Printing 5 follows in the footsteps of Geocortex Reporting, and will allow you to generate high-quality, high-resolution map print outputs in all sizes. We’re aiming to release the product in February of 2019
Geocortex Mobile Viewer 5 will fast become the world’s most capable framework for building mobile, offline, native apps on top of the ArcGIS platform, and the public beta is also scheduled for January
What’s really cool about the 5-Series is the new patterns we’re seeing customers take advantage of: from using the software entirely in the cloud SaaS environment at apps.geocortex.comor deploying workflows and reports into Web AppBuilder for ArcGIS (Developer Edition). We’ve even seen one of our Belgian partners, SIGGIS, integrate Geocortex Reporting 5 capabilities into ArcGIS Pro! These opportunities come alongside new Geocortex Essentials commercial offerings, which allow you to pick and choose the components and deployment patterns you need for your business or organization.
With five new products in the 5-Series, two already launched, and three more on the doorstep, we’re thrilled to say that Geocortex Essentials 5 has officially arrived!
Today, over 1,500 customers use Geocortex Essentials across a broad spectrum of industries and use cases, and we continue to serve those applications by improving Geocortex Essentials 4.x and the popular Geocortex Viewer for HTML5. In the summer, we released a significant performance improvement, resulting in a 50% decrease in startup time across all browsers.
Hundreds of customers use Geocortex Analytics to monitor the use of their Geocortex applications and their broader GIS infrastructure. In early 2018, we released a major update to the product to improve reliability and includereporting on specific end-user activity. We’re committed to ensuring that Geocortex Essentials 4.x and Geocortex Analytics remain premium software packages for all our customers, in parallel to developments happening in the Geocortex Essentials 5-Series.
We’ve now drafted our product portfolio strategic plan for 2019: who’s going to work on Project A and Project Band for how long, and when are we going to release FeatureX or Feature Y. This time of the year is exciting because we’re charting out the details of our next chapter on our march towards our long-term product vision. As mentioned, we havethreemajor product releases coming in Q1, and you can expect momentum to continue across all 5-Series products, as well as Geocortex Essentials 4.x and Geocortex Analytics. We’re also scheduling a sixth 5-Series product planned for Q4 –stay tuned for information about that one... for now, we’ll leave you in suspense 😊.
Here’s wishing you a happy holiday season as we wrap up a terrific 2018 and look forward to another fast-paced and action-packed 2019!