Disclaimer on Launch of Site
I've seen some older posts, 2012 and early 2015 about launching a disclaimer on the opening of a site with a button that the user has to click throughin order to access the map. Has anyone come up with a solution for this?
0
-
Hello Stephanie,
I've added your name to the list of stakeholders for this feature. One option that has been used is to configure the DefaultNoCloseButton and set allowClose to false. This means that when a workflow is displayed, the 'X' in the top right corner is hidden and the only way to dismiss the panel is to click one of the configured buttons.
Thanks, Stefan0 -
I'm looking for the same feature 0 -
Is there a reason you can't use a startup workflow with a Display Form that uses the ModalWindowNoCloseButton container? 0 -
We have written a customized disclaimer page that a user must accept. Additionally we've added the capability to set and store a cookie to delay the next time a user is prompted to accept the disclaimer. We haven't officially released this as we are still working on a few other things but you can view a demo at https://maperture.digitaldataservices.com/gvh_custom/ 0 -
We have implemented a disclaimer for our public map viewers that users must accept before they can see parcel data. It makes use of a custom module along with a startup workflow. If the user declines, the workflow will remove the parcel layer from the viewer. We have not implemented any cookies because we need the user to accept each time they use the application. This disclaimer is also AODA / WCAG 2.0 compliant. There is also a bit of javascript added to the index.html to handle trapping certain keycodes (eg. escape key).
You can see it in action at http://www.giscoeapp.lrc.gov.on.ca/matm/Index.html?site=Make_A_Topographic_Map&viewer=MATM&locale=en-US.0 -
Dear Peter Hanmore can you please share the custom module and the workflow if that possible 0 -
Hi Peter, would you be able to share this? I've been trying to do this and I can't figure out how for the life of me. If there is anything I need to customize, this is it! Need help, please! 0 -
Stephanie,
I'll check about posting the code. We've actually started using some new code for our disclaimers. At the very least I should be able to detail the process we followed, if not the actual code.
Peter.0 -
Thanks Peter! I realized after I posted my request that Daniel Briggs had shared back in July a simple workflow that utilizes what John Nerge is referring to. It works perfect. The only thing I can't figure out is I tried to add a 'Disagree' button that would close the entire viewer and redirect to our corporate homepage, but it doesn't seem to work.
The following is what I did:- Add a decision after the DisplayForm where 'buttonResult' = "Agree"
- From the False node, I added 'RunExternalCommand' where the Command Name is "NavigateCurrentPageToUri" and the Command Parameter being the web URL.
0 -
True or false: Your user had to agree to the terms in order to enter the site, and if they disagree, they aren't allowed to use the site.
Wouldn't you accomplish the same thing by only having an agree button? If the user doesn't want to agree, they can click back or close the tab. The disagree button is a false option from a usability standpoint. There isn't some different application I can use if I disagree to the terms. The outcome of disagreeing is the same as not using the application.
Better yet, what about having an OK button and an I Agree checkbox? I'm by no means a legal expert, but thinking as a user, clicking a button is a mindless activity. Clicking a button and then realizing it won't work until I check a box forces me to stop and think about what am I agreeing to (or I just check it mindlessly too, in which case the process is still no worse for wear).
Here's a stack exchange with more thoughts on the topic:
http://ux.stackexchange.com/questions/76687/i-agree-check-box-or-buttons0 -
Hi,
I am looking for a similar implementation as Peter Hanmore mentioned and which can be found through this URL 'http://www.gisapplication.lrc.gov.on.ca/AIA/Index.html?viewer=AIA.AIA&locale=en-US' however, the details or implementation code is not clear for me.
I am facing some issues with John Nerge recommended implementation when I add an image to the top of the disclaimer and the disclaimer text is larger enough to make a scrollbar. This is what happens:- As site is loaded and the disclaimer window appears, it scrolls to the bottom but still the agree or disagree buttons are hidden and requires the user to scroll further down. It makes user wonder what to do.
- Comment #2 is related to #1 however is a bit weird as if I initiate the same workflow from a tool or hyperlink, I can see the bottom Agree or disagree buttons without issues.
Thanks in advance for your help.0 -
Hi guys,
Please share some thoughts in light of your experience regarding the questions I posed in the thread above.
Thanks0 -
I think the article I posted back in December covers the topic well, in particular this response that states "it's not answerable without UX goals":
https://ux.stackexchange.com/a/76719
I know that doesn't answer your question about the functionality you're trying to get in your form. Instead, I'm suggesting you think about different question: what is the purpose of the user agreeing to your terms?0 -
Thanks John, your artical and shared link is extremely useful and i wish GeoCortex had the flexibility of easy implementation of these stated UX goals. However, in either case of #1 or #2 objectives, I am finding it hard to make the button visible when I have fairly large disclaimer text to cause a scrollbar appear and when I load the workflow at startup :(. BTW, my preference will be a bit modified version of option 1 or option 2.
I was hoping that some runtime form modification might help but am not sure how as controls are different in DotNet and GE Workflow.0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
14 kommentarer