The dashboard available inside of Geocortex Workflow Designer allows users to easily customize their design experience based on the viewer application type that their workflow will be running in. This helps to ease development requirements by creating design environments that contain only the workflow activities that are guaranteed to run inside of the specified viewer application.
This Geocortex Tech Tip explains how to use the Workflow Designer dashboard to create customizable design experiences. Additionally, it demonstrates how to initiate design experiences that are specific for developing server-side workflows or workflows that need to run in multiple environments.
Hi, it’s Paul here from the Technical Sales team. Today we’re going to have a look at the new dashboard inside of Geocortex Workflow Designer. This dashboard allows you to pick the viewer application type that you’re building a workflow for. Based on what you choose, it customizes your design experience accordingly. Let’s jump in!
Our documentation in the Geocortex Documentation Center has some great tips and tricks for creating Geocortex workflows in different environments. There’s also a handy dashboard, as I mentioned earlier, within Geocortex Workflow Designer that will allow you to customize your design experience specifically for the viewer application that you’re working with.
We’ll hop over into Geocortex Workflow Designer. This is the dashboard here that I mentioned. Inside this dashboard we have options to create a Geocortex workflow for a given viewer application.
I’ll hop into the “Workflow for ArcGIS Web AppBuilder” version of Geocortex Workflow and you’ll see here on the left side of the screen that I’ve got a list of customized activities specifically for Web AppBuilder. You can see that it says, “Showing 210 of 221 activities”. That means that 210 of the total 221 activities available in Geocortex Workflow will work with Web AppBuilder.
You can also see in the list that there’s a couple of activities that will only work with ArcGIS Web AppBuilder. These wouldn’t be available if I were working with, for example, Geocortex Web.
I’ve installed this instance of Geocortex Workflow alongside my portal for ArcGIS instance. Because I’ve done this, the dashboard will show all the same options with an additional “Server Only Workflow” option. Because I’ve installed Geocortex Workflow internal to my portal environment, I can now build server-side workflows. Common examples of server-side workflows include workflows for connecting to mail servers or workflows for connecting to internal databases. So, with this “Server Only Workflow” option you can run server-side activities that run on the server and then possibly feed information over to the client.
Finally, we’ve got an option over here on the right called “Choose Environments”. This will allow us to sort of customize our workflow. So, if you’d like to build a workflow for multiple viewers at the same time, or if you’d like to have that option available, you can select this to build a workflow that will run within multiple applications. In this case I’ll select the boxes next to “Geocortex Web” and “ArcGIS Web AppBuilder”. Now my workflow will display activities specific to both these applications. So, there are some options available for me to customize the design experience.
That’s all I have for you today. Have a good one!
Want to learn more about the capabilities of Geocortex Workflow? Click the button below for more information on what is possible with Geocortex Workflow.